Open cgoudie opened 1 week ago
Hey there @tronikos, @drafteed, mind taking a look at this issue as it has been labeled with an integration (androidtv_remote
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
androidtv_remote documentation androidtv_remote source (message by IssueLinks)
Can you try the following from the documentation?
If you are not able to connect to the Android TV device, or are asked to pair it again and again, try force-stopping the Android TV Remote Service and clearing its storage. On the Android TV device, go to Settings > Apps > Show system apps. Then, select Android TV Remote Service > Storage > Clear storage. You will have to pair again.
Trying these steps has no impact on the SSL error. Tried on another nvidia shield also, same result.
Try deleting androidtv_remote_cert.pem and androidtv_remote_key.pem in config/.storage
Try deleting androidtv_remote_cert.pem and androidtv_remote_key.pem in config/.storage
This trick did it for one, but not for both. The other one now reports "already_in_progress" . I did a bunch of googling, but I'm not sure what to clear or delete to make this work.
On the SSL topic, maybe it would make sense to auto-delete this key file if it's not valid.
Can you try adding to your configuration.yaml
:
zeroconf:
ignore:
- androidtv_remote
Regarding the pem files, I think it makes more sense to automatically delete them once the user removes all entries to make sure the user starts fresh.
Can you try adding to your
configuration.yaml
:zeroconf: ignore: - androidtv_remote
I tried but...
Invalid config for 'zeroconf' at configuration.yaml, line 16: 'ignore' is an invalid option for 'zeroconf', check: zeroconf->ignore
Regarding the pem files, I think it makes more sense to automatically delete them once the user removes all entries to make sure the user starts fresh.
Maybe use a lazy strategy? If the user is setting up android_tv, and there are no current devices, and the file exists, delete and recreate before setting up the first one.
Somebody else added this zeroconf workaround in the documentation but it doesn't seem to work. I'll remove it from the documentation.
Can you enable debug logs and post logs? Can you also follow the steps in https://github.com/home-assistant/core/issues/109314 and run demo.py from the underlying library?
Somebody else added this zeroconf workaround in the documentation but it doesn't seem to work. I'll remove it from the documentation.
Can you enable debug logs and post logs? Can you also follow the steps in #109314 and run demo.py from the underlying library?
Actually... that zeroconf above is so bad to the config that it keeps zeroconf from loading, and I was then able to add it by hostname, then fix the config and zeroconf loads. 🤦
The problem
I can see others have the integration working, but I wonder if I'm the first to set it up recently. I have developer options enabled. Debugging turned on. Network debugging turned on.
What version of Home Assistant Core has the issue?
core-2024.7.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
androidtv_remote
Link to integration documentation on our website
https://www.home-assistant.io/integrations/androidtv_remote
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response