To give everyone an update, there are some changes coming in the next few days/weeks on this binding.
First, sooner than later PhilipsTV will be added in. There is a test jar floating around in a separate thread if anyone is interested, fair warning they are very alpha and not working properly just yet. Once it’s stable I’ll be posting it here.
Second, and probably more impactful, it looks like there were some upstream dependency changes which is going to make the hybrid jars really hard to build regularly. I’m going to fork off 3.x to a separate thread shortly and release much less frequently there (major bug fixes and security fixes only). It’s likely PhilipsTV and any new/emerging features will be a 4.x only a little sooner than I had thought.
I have a Sony Bravia and didn’t get it working. I got always the error Message GoogleTV Error Message 95:
The PIN Login seems to work well, but thats all.
Here are my trace, maybe this helps or someone can help me to get my Sony working with openhab.
There is a pending PR right now that resolves this issue and I’m working on a new marketplace drop which will include it as well as the PhilipsTV protocol.
I’ll be updating the main thread to include either this jar or one very close to it in a few days. This in theory should be compatible with 3.x. To note, there is a dependency on upnp now because of PhilipsTV. This is satisfied either by having another binding that uses upnp installed (e.g. sonos or upnpcontrol), or by adding the necessary jar files to addons.
Please let me know if you have any issues, or more hopefully successes!
I am VERY pleased to announce the addition of the PhilipsTV protocol to the AndroidTV binding. For those who haven’t been following the other thread, the binding was originally written in 2019 by bennYx0x. The original author (whom credit is duly given) is no longer able to support it directly and it was never merged into the code base. As the Philips TVs since ~2016 have been AndroidTV based it naturally fit inside of the AndroidTV binding. The code was adapted and added in a similar way to the ShieldTV.
Some things to note:
KeyPress now has a fall through mechanism to support both the main GoogleTV interface as well as the vendor specific interfaces. For example, you can still type KEY_UP, or you can use any of the commands here: https://jointspace.sourceforge.net/projectdata/documentation/jasonApi/1/doc/API-Method-input-key-POST.html on the Philips TV. The binding will first check against the GoogleTV command list, and if nothing matches it will pass the command along to the vendor protocol.
There is a condition observed when powering on the Philips TV using the Wake-on-LAN function where the TV may not power up after coming out of low power mode. In some cases it takes the TV as long as 20 seconds to wake up which is beyond the current timers. The fix to this is to simply send the power again when the thing comes back into an online state. This is a todo item that I hope to have fixed in the next few days.
The App channel is not yet normalized for PhilipsTV versus ShieldTV in respect to starting an app by name. On ShieldTV, this channel accepts the “com.google.android.youtube.tv” reference where the PhilipsTV accepts the “YouTube TV” reference. This is also an open todo item. Eventually, both bindings will accept the “com.xyz” on the App channel and “App Name” on the AppName channel.
There is a significant amount of code changes that have been made between this version and the current merged version. At present there is approximately 5700 lines of new code with changes to both GoogleTV and ShieldTV. Please report any issues so we can resolve them before this gets merged.
With the addition of PhilipsTV we now add a requirement for upnp. There have been instances where users have reported an exception because “org.openhab.core.config.discovery.upnp” is missing. There are two ways to resolve this. 1) Install another binding that uses upnp, this will install the proper dependences or 2) Install the jupnp.org and org.openhab.core.config.discovery.upnp jar files for your specific release. As this changes per OH release it’s not possible for me to build a kar that would work for everyone (from what I understand at least).
In respect to the hybrid 3.x/4.x jars, they seem to be working again for the moment after some trial and error. This is getting more and more complex as 4.x updates dependencies. As I’ve said before, my goal is to keep the hybrid jars until 4.1 is released and then sunset if that’s possible. Once that happens, I will likely transition the marketplace to only include new features that are not merged into the current snapshot and release one final 3.x jar that aligns with 4.1 release. If the hybrids break again, we may just be stuck
@morph166955 I am having an issue with OH 3.4.5 I no longer see the binding in the binding list nor as an available binding in the openhab distribution. Is there any issue with this version of OH? Do you have a copy of previous jar files I could simply add in the addons?
Thank you for your help and great work.
My issue was caused by two problems: the firts the authorisation to the folders (I had to restore my OH 3.4.4 backup as OH 4.1.0 M1 is still having issues with the Sonoff binding) and the second the market place itself. Tried this morning upgrading the AndroidTv binding (I am on July 6 release) and although it seemed to have installed, the Shield was no longer working, so simply copied the old binding in the bundle folder and all went back to normal.
I haven’t changed that in a year now minus moving 4.0 to 4.1. There was a few issues posted about the marketplace having issues, not sure what the fix was.
Right, but now OH 4.1 snapshots and milestones are released. That version range will definitely exclude all the 4.1 versions I think (IIRC the ) is exclusive not inclusive). The snapshots and milestones are not treated as < 4.1.0.
This binding works exactly the same on all versions from 3.2 through 4.1. Marketplace is confirmed to be working on all versions of the marketplace through the most current snapshot of 4.1 as well.
For anyone who is tracking the PhilipsTV updates, I have submitted the PR for review in hopes that we get it merged in for the 4.1 release later this year.
1 Like
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
520
I finally set this up with 3 Nvidia Shields and I have a couple issues.
After rebooting OH, the Google PIN process on 2 of the units is needed again and the Google Thing is OFFLINE. Even though it says it’s logged in after the reboot.
My oldest Nvidia Shield doesn’t react to the Google PIN process. It’s running 9.1.1 version of the OS. I have confirmed Google TV is installed on this device via my phone seeing it.
I’m running this version of the binding → 4.1.0.202308281751
I would need to see a debug log to see what’s happening. What version of OH are you on? Login showing successful is the trigger for the device to go online. What is the thing status saying?
As far as the old one, please make sure it’s updated. Are you getting any error messages? If you are getting one that says the following then you are running an old version of the googletv protocol.
Just to mention that some AndroidTV have 6467 actively blocked (like mine)
Its a Hitachi branded cheap QLED AndroidTV. GoogleTV is installed and running while pairing request but LAN scanner shows 6467 as blocked.
Anyway, the only purpose to connect to the TV was to get a status whether to turn on/off background light. I can do this with network availability, so no big thing for me.
