-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device discovery and Roku TV #139
Comments
Based on this comment andrewsayre/pysmartthings#63 (comment), there's no screen Id or lounge or anything. |
That’s very interesting, that would explain why auto discovery magically didn’t work for me when I tried to use it a couple weeks ago. Thanks for making such a detailed issue |
I've been trying to figure out how the |
I didn't have time to do a capture, but I tried to understand the lounge/dial better. It turns out it is normal for the DIAL info of the app to not contain additionalData at all. I think in some way, if the TV is already in a lounge, it might return My understanding is the lack of https://github.com/patrickkfkan/yt-cast-receiver is a good resource to test against actually, and I understood some of the ins and outs better because of it. |
I found myself fiddling with DIAL and lounge API, so I thought I'd share a couple of findings
So we get the response from SSDP discovery:
Right, so hitting the location (
http://IP:8060/dial/dd.xml
), and we need to read the response headerApplication-URL
. Interestingly, the value for me isAs you can see, there's no trailing slash, which might be causing an issue here
I guess the issue here is that we need to check for a trailing slash, and if it's not there, add it.
Next, when hitting
http://IP:8060/dial/YouTube
, it gets blocked (403) if you do not add this exact origin headerThe response headers contain
So I guess that's something that needs to be added to the request here.
Finally, here's the content of
http://IP:8060/dial/YouTube
So this is strange, since there's no screen id and no lounge id here. So this could cause an error.
Anyway, these are some observations, perhaps they are reasons why the discovery is not working for some people.
The text was updated successfully, but these errors were encountered: