Ok folks, the moment everyone’s been waiting on is here! The googletv protocol stack is close to baked. I have a few small things to tweak in but it’s looking good (THANK YOU @mhilbush).
I’ve also just merged the googletv stack onto the shieldtv thing. So what does that mean. All of the things available on the googletv protocol are now available on the shieldtv. Like power, volume, mute, google keycodes. All of it.
You may notice that your thing status is offline because GoogleTV is waiting for a PIN. To use this, you must run the PIN process TWICE for a new device. So request, pin, request, pin. If you had already done the PIN process for the shield and are upgrading the jar, you should only have to do it the one time for the googletv side. The on screen displays should look very different between the two. The first is authenticating shieldtv, the second is googletv. You should see the thing status tell you when the first comes online. Once both are hooked you should go ONLINE.
Add the power, volume, mute channels. Power and mute are read/write. Volume (for the moment) is read only (I’m still working on the command to set the volume, hopefully this is soon). The binding will know which protocol to send commands on.
For users who are here just for the GoogleTV stack (anything that isn’t an Nvidia Shield), just replace shieldtv with googletv and you’re good to go. You only do the PIN process once. Also note, APPNAME and APPURL don’t work as we don’t get an APPDB from googletv. Also, starting apps by sending a command isn’t working yet for you. That’s hopefully coming with the volume control once I figure out what the correct syntax for the command is.
I can confirm that the mDNS errors are gone on both of my Chromecasts with Google TV (HD and 4K). When I deleted my things, they popped up in autodiscovery and I didn’t have to go through the PIN process again.
The APP and POWER channels are working, but I haven’t tested anything else.
It seems like @morph166955 has posted a new binding and mine stopped working as usual. I have used the command you have given me and this is what it returned:
274 │ Active │ 80 │ 4.0.0.202302171450 │ org.openhab.binding.androidtv
After posting the above I tried to uninstall the binding and found that there was no new version. Therefore, I downloaded the jar file and put it in the addons, but don’t seem to be able to display it in the bindings.
I then stopped the container and restarted to check if the binding became available, but to no avail. I looked at the Shield in things and found it to be online and fully functional, despite having unistalled the binding. I then run the command line again and this is the result:
277 │ Active │ 80 │ 4.0.0.202302171450 │ org.openhab.binding.androidtv
Another thing I cannot understand is why despite having the Sonoff binding up and running, since I have installed it it does not appear in the binding menu. Any clues?
So thats interesting. I haven’t updated the main thread yet so absolutely nothing should have happened. Thats still the jar from the main thread, not the new one I posted last night. I’d open an issue on github for one of the developers to look at this.
Hey @michaeljoos! Thanks for trying it out. I would try to not use the port number in the configuration. It looks like that could be related to something Philips specific. The binding attempts by default to connect to the googletv video server on port 6466 which should be standard across any googletv installation. What you should see is a connection attempt to 6466, a rejection for certificate_unknown, and then a connection attempt to 6467. At that time you should be able to send REQUEST to the PIN channel and get a code. Once you submit the OSD code to the channel you should see the connection to 6467 close and a new connection to 6466 open. Assuming everything works, you should see a ton of messages back and forth indicating that PIN was successful. The thing should also come online at this time.
I’ve updated the main thread with the googletv version and I’ve pushed the changes into the PR so everything is nice and tidy now. Marketplace should update from this.
Interesting. Your TV isn’t spitting the normal certificate_unknown error. Can you please make sure you have updated the google video app on your tv (or confirm it’s installed)? If so what version is it on?
Also to note the getAcceptedIssuers being empty is absolutely normal and expected.
Under addons I have two folders. One named shieldtv and the other androidtv. Is that normal?
Again the ShieldTV is not connected and I receive an ERROR:HANDLER message on the state of the device. I used the command provided by @mhilbush and this time the prompt returned no message.
I then installed the new binding and the Shield turned to OFF LINE. In “things” the INBOX diplays the Shield as it has to be installed.
It had various keys. I have deleted the folders suspecting that this could be part of the issue I was having. I am now proceeding with a fresh re-install and configuration of the Shield. I will finish tomorrow if possible as here it is 22:30 and have another long busy day tomorrow.
Perfect. That’s what im running. I’ll go look in the code to see where this is stalling out. We look for a specific error to fire the PIN connection. It could possibly be the android version. Ill get back to you once I can align the errors to the code.
Were the folders in addons or just the generic userdata folder? We did change the folder name when we went from shieldtv to androidtv for the keystores. Otherwise the binding jar should just be in the addons folder, no sub folders I’m aware of (unsure if the marketplace creates folders or not).
NICE! I’ll see if I can write something into the binding to account for devices that don’t send the traditional certificate_unknown that we’ve been seeing (this is what usually triggers the PIN pieces we had to use FORCE for).
As for WOL, what’s the use case in respect to this? We maintain a connection to the device when it’s in a “powered off” state, which is more exactly a standby state. Does the Philips kill the connection when it’s powered off? I don’t see why we couldn’t do some kind of WOL functionality, but I’d like to understand how it applies.
