Yes it does. No issues at all.
Ok, I’m going to peel this off to a DM to avoid spamming people’s inbox any more. I have a jar I want you to test with that may answer some questions. Standby.
I’ve pushed version 0.06.2 (1fa8869). This should fix the IPv6 issue @michaeljoos and force it only to IPv4.
I can confirm that auto discovery now adds IP4 to Hostname 
For anyone who is not able to connect to their Shields after the PIN process, use the goggletv thing instead of shieldtv. Use the latest binding published by morph as it solves a previous issue with ipv6 being used instead of ipv4, which did not allow connection to the Shield.
Let’s not get too hasty on this. The difference between the two is that shield adds the extra protocol stack on top of the google stack. There’s many benefits to that protocol, like the ability to control the apps. In not entirely sure why it’s not working on your shield but I’d still like to figure that out. I can say that it does work on a variety of shields so please don’t just abandon that piece.
I’ve sent you a message. Whenever you have the time to answer I will then follow through with the testing.
One thing I still find strange is that prior to the addition of the Google TV function I wasn’t having any issue. This led me to the conclusion I reported above.
Yeah I’ll reply in a bit. Need more than my phone to send. Proper response.
I’m a little confused as to why the addition of google impacted you. The code isnt even in the same folder. Basically we just now flip both on at the handler. I see the stack working as I’d expect with the keepalives and some other commands. I’m sure it’s just a protocol issue at this point. Probably a flag we’re missing.
Ok did some testing here. I’ve got 1fa8869 loaded onto my two OH here (production and dev). I completely wiped all of my certs and restarted the binding to make it fresh. I was able to authenticate both shield and google without issues. So for the moment I’m going to assume that the code is working as expected at least for my model. I’ve got the 2017 models running Shield 9.1.1 / Android 11. I do see one small issue in the code that I’ll correct, but it shouldn’t be impacting anything (it causes a reconnect to happen on shield minutes after the binding fires up if the PIN isn’t executed).
@Norixone I’m going to write up the instructions to test yours as soon as I’m done with this. I wanted to get a sanity check done here to see if I hosed up something on my end and broke what was working here.
I’ve posed 0.06.4 (2d02a80) which should fix the issue that was causing the reconnection I mentioned above. I think this could have been responsible for the PIN issue @Norixone as it from what I’m seeing in your logs you were getting a reconnection between REQUEST and putting the actual PIN in. That reconnection will cause the PIN process to fail. This should fix that. Also to note, you only have 60 seconds from REQUEST to when you enter the PIN before the shield rejects the entry. You won’t get an error when this happens, you will just have it quietly fail and need to be run again.
@morph166955 I confirm it is working although only after second attempt. See the message I have sent to you .
1 Like
Glad to hear it! So as far as I’m tracking, no one is reporting any issues at this time.
For the non shield users, can you report in with make/model/os version so we can track it? Thanks!
I have this working on a DirecTV Stream device (C71KW). Only using keyboard channel so far (that’s all I need). Seems to work great. Set up was a bit of a struggle, but finally got pin code to work.
Awesome! Can you elaborate on the PIN issues?
Not exactly sure what the issue was, but i couldn’t get the pin code to take. I then tried on another server running 4.0 and it worked. Then I went back to my live environment running 3.4 and it worked. In the middle of all that I removed a chromecast binding that I wasn’t using, but it seemed the discovery was the same as your binding. Also had a second TV that went fine, but I removed that Thing thinking it may have been a conflict. All that to say I don’t know exactly what corrected the problem, but it worked out in the end.
So to be clear, you tried multiple times on the 4.0, it failed. You went to the 3.4 environment, it worked. Then you went back to 4.0 and it worked?
The chromecast binding uses the same mdns fqdn to identify the devices (unfortunately they are all the same). @rpwong have you had any issues lately, I believe you have a few chromecasts using both bindings.
I didn’t have any issues with the PIN and I don’t recall needing to disable my Chromecast binding/things. Aside from setting up the POWER channel to trigger my Harmony Hub, I haven’t had time to play around with the AndroidTV binding.
Opposite. Tried multiple times on 3.4 and failed. Tried 4.0 and it worked. Went back to 3.4 and it then worked.
I also have a Formuler Z8 that has not worked.
What android version does it run?
Do you have Google Video installed and updated?
Does the Google Video app on your phone connect successfully? If so, does the PIN have a colon in it?
Looks like version 7.0. I don’t have Google video.