Setting up android tv remote works, but stops working after a little bit, and reports a different IP address then used for setup

borgqueenx commented 2 days ago

The problem

Android tv bridge cannot connect to my nvidia shield. it works for some seconds, then a bit later it reports that it couldnt connect to "ip address here", and i have to retry. During manual setup, i selected the ip address of the shield, enter the code i see on screen and then connects without issue. The issue is, as soon as it reports that it failed to setup and being tried again, the IP address noted here is different then the one i used to set up the nvidia shield. And the nvidia shield has a static IP address. I checked the router to see what IP address the integration android tv remote wanted to connect to, and it's my android phone.....??

Wiping the data and cache of the remote service on the shield is not working, the issue comes back fast.

What version of Home Assistant Core has the issue?

core-2024.9.3

What was the last working version of Home Assistant Core?

core-2024.9.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

android tv remote

Link to integration documentation on our website

https://www.home-assistant.io/integrations/androidtv_remote/

Diagnostics information

please let me know how to get these if available, there is no button to download diagnostics at this integration, it seems.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 2 days 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!

Code owner commands

Code owners of `androidtv_remote` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign androidtv_remote` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

androidtv_remote documentation androidtv_remote source _{^{(message by IssueLinks)}}

Drafteed commented 2 days ago

Could you disable the zeroconf integration and check if the issue persists?

borgqueenx commented 2 days ago

how do i try this? i see removing the default config from configuration.yaml could work, but then it disabled a whole load of standard loaded integrations. Is this issue already known at zeroconf developers?

borgqueenx commented 2 days ago

i made a issue for zeroconf as well. hope this can be solved some time :)

borgqueenx commented 1 day ago

yesterday, i re-added it again and instead of manual discovery, were sure to manually select the IP address. I see the error is different now, then when i automatically added the device. It simply now says that authentication expired. i cleared the data of the android system app android remote two days ago, so it seems that was not a great help either.

Would this still be related to zeroconf then?

home-assistant / core