Hello
Is there any chance for upgrade lgtv1 binding to OH3.
It works pretty well witch older LG 3D TV’s with netcastOS.
Same here.
But is the binding still maintained? Couldn’t find up to date source.
There is only v1 binding.
As I was also using this binding which is now missing and I have no experience in developing bindings, I created a small script that can be invoked from rules to at least trigger commands: GitHub - michikrug/lgtvremote
E.g.:
rule "Turn TV Off"
when
Item TV_Switch received command OFF
then
executeCommandLine(Duration.ofSeconds(4), "python3", "/etc/openhab/scripts/lgtvremote.py", "-a", "192.168.xxx.xx", "-p", "123456", "-c", "POWER")
end
Hi!
Thanks for sharing !
Could you add command to switch HDMI inputs?
We also lost online status and state of TV/mute etc.
Try this - we can add all commands in one rule
item
String TV_LG_command "LG TV command"
rule
rule "LG TV Remote"
when
Item TV_LG_command received command
then
switch (receivedCommand) {
case "POWER" : executeCommandLine(Duration.ofSeconds(4), "python3", "/etc/openhab/scripts/lgtvremote.py", "-a", "192.168.xxx.xx", "-p", "xxxxxx", "-c", "POWER")
case "MUTE" : executeCommandLine(Duration.ofSeconds(4), "python3", "/etc/openhab/scripts/lgtvremote.py", "-a", "192.168.xxx.xx", "-p", "xxxxx", "-c", "MUTE")
}
end
sitemap
Switch item=TV_LG_command label="TV LG Remote" mappings=["POWER"="TV OFF", "MUTE"="MUTE"]
For the online state I used the network binding using ping to the TV IP.
As I use a receiver for the audio I do not have a need for the mute state.
I will have a look what else is possible.
Maybe I find also some time to learn how to write a proper binding.
For changing inputs you could (for now) only use the EXT command followed by calls to the LEFT/RIGHT/OK commands to select the input you want.
Works like charm. Thanks a lot @michikrug . Nice job
“MUTE” was only an example - we can add all comands in one rule. Propably I will do that if i got free time.