[async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable

[izab (Isabella Borgward)]

[There doesn’t seem to be a networking category or tag, so sticking it here.]

HA 2024.5.1 running in Docker on Debian.

My logs are spammed with this, every 30 seconds.

2024-05-28 20:49:23.051 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=24 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=24, family=10, type=2, proto=0, laddr=('::', 56238, 0, 0)>
2024-05-28 20:49:53.052 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=24 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=24, family=10, type=2, proto=0, laddr=('::', 56238, 0, 0)>
2024-05-28 20:50:23.053 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=24 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=24, family=10, type=2, proto=0, laddr=('::', 56238, 0, 0)>

There have been some issues on Github that were auto-closed without a fix.

async_upnp_client errors

UPnP: continious errors in logs

A few discussions about it, eg

Lots of errors in the logs after moving to new home

Hi all, I’m not sure where all the errors come from that I’m seeing in the logs. I recently (two weeks ago) moved to a new house and not everything is set up properly again. I unfortunately even had to swap my router, but the WiFi and the LAN that my HA and all other device are/would be connected to are still the same because I’ve split internet router and my local network to two different hardware devices, the latter still being the same. So I’m seeing now an immense amount of this error (66,…

again, no real conclusion, just dies without answer.

I am not sure when it started. I really don’t look at the logs very often.
The only thing I can see in HA that isn’t working, is a Bluetooth adaptor [that I don’t use]. Many of the integrations I have use networking, and work fine.

If I understand correctly, some part of Home Assistant is trying to listen on :: [any IPv6 address]. In issue 69669, chishm inferred that " ('FF02::C', 1900, 0, 2)" meant interface #2. So from “(‘::’, 56238, 0, 0)” I would infer that it’s referring to interface 0, but interfaces are numbered from 1 on Linux! So what is it really doing?

[izab (Isabella Borgward)]

I had to restart the container for an unrelated reason, and these events have stopped.

[Edwin184]

I had what looks the same problem and solved it for me.
In my HA configuration I had a static IP address defined and have made a address reservation in my Deco. However what I found was that the MAC address on the address reservation in my Deco was not the same MAC address as my Home Assistant has.
So I corrected this everything is working fine again.

[wfox]

My HA is running on a Raspberry Pi. This error happens to me from time to time without any changes to the network or any integration.
When it occurs, access to HA via the mobile interface on a local network is unavailable, but it works when I connect via VPN.
In some cases, the connection returns locally after a few minutes. In others, I have to restart HA (turn off and on the Raspberry Pi), because I don’t know how long it will take for the connection to recover.

** In the case of pint, I had to connect using Tailscale to access the error log.