-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonos Integration throws an error: "Login attempt or request with invalid authentication from sonos IP" #110654
Comments
Hey there @jjlawren, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) sonos documentation |
Please post the log files that show the error |
error_log.txt Sure. Here we go... |
Thanks, this is a duplicate of Please review the info there and comment on the specific of your situation and/or if the workarounds work. Let's close this issue to consolidate everything into 88714 |
Same issue Any idea on how to fix this? |
Look at #88714 |
The problem
Sonos Speakers throw an error quite often of beeing unable to connect:
home assistant Login attempt or request with invalid authentication from sonos IPADRESS See the log for details.
This leads to oa lot of unnecessary warning messages in Home Assistant System. So far most of the times they keep working, or a power cycle of HASS helps. Not a good solution but works. Please also see here: https://community.home-assistant.io/t/constant-invalid-authentication-from-sonos-devices-in-logs/442328/20
What version of Home Assistant Core has the issue?
core-2024.2.1
What was the last working version of Home Assistant Core?
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
The text was updated successfully, but these errors were encountered: