More "Something Went Wrong" Issues

If you didn’t reboot the router while the Sonos devices were powered down, you may still have network issues.

Beyond that, since I’m certainly not having this issue, I’d also try, at least temporarily, wiring one Sonos device to my router, to see if that helps. I wouldn’t use a surround speaker or a Sub, though.

I’d also call Sonos Support directly to discuss it.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system

Having to shut down my whole network, unplug all my speakers, and then restart my whole network just to Band-Aid Sonos’ networking issues is not a reasonable suggestion or solution. Despite that, it seems to be their solution for everything. I have contacted support since the update, and as expected they said I had to do this. Usually this does at least fix things for a little while, but this time it had no effect.

FWIW, I did previously have one of my players wired and was told by Sonos support to change it to wireless instead - they said this was bad advice and hasn’t actually helped anything in a long time. I find this funny/sad because it was Sonos support that told me on yet another previous call that I had to wire one of my players for things to work reliably - for the record, that didn’t help anything.

I have not yet managed to talk with anyone at Sonos support who did anything beyond reading me useless (and conflicting) scripted responses. I guess you have better luck than I do when you call in.

Try setting static IP addresses for all your speakers. I did just that a long time ago and have not had any of the issues you have described.

That’s interesting. I’ve been told several times it’s not possible to set static IPs on Sonos devices, and I’ve not found a way to do so. How did you go about it? Are you actually talking about DHCP reservations? If so, that’s not the same thing and I’ve already done that.

Since we, like you are just users and have no ability to force Sonos to fix anything all we can do is offer things that have been found to work. I’m sorry you don’t find that reasonable but it has helped a large number of folks that have come here for assistance to get their Sonos working. I’ve put a lot of hours into finding a better solution or even just getting a clear description of the IP issues, failed at both. So I’m left with the less than great options offered here.

Sonos uses DHCP to fetch IPv4 addresses so reserving them in the router's DHCP server is what has to be done.

I understand we are mostly just users here. I posted in the community to share my experience and add my voice to the chorus calling out the [many] issues. The only way we can possibly get Sonos to fix things is by drawing enough attention to the problem(s). If I just keep calling support and getting nowhere it doesn’t help anyone - they certainly don’t care about us individually, but hopefully they’re not foolish enough to ignore the health of their user community.

My frustration on the total network restart is with Sonos giving that as their official “solution” to seemingly any issue. How is that reasonable? “We understand the car we sold you doesn’t work - just close the highway for a while and then it’ll probably start again. Also, we’re not going to help you any further until you do so.” Many users and/or environments don’t have that option and/or access to do so. I would segregate the Sonos onto their own network so I can script crashing it on a regular basis, but the requirements of the clients being on the same network as the players breaks that idea. Sonos have also chosen to use a non-standard multicast relay setup so we can’t just route the traffic as we would with similar products either. And the way they do DHCP for stereo pairs / surrounds / subs is so hilariously broken you can’t pass their DHCP requests through a gateway reliably…

I am already using DHCP reservations for both my players and my controllers. Actually, just about all of my network devices have reserved addresses - makes logging and scripting easier. Restarting everything as prescribed has not helped with the current crop of "Something Went Wrong" issues, nor has uninstalling & reinstalling the app. I’ve also tried removing all my libraries and re-adding them, along with trying a factory reset on a couple of the more problematic speakers - also no improvement. I’m not sure what changed in the latest release (the release notes are basically useless), but something has clearly gone awry. I understand it’s not affecting every environment, but a quick Google search shows it’s clearly not just me or my systems.

Sorry for the long post and frustrated tone. It’s just so sad to see this happen to a company whose products I’ve been using and recommending for years. Not to mention how much of my own money I’ve invested in the platform only to have it “upgraded” into uselessness. 

This is of course totally unacceptable. They are trying to make their problem to our problem.

Just sayin' - I am still on old firmware and all works great. No network issues at all. And all the nice old features available... But I'm afraid that they will sooner or later force me to upgrade the firmware.