Good evening
My sonos devices keep going unavailable. It happens every minute and strangely it seems to almost always happen at 49 seconds into the minute. I see that more people are having issues but i cannot for the life find out what is happening in my installation specifically. All i see in the logs is:
2025-07-05 19:31:00.837 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities media_player.badkamer_sonos, media_player.keuken_sonos, media_player.slaapkamer_sonos_bed, media_player.woonkamer_sonos_bureau, media_player.woonkamer_sonos_klok, media_player.woonkamer_sonos_televisie are missing or not currently available
This leads me to believe it is a connection issue. Althought i have had no issues whatsoever in the past. It didn’t start with a specific update for as long as i can remember, and i have not made changes in my network at home.
I have already set the speakers to a static IP but this has not solved the issues.
Any help is greatly appreciated. I am fairly new to this so if you could run me through the steps to get the debug info needed that would be greatly appreciated
did you find out why? Mine started doing this after I updated to the latest HA version
Same thing here. Any time I try to send anything to it, it will go unavailable until I reboot the sonos.
I have tried a lot of things but still run into this issue. Have not been able to fix it sadly 
Same here - the sonos are on the network, they show up in ssdp and can be pinged but they don’t seem to become accessible until I launch the sonos app on my phone.
Make sure you have uPnp enabled on the Speakers.
I figured out the issue. It is not uPnp or network but we had 2 Sonos accounts and 2 systems. Disabling the system with the second account fixed the issue. Traced down several similar issues in github and few odd warnings in the logs, the HA Sonos implementation doesn’t support multiple “households” aka Sonos accounts and it seem to take the first one basically.
Yes, that is not supported. That said, we should have better detection of the issue. I believe in manifests primarily when alarms are configured on the speakers. Open a GitHub issue and I’ll add code to detect the problem to make the next persons life easier.
It would be nice to have a clear warning on this. I did have a look at the soco library, technically it seems to be able to support multiple households but not sure there is a clear way to find them.
Anyway, I can create a new issue if that helps but this is an old one with exactly the same issue Sonos integration with multi houseId’s · Issue #89300 · home-assistant/core
Please create. I’ll work on it.
The root issue is in SoCo there is an alarm singleton that exceptions when there is more than one household. That is what prevents the integration from loading. I could not find a simple way that wasn’t a breaking change (meaning breaking the soco api), to have more than one list. Happy for help.
So the Soco constructor has an optional household parameter but I’m not totally sure how that one is used or if it would prevent that exception. Wondering if there is any chances this would avoid the alarm issues. Ideally, could HA have the household id as part of the device?