Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Apple TV advertising remote on unreachable IP

See original GitHub issue

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

Issue Analytics

State:
Created 2 years ago
Comments:12 (3 by maintainers)

Top GitHub Comments

1reaction

postlundcommented, Oct 19, 2021

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).

0reactions

pug306dcommented, Jun 10, 2022

Still an issue…

Top Results From Across the Web

If your Siri Remote or Apple TV Remote isn't working

Restart your remote If your remote still isn't working as expected, try restarting your remote. Press and hold the TV/Control Center button and ......

Why can't the Plex app find or connect to my Plex Media Server?

App Is Remote from the Server. If your app is not on the same network as your Plex Media Server: Ensure that Remote...

Network Troubleshooting Guide - Savant Knowledge

The Savant App generates a Network Unreachable Error when the Savant Host is having trouble communicating with the local Wi-Fi network. This error...

How to Fix Problems with the iPhone Remote App - Lifewire

On Apple TV, go to Settings > General > Network > Wi-Fi and select the correct network. Restart the router. If you have...

Troubleshooting (When Running Firewalla)

Not able to see network traffic? · Make sure the box monitoring mode is on. · If you are in DHCP mode, likely...