Open mfort01 opened 5 months ago
Thank you for this issue @mfort01. The ssdp
component is both used for announcing the Home Assistant presence on the network and listening for any UPnP devices (such as, as you mentioned, DLNA devices, IGD devices (routers, upnp), ...).
Given the log entries before the ERROR
s, I do think the error originates from the announcing the Home Assistant presence. It also appears that it is related to the IPv6 address ::
, on the fd=91
socket.
I'm not entirely sure why this is happening. Can you elaborate a bit more on your set up? Like, are you running HAOS, from a container, VM, ...
And is there a firewall preventing sending any packets?
I had what looks the same problem and solved it for me. In my 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.
The problem
While looking in home-assistant.log for error messages related to another issue I found that the Async UPNP advertisement service repeatedly erroring (approximately every 30 secs) upon sending SSDP packets. I just yesterday had pulled the latest container version and updated to 2024.5.5 (had been on 2024.1.x). Not sure if its related though as I'd not looked at the log file for months.
While trying to troubleshoot I did enable UPNP on my router and it was found nearly immediately as a potential service in HA, so appears the device discovery side of things is working. Quick scans through documentation for the handful of integrations I'm running doesn't suggest any are using UPNP (i.e. no DLNA devices or integrations installed)
Happy to provide any additional info/debug outputs upon suggestion.
HA configuration.yaml logger config logger: default: error logs: homeassistant.components.ssdp: debug async_upnp_client.ssdp: debug async_upnp_client.server: debug async_upnp_client.traffic: error
Docker-compose.yml configuration homeassistant: container_name: homeassistant image: "ghcr.io/home-assistant/home-assistant:stable" volumes: - ./homeassistant:/config - ./etc/localtime:/etc/localtime:ro - /run/dbus:/run/dbus:ro devices: - /dev/ttyUSB0:/dev/ttyUSB0 restart: unless-stopped privileged: true network_mode: host
What version of Home Assistant Core has the issue?
core-2024.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Unknown
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response