Scope_ID is still not given in SSDP

[cociweb]

The problem

a long lived error messages in the logs which still floods it. There is no clue where is it coming from, and why:

After restart/initialization:

Logger: async_upnp_client.ssdp
Source: components/ssdp/__init__.py:350
First occurred: 22:24:55 (2 occurrences)
Last logged: 22:34:55

Received error: [Errno 1] Operation not permitted, transport: <_SelectorDatagramTransport fd=29 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=29, family=10, type=2, proto=0, laddr=('::', 42817, 0, 0)>

During working time:

Logger: async_upnp_client.ssdp
Source: runner.py:188
First occurred: 22:25:41 (26 occurrences)
Last logged: 22:38:11

Received error: [Errno 1] Operation not permitted, transport: <_SelectorDatagramTransport fd=122 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=122, family=10, type=2, proto=0, laddr=('::', 53382, 0, 0)>

The ports are various. There is no further logs, and it makes me upset only, not experienced any malfunction.

What version of Home Assistant Core has the issue?

supervised, version: N/A

What was the last working version of Home Assistant Core?

N/A

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

ssdp

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

There was 2 similar (or same?) issue in the past, but no real resolution found and their fix did not eliminate the above mentioned errors. https://github.com/home-assistant/core/issues/81459 https://github.com/home-assistant/core/issues/86631

[home-assistant[bot]]

ssdp documentation ssdp source

[issue-triage-workflows[bot]]

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.

[cociweb]

it's still problem on 2024.4.2.

[home-assistant[bot]]

Hey there @stevenlooman, mind taking a look at this issue as it has been labeled with an integration (upnp) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `upnp` 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 upnp` 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)}}

---

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

[StevenLooman]

Thank you for this issue @cociweb. I didn't see this issue as it didn't have the upnp or ssdp label. You state that you are running supervised thus I am assuming you are not using Docker or HAOS. Thus, you are managing your installation yourself.

Is HA running with elevated privileges? It seems that it can find the proper addresses (with a scope_id), but it cannot (is not allowed to) send anything. Or perhaps a firewall is preventing this.

What do the network settings report? You can view these via Settings --> System --> Network.

[StevenLooman]

Did you manage to get the network settings, @cociweb?