Apple TV advertising remote on unreachable IP

pug306d commented 3 years ago

The problem

When trying to setup the forked-daapd integration HA detects an Apple TV for OwnCloud called LS.IO Music, when I try to configure it though the pairing fails as OwnCloud is trying to connect to the wrong IP for HA.

Owncloud is also running in docker but on a different host, the container has an IP 192.168.1.10 so I expect it to connect to HA using 192.168.1.81 but it is trying the docker IP 172.17.0.1

I logged this with OwnCloud as I would expect its more efficient to use the IP in the local VLAN but they say HA should not be broadcasting these IP's

https://github.com/owntone/owntone-server/issues/1311

What is version of Home Assistant Core has the issue?

2021.9.5

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

forked-daapd

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

[2021-09-10 09:51:30] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX at 192.168.1.81:59015, paircode XXXXX
[2021-09-10 09:51:30] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX) at 192.168.1.81:59015, paircode XXXXX
[2021-09-10 09:51:31] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX) at 172.30.32.1:59015, paircode XXXXX
[2021-09-10 09:51:31] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX) at 172.30.32.1:59015, paircode XXXXX
[2021-09-10 09:51:32] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX) at 172.17.0.1:59015, paircode XXXXX
[2021-09-10 09:51:32] [ LOG] remote: Discovered remote 'pyatv' (id XXXXX) at 172.17.0.1:59015, paircode XXXXX
[2021-09-10 09:52:27] [ LOG] remote: Pairing failed with 'pyatv' (172.17.0.1:59015), no reply from Remote
[2021-09-10 09:52:27] [ LOG] web: JSON api request failed with error code 400 (/api/pairing)

Additional information

No response

probot-home-assistant[bot] commented 3 years ago

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

probot-home-assistant[bot] commented 3 years ago

Hey there @uvjustin, mind taking a look at this issue as it has been labeled with an integration (forked_daapd) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

uvjustin commented 3 years ago

The is probably from the apple tv integration, not from the forked daapd integration.

probot-home-assistant[bot] commented 3 years ago

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

probot-home-assistant[bot] commented 3 years ago

Hey there @postlund, mind taking a look at this issue as it has been labeled with an integration (apple_tv) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

postlund commented 3 years ago

This will be fixed at some point when I migrate to python-zeroconf as Home Assistant can determine what interfaces to announce on. Currently all are considered.

postlund commented 3 years ago

I'm adding support for specifying which addresses to listen on/broadcast during pairing, which means I can pass the addresses configured in Home Assistant (the network integration). I'm hoping to finish it within the next few days and have it incorporated in the beta component (https://github.com/postlund/hass-atv-beta).

pug306d commented 2 years ago

I tried the new beta but could not see how to specify the address that is advertised - could you let me know? Thanks!

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

pug306d commented 2 years ago

@postlund is this fixed in the new release? I could not see how to set the IP? Thanks!

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

pug306d commented 2 years ago

Still an issue…

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

pug306d commented 1 year ago

Still a problem in home assistant 2023.1.4

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

pug306d commented 1 year ago

Still an issue…

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

pug306d commented 1 year ago

Still an issue with 2023.7.3

home-assistant / core