-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
Unable to Add Roku Television #74712
Comments
roku documentation |
Hey there @ctalkington, mind taking a look at this issue as it has been labeled with an integration ( |
I began having a similar issue with the integration already installed after updating to 2022.7. Removed integration to attempt recovery and now unable to reinstall. Thanks for any input edit: forgot to mention TCL 55" (55R625) |
@jayjaytay I'd be curious to see the result of: http://DEVICEIP:8060/query/apps (try in web browser when device is on) |
@skyegalen if it's the apps for you too, please try above url in browser as well. Otherwise advise new issue with your error output |
side note: I believe the root cause is newer xmltodict in recent versions of HA. they changed from OrderedDict to dict and that threw off some parsing from what I'm seeing. hope to have fix in next minor release of HA 2022.7 |
Thank you for the quick repair! |
The problem
I own two Roku TVs (a newer, 75" TCL, and an older, 55" Insignia). The Roku integration in Home Assistant can see the 75" TCL just fine, but trying to add the 55" Insignia, I get an "Unexpected error."
What version of Home Assistant Core has the issue?
Home Assistant 2022.7.1
What was the last working version of Home Assistant Core?
Home Assistant 2022.6.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Roku
Link to integration documentation on our website
https://www.home-assistant.io/integrations/roku
Diagnostics information
config_entry-roku-0d916486f0ac2ac41c53a61fcea95fab.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: