That’s interesting. Any chance of a network issue? IO Error generally implies that it can’t connect to the device. Just to confirm, you’re on the most recent version posted correct? Is the device wired or wireless?
No concerns for me, but I do have a question: will app control be possible with Google TV, or will that remain read-only?
I’m not too concerned about it, which is why I haven’t asked before. Sorry if I’ve missed seeing a previous post addressing it. This thread has gotten a bit long. 
I’ve posted an updated jar v0.10 (5eb0a06). This is likely the last jar prior to the binding being merged into 4.0. It should be completely stable. It includes the commits from the review, please report any regressions.
@rpwong my apologies I didn’t see this message. The problem is simply that I don’t have any frame of reference for what the commands needs to be to do that. The protocol stack supports it. If I can figure out what the commands are, it’s a very trivial amount of code to add to the binding.
1 Like
No worries. Maybe add it to the wish list and we can talk about it in the future? Like I said, I’m not too concerned, but if it’s possible we might as well look into it. I’ll help you as much as I can.
Thanks!
Both are listed at the bottom of the main post.
1 Like
Maybe you can get a hint from Philips TV Binding?
The app control worked for me with this binding. I know it’s Philips specific, but maybe this can give some direction?
1 Like
Unfortunately, it’s two different protocols entirely. The same problem holds true with the Sony TVs.
That said, given that we have the structure already to handle multiple protocols (like Shield), I have considered adding specific thing types for those with that separate protocol channel to handle the stuff GoogleTV doesn’t. I’ve been holding off on that until we merge in as I really don’t want to introduce any additional complexity to the binding before it’s merged. Given that the other bindings do exist though, I don’t have a reason to not pull (part of) them in at a later time to handle the specific things that we can’t do today. It would be one at a time obviously as we slowly integrate them.
2 Likes
First I need to commend you on this binding. Looks great and hope I can get it working on my side.
Having some issues with the pin as it does not appear on my tv as expected. I have a Xiaomi Mi Android TV stick (year: 2022, model: MiTV-AYFR0)
Steps I followed:
- Updated .thing file to include googletv and updated to my IP address.
- Added the Google_TV items to my .items file.
- Installed the AndroidTV binding from the Main UI menu.
- Discover the things. 2 Things appear namely GoogleTV and Mi TV Stick.
- Both Things are offline at this stage.
- Send the following through the CLI: openhab:send GoogleTV_PINCODE REQUEST.
Below the openhab.log file.
2023-04-27 10:59:00.120 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:00.132 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:00.623 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:00.624 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Opening GoogleTV SSL connection to 192.168.1.12:6466
2023-04-27 10:59:00.634 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:00.720 [DEBUG] [l.googletv.GoogleTVConnectionManager] Assuming server certificate is valid
2023-04-27 10:59:00.721 [TRACE] [l.googletv.GoogleTVConnectionManager] Subject DN: CN=atvremote/soul/soul/MiTV-AYFR0/10:38:1F:3B:73:C5
2023-04-27 10:59:00.722 [TRACE] [l.googletv.GoogleTVConnectionManager] Issuer DN: CN=atvremote/soul/soul/MiTV-AYFR0/10:38:1F:3B:73:C5
2023-04-27 10:59:00.723 [TRACE] [l.googletv.GoogleTVConnectionManager] Serial number: 1635909714552
2023-04-27 10:59:00.723 [DEBUG] [l.googletv.GoogleTVConnectionManager] Returning empty certificate for getAcceptedIssuers
2023-04-27 10:59:00.764 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Message reader thread started 6466
2023-04-27 10:59:00.765 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Command sender thread started 6466
2023-04-27 10:59:00.778 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - GoogleTV PIN Process Incomplete
2023-04-27 10:59:00.779 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - startChildConnectionManager parent config: 6466 NORMAL false
2023-04-27 10:59:00.780 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - startChildConnectionManager child config: 6467 PIN false
2023-04-27 10:59:00.786 [TRACE] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Initializing SSL Context
2023-04-27 10:59:00.791 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Message reader thread exiting 6466
2023-04-27 10:59:01.137 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:01.265 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:03.146 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:03.647 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:04.283 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:04.652 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:04.788 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:05.154 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:05.666 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: true - Logged In: false
2023-04-27 10:59:05.793 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:06.672 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:06.797 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:07.176 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Opening GoogleTV SSL connection to 192.168.1.12:6466
2023-04-27 10:59:07.290 [DEBUG] [l.googletv.GoogleTVConnectionManager] Assuming server certificate is valid
2023-04-27 10:59:07.292 [TRACE] [l.googletv.GoogleTVConnectionManager] Subject DN: CN=atvremote/soul/soul/MiTV-AYFR0/10:38:1F:3B:73:C5
2023-04-27 10:59:07.294 [TRACE] [l.googletv.GoogleTVConnectionManager] Issuer DN: CN=atvremote/soul/soul/MiTV-AYFR0/10:38:1F:3B:73:C5
2023-04-27 10:59:07.295 [TRACE] [l.googletv.GoogleTVConnectionManager] Serial number: 1635909714552
2023-04-27 10:59:07.297 [DEBUG] [l.googletv.GoogleTVConnectionManager] Returning empty certificate for getAcceptedIssuers
2023-04-27 10:59:07.299 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:07.340 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Message reader thread started 6466
2023-04-27 10:59:07.341 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Command sender thread started 6466
2023-04-27 10:59:07.347 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - GoogleTV PIN Process Incomplete
2023-04-27 10:59:07.348 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - startChildConnectionManager parent config: 6466 NORMAL false
2023-04-27 10:59:07.349 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - startChildConnectionManager child config: 6467 PIN false
2023-04-27 10:59:07.352 [TRACE] [l.googletv.GoogleTVConnectionManager] theater - Initializing SSL Context
2023-04-27 10:59:07.356 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Message reader thread exiting 6466
2023-04-27 10:59:07.802 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:07.842 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:08.304 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:08.846 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:09.351 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:10.357 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:10.860 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:11.363 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:11.823 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:12.374 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:12.426 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: true - Logged In: false
2023-04-27 10:59:13.379 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:13.428 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:14.385 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:14.432 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:14.934 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:15.155 [TRACE] [.androidtv.internal.AndroidTVHandler] theater - Command received at handler: pincode REQUEST
2023-04-27 10:59:15.156 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Command received: pincode
2023-04-27 10:59:15.157 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Command received: pincode
2023-04-27 10:59:15.391 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:15.436 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:15.893 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
2023-04-27 10:59:16.440 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
Hope someone can help. Thank you.
@jabez01 Thank you for giving it a try! I have a few thoughts
- Please confirm you have GoogleTV installed on the device. The link is on the main thread. When we see “Online: false” that means that we are having an issue opening a basic connection to the device.
2023-04-27 10:59:00.120 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Device Health - Online: false - Logged In: false
2023-04-27 10:59:00.132 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Device Health - Online: false - Logged In: false
- It looks like you have the same IP address configured for 2 devices. Do you have multiple things configured?
2023-04-27 10:59:00.624 [DEBUG] [l.googletv.GoogleTVConnectionManager] 10381F3B73C5 - Opening GoogleTV SSL connection to 192.168.1.12:6466
2023-04-27 10:59:07.176 [DEBUG] [l.googletv.GoogleTVConnectionManager] theater - Opening GoogleTV SSL connection to 192.168.1.12:6466
- Is everything on the same network or do you have VLANs/firewalls/etc?
Hi!
Thank you very much for the awesome binding and for sharing your hardwork. I really apreciate it.
Here goes my feedback, Everything works perfect and as expected in my Nvidia Shield except for one thing. I realize that for most people using openhab and this binding the intended use case is to exclusively use a mobile device as their remote controler. For me however that is not the case I use openhab to have an API and do some automations but I still use my Harmony remote control and some time the nvidia remote controler.
The problem is that when I do a search in my Shield it no longer lets me use the on screen keyboard. It keeps telling me to use my device’s keyboard. This only happens if and when openhab is using this binding. Is there any way you could think I could fix this?
@morph166955 thank you for the quick feedback. About the questions:
- I have ‘Google Play Movies and TV’ installed. From an earlier message in this thread I believe I have the correct app.
- I have only 1x thing in my Things file:
Thing androidtv:googletv:theater [ ipAddress="192.168.1.12" ]
However, 2 Things were discovered namely GoogleTV and Mi TV Stick (10381F3B73C5). I also tried to connect with both running (as per the openhab.log I posted) or either one of them disabled.
- OH and the device are on the same VLAN.
Can you check on the UI to see if any of the discovered ones were added on there? Also, can you confirm you have the right address configured? It’s definitely duplicating something somewhere.
I’m intrigued by the issue. I actually use the Neeo remote or habpanel on my side, not the app. Can you try to change the thing to be googletv instead of shieldtv. Im curious which connection is causing the issue (assuming its not both). We emulate two different apps, sounds like we found a conflict.
I don’t know about others, but I hate using mobile devices (and touchscreens in general) as remotes. So, I wouldn’t make that assumption.
I use my Harmony Hub remote regularly and haven’t run into this problem (I just checked to be certain).
Is openHAB supposed to show up as a keyboard when you use the shieldtv thing? I checked the Remotes & Accessories settings in my Chromecast with Google TV, and I only see the Harmony Hub keyboard and my Chromecast remote.
Sure thing!
I tried with both and this is how it goes
Test 1:
Initial state : On my Shield I go to search and the on screen keyboard shows up
- Scan for things, two things showed up (Google and Shield)
- I add Shield
- In shield go to search, on screen keyboard shows up but as soon as I use it this happens (even before PIN initialization):
Test2:
Initial state : On my Shield I go to search and the on screen keyboard shows up
- Scan for things, two things showed up (Google and Shield)
- I add Google
- In shield go to search, on screen keyboard shows up and stays on
I cant just use the Google thing because the PIN Channel initialization wont work
Things I have tried to fix the issue with the SHield thing:
- Look for a remote in the devices to remove, nothing shows up there
- Select GBoard as default Keyboard
- Kill Android Remote Services
None has worked so far. Something keeps taking over on screen keyboard
Something I noticed is that when the THING is created. Can setup my default keyboard to be GBOARD. for a few seconds everything is fine…but as I am typing something GBOARD disapears and Im back to “Use the keyboard in your device”. At that point I go and check and the default keyboard has changed:
Im troubleshooting my issue and Ive done soooo many experiments. I actually have 2 OH servers at the moment to test different scenarios. One thing I noticed is that at some point one server was finding my Android TV with a scan while the other just wasnt.
After restarting OH in the one that wasnt I was able to find it with a scan. That might solve your issue
Just make sure you delete -everything- you already created, Thing, equipment in the se,mantic model, links even uninstall the binding. Restart OH and start from scratch. Also turn off and on your android TV before you start
The app channel is read-only for Android TV devices. At this time you can only send to Shield devices.
1 Like
A few ideas/notes:
- You won’t have to do pincode if you name the thing the same thing
e.g. androidtv:shieldtv:livingroom vs androidtv:googletv:livingroom. Once you do it once, it will keep based on the room name. - Try to do the pair without the search window up. It may be blocking it.
- There is actually a KEYBOARD channel, not sure if you can implement with that somehow but I did build that in to help with searching.
- Can you send the output of
openhab> openhab:things list | grep android
openhab> openhab:items list | grep android
I’ve not built any custom widgets or dealt with them, so not 100% sure what I’m looking at with what you posted. I do see a few things that I’m not 100% sure about. For KEYCODE, you need to make sure you are sending the keycode number that translates to what you’re trying to do (see the link in the first post to the readme which has the code list). Also note, different devices accept or ignore different buttons (all depends what the specific vendor implemented). @rpwong is correct, as it sits today app is readonly except for shield devices. We hope to have that readwrite soon, but we don’t have the specific command to do it nailed down yet.
1 Like
Thanks for following up!
- You won’t have to do pincode if you name the thing the same thing
e.g. androidtv:shieldtv:livingroom vs androidtv:googletv:livingroom. Once you do it once, it will keep based on the room name.
Not sure what you meant by “You wont have to do pincode” but I tried adding the Thing with the google binding and it shows offline. Did you mean it should be online ? (so now I have 2 things one online with shield binding and one offline with google binding)
- Try to do the pair without the search window up. It may be blocking it.
Ive tried that. if use the thing androidtv:shieldtv PINCODE works if I try androidtv.googletv PINCODE doesnt work
- There is actually a KEYBOARD channel, not sure if you can implement with that somehow but I did build that in to help with searching.
Not sure what to implement with those. What Im trying to do is to keep using the on screen keyboard so that I can use NVIDIA’s remote controler
- Can you send the output of
sure thing!
openhab> openhab:things list | grep android
androidtv:shieldtv:fee5e1e9 (Type=Thing, Status=ONLINE, Label=SHIELD, Bridge=null)
androidtv:googletv:48B02D36B215 (Type=Thing, Status=OFFLINE: GoogleTV: PIN Process Incomplete, Label=SHIELD, Bridge=null)
I dont have any items greping with android because I named my thing SHIELD, but with SHIELD I have items for every channel:
openhab> openhab:items list | grep android
openhab> openhab:items list | grep SHIELD
Harmony_Hub_Current_Activity (Type=StringItem, State=SHIELD TV, Label=Current Activity, Category=, Tags=[Control, Current], Groups=[Harmony_Hub])
SHIELD_Keycode (Type=StringItem, State=NULL, Label=Keycode, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_Keyboard (Type=StringItem, State=NULL, Label=Keyboard, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_Key_Press (Type=StringItem, State=NULL, Label=Key Press, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_App_URL (Type=StringItem, State=http://192.168.1.104:38615/com.teamsmart.videomanager.tv, Label=App URL, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_Player (Type=PlayerItem, State=NULL, Label=Player, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_App (Type=StringItem, State=com.teamsmart.videomanager.tv, Label=App, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_Pin_Code (Type=StringItem, State=NULL, Label=Pin Code, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD_Power (Type=SwitchItem, State=ON, Label=Power, Category=Switch, Tags=[Switch, Power], Groups=[SHIELD])
SHIELD_Mute (Type=SwitchItem, State=OFF, Label=Mute, Category=SoundVolume, Tags=[Switch, SoundVolume], Groups=[SHIELD])
SHIELD_App_Name (Type=StringItem, State=SmartTube, Label=App Name, Category=, Tags=[Point], Groups=[SHIELD])
SHIELD (Type=GroupItem, Members=11, State=NULL, Label=SHIELD, Category=, Tags=[Equipment], Groups=[LivingRoom])
SHIELD_Volume (Type=DimmerItem, State=100, Label=Volume, Category=SoundVolume, Tags=[Control, SoundVolume], Groups=[SHIELD])
To be clear this is just the current state, of course to try sending Pin_Code request via the googletv thing I created an item and link first. I just deleted it for now
Additionally, I would try to debug the binding and figure it out. I managed to compile it already but having problems installing it. After adding the jar file to my addons folder nothing happens I dont see the binding 
is there anything else I need to do to make that work?
[ EDIT ] I figured the binding is not supposed to show up as installed. I get however some errors in the logs:
17:04:03.456 [ERROR] [Events.Framework ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.androidtv [250]
Unresolved requirement: Require-Capability: osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))"
at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) ~[org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) [org.eclipse.osgi-3.17.200.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) [org.eclipse.osgi-3.17.200.jar:?]
Not a clue what am I doing wrong
What version of OH are you running?
Try to name it “androidtv:googletv:fee5e1e9” instead of 48B02D36B215. It will force it to use the same certificates. Also, don’t forget, you need to update the channel name on the items when you change the thing as well.