Sonos Speaker Login
strickersuk opened this issue · comments
The problem
Hunting around looks like I'm not the only one, getting these errors in the log:
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:125
Integration: HTTP (documentation, issues)
First occurred: 08:26:19 (55 occurrences)
Last logged: 12:36:03
Login attempt or request with invalid authentication from 192.168.86.1 (192.168.86.1). (Linux UPnP/1.0 Sonos/68.2-29160 (ZPS27))
Login attempt or request with invalid authentication from 192.168.86.1 (192.168.86.1). (Linux UPnP/1.0 Sonos/68.2-29160 (ZPS12))
Login attempt or request with invalid authentication from 192.168.86.1 (192.168.86.1). (Linux UPnP/1.0 Sonos/68.2-29160 (ZPS19))
What version of Home Assistant Core has the issue?
2022.5.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
Sonos
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?
No response
Additional information
No response
Hey there @cgtobi, @jjlawren, mind taking a look at this issue as it has been labeled with an integration (sonos) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
sonos documentation
sonos source
(message by IssueLinks)
There shouldn't be a reason the Sonos devices themselves should be trying to reach the HA frontend port unless you're playing local media or using TTS.
Any chance you have another device on the network that integrates with Sonos like a Fritzbox?
Possibly the Google/NEST mesh network?
Not sure. It seems like something is proxying these requests as they're all coming from 192.168.86.1 and the model number keeps changing. Is that your router's address?
It is yes, I have multiple Sonos speakers hence the different model numbers I think? Are these the user agents for the speakers?
Yes. However it seems the router is the source of these messages and is not caused (or can be fixed) by the Sonos integration.
Finally tracked down what was happening and have resolved it. HA is running under https on my own domain so all requests route from the internet. This was causing issues with Sonos trying to resolve device locally, I've resolved it using AdGuard and a DNS rewrite.