I decided not to go through the process of integrating this version of the binding into the main project.
Instead I am right now working on a version for openhab2, as this naturally fits the way this framework works and discovered devices. Yesterday I was able to get the basic functionality working.
An initial version for openhab 2 is ready for review.
The plugin performs background auto discovery of WebOS TVs. It will connect to the TV only if at least one channel is connected.
The plugin will attempt to auto detect the local network interface. The IP can also be configured in a configuration file cons/services/connectsdk.cfg with following content (example) binding.connectsdk.discovery:localIP=192.168.1.1
This will not be necessary if your hostname resolves to this IP or if you just have one non-loopback interface.
This plugin now theoretically also supports IPv6, even though I have not tested.
Also the size could be further reduced. (1.53 MB -> 0.97MB) as OH2 provides more of the required libraries out of the box.
Okay, i started to completly set everything up new from scratch (Installed raspbian on pi2, installed java 1.8, installed openhab over apt-get). After first connection my TV doesnât gets paired again. You can see, that openHAB is recognizing the TV when you turn it on and off, but no pairing is done. So same behavior as before. Donât know whats wrong.
I already tried over Wifi and over LAN Cable, but same behavior. Is there something i should look out when i install openHAB with âapt-getâ such as read/write rights in directories or other things because of the privileged openHAB User which executes openHAB instead of root? I already gave rights to the directory â/etc/openhab/jetty/etc/â where connectsdk saves the connected Devices. Maybe there are other directorys which connectsdk saves to?
Okay, but iâm not running openHAB as root. If you install openHAB over apt-get it creates a new User âopenhabâ which is running openhab. Donât know if this could be a Problem. I will look into my TV Settings later. Maybe there is something else i havenât seen yet.
Worked straight away.
Wondering if there are any options to check the state of the power. Now thinking of using the NetworkHealth binding for this but if itâs possible with SDKâŠ
And also the SDK page states you can launch an app. Any plans of integrating this?
Thanks for the great binding
After Switching to openHAB 2 i have a problem that is related to the problem i had before under oh1. The first Connection succeded. After Restarting the TV it doesnât reconnect. In the Logs there are some errors. Maybe you can use the Log to Debug my Problem.
Hi, well, checked the log⊠but does not give me any hint. this null pointer exception happens deep in smart home code during the thingUpdate execution. Donât think any of the parameters the binding hands over are null.
btw. I donât think OH2 is quite production ready yet⊠At least I personally have not yet switched. Only have a test instance running right now.
Many thanks for this addon, Sebastian! Iâm using it since some months now w/o any problem.
Just your hint for powering up the device doesnât work for me. Wake-on-LAN does not seem to be supported on my device (tested with command line tools). At least, I canât find a setting for this in the webOS menu. Do you also use it on a 2014er WebOS model like me or did you test your addon on newer devices only?
I have a menu entry under general settings to allow mobile devices to start the TV. This had to be enabled.
I own this model: LG 60UF7709. OS Version shown in Info Menu on TV is 4.00.70
Interestingly the version reported through the API on response to hello command is different:
Same here. I have a WebOS2 2015 model 32lf652 with no option of wol.
I also wonder. After almost every power on the tv keeps asking to allow connection. Is it possible to get rid of this?