Leaving this posting to help other folks as I didn’t find any Google results for the “Failed to request visible zones” error.
For months, my Sonos configuration worked great. At some point, various entities started throwing errors. In a fit of random troubleshooting, I deleted the Sonos integration, and then re-added it. Unfortunately, after re-adding it, no devices or entities were discovered by the integration.
I then manually added the Sonos IP addresses in the YAML configuration file, but that didn’t resolve the problem. The log file showed various error messages complaining stating that the integration “Failed to request visible zones” from each Sonos IP address, along with “UPnP Error 501 received.”
I have 22 Sonos clients on my network, so I thought perhaps I had crossed a threshold of too many devices at some point. But then I started to suspect perhaps my old Sonos Playbar, recently added to the network, might be the culprit. It is compatible with Sonos S2, but, sure enough, once I removed the Playbar—boom, the integration started working again (after a restart).
So if you find yourself in a similar situation, try removing older Sonos gear from your network.
I’m in a similar situation with a lot of Sonos devices, except I have no older Sonos gear… I got rid of all that when I went to S2. The oldest Sonos device I have on my network is a Sonos One.
Do you think there could have been anything else you did that fixed the issue at the time and you thought it was the Playbar removal?
One thing I have noticed going through different threads on this issue is that everyone who experiences it seems to have a large Sonos network, and some people seem to have a network built on Ubiquiti UniFi devices… me included.
For anyone else that comes across this since it seems to be the first hit when searching for this error…
I was receiving the same error after doing the exact same thing (removed and re-added the Sonos integration). All of my devices are new. I resolved the problem by power cycling most of the Sonos gear. I have 28 total Sonos devices, and 21 of them (20 amps, 1 port) are in the same wiring closet on the same power strip so it was relatively simple to reboot those. By the time I got back downstairs to my computer, the integration had already discovered all of the devices.
Might be worth a try for anyone with the same problem.
Good to know but let us know if it comes back… mine has seemed to resolve itself or be resolved by rebooting Sonos devices only to come back a few minutes, hours, or days later. I can usually adjust the volume of a Sonos device without causing the issue to come back, but interacting in other ways like pausing, playing, or selecting new media usually makes it come back.
If it continues to be a problem for you, please add a comment to the issue below on Github I created. Sonos is a core part of my system and it would be so nice if I could get it to work with HA reliably.
So, just for “fun” … I tried removing the power to all Sonos devices again and the system did work for a while. But, as soon as I had to restart Home Assistant a little while later, none of the Sonos would come back as working again.
Please do let us know if this resolved it permanently for you. Maybe I just need to put a zigbee switch on every Sonos device to regularly power cycle the entire Sonos network until this is more permanently fixed.
Also, maybe a few more details about your system would help?
Are all off your Sonos products wired (the ones that can be)? Do you still have wireless turned on even if they are wired?
Do you by chance have any Ubiquiti network equipment? Have you configured the settings for STP that Sonos recommends and set the STP priority of your switches?
I feel like I’ve tried everything to make this more reliable and it’s really hard to find other people that have as many Sonos products as we have (which I believe is part of the “problem”). I even called Sonos about this, and besides telling me that they couldn’t help… the rep also told me my problem was that my system was “too big” even though I’m far below the limit of 32 Sonos devices. I was quite surprised… especially with how much their products cost.
Don’t get me wrong, I still love the system. But, I love it a little less than when I first started using it almost twenty years ago.
Hopping in here - same issue. I’ve added some of my logs to the GitHub thread. Also Ubiquiti network equipment, setup with STP and configured properly. I haven’t messed with my network settings in a while, nor added Sonos devices, and it’s been working fine for over a year until now. My devices are on a different VLAN, with IPs specified in my configuration.yaml (though I’ve deleted the integration and rebooted with this commented out, which did not help). My sonos are connected over SonosNet with a bridge and most devices hardwired via ethernet.
I have not attempted to powercycle devices as it requires moving furniture and getting a ladder out, but I’ll be attempting that in the next few days if it doesn’t magically fix itself by then. I’ll try to provide any useful info on GitHub that’s requested in the meantime.
After a lot of trial and error I believe we found the root cause of this issue, you can check the github issue for more details. But, hopefully, the developers of this integration will be able to fix this.
I get the UpNp error when trying to group a older device with my newer… Older one being Sonos Play 5 Gen 1, paired with a newer IKEA Symfonisk speaker.
Should this not work due to different sonos controllers? I dont get why that would be a problem trying to group the speakers toghether in HomeAssistant using custom Sonos Card from HACS.
Other speakers can be grouped together no problem…
… I tried removing the power to all Sonos devices again and the system did work for a while. But, as soon as I had to restart Home Assistant a little while later, none of the Sonos would come back as working again.
