Forcing Updates

It’s a pain in the a**, friends come round you switch on Sonos and guess what you can’t play any music, it worked fine the day before but not now. The system does not NEED an update, the update might help but it’s not NEEDED, please give us the option to update when we’re ready.

You're not forced to update*. Disable the update check in the system (which BTW doesn't automatically update, it just notifies that an update is available), and ensure that Sonos apps on iOS/Android don't automatically update from their respective app stores.

If you don't prevent the controller apps updating they'll go out of step with the player firmware, which will then usually require a system update before you can play anything. This is because controllers and players must be at compatible versions.

(*Except when you add a new unit to the system.)

Totally agree with these comments. These forced updates are driving me nuts. Almost chucked a Sonos across room. Can never just turn the damn thing on to listen to music when i want to.

I generally prefer genuine replies. You are surprised that I didn't mention any of those things? I'll tell you why, because I've owned Sonos since 2013 and I have NEVER had any of these issues until the last 15-months or so... specifically when Sonos made the decision to start adding voice capabilities to the speakers.

I have a degree in computer science and I can eventually fix most issues... so your items 1.-5 are all in play and all things that I have leveraged to get the system back up and running once it goes down. But I have to tell you... I didn't buy these expensive speakers to spend a hour trouble shooting, rebooting and/or contacting customer service (by the way...just try...try...try to speak with an actual SONOS customer service rep). If anyone chooses to go that route, put on a pot of coffee... its going to take awhile.

I'm really really surprised that your approach to dealing with these matters is to point customers to technical solutions.... solutions that WERE NOT required just a year or so ago. If SONOS had started out this way, it would have failed day-one.

What I've noticed from this forum are more defensive "'redirects" instead of addressing the issue full on.. My post was specifically addressing the "forced upgrades" matter which Ken's response above totally ignored and quite frankly, I'm not sure you can because its tough to reconcile the corporate party-line with the consume reality. Beyond the scripted responses, I can tell you that you have a problem that's becoming more and more prominent.

A Bed Time Story: Once upon a time a company called Microsoft had an operating system called "Windows XP". I just worked. Then they decided they need to come up with solutions to problems that didn't exist. They pissed off so many loyal customers that they turned in mass to a tiny company called Apple which delivered a computer and operating system that did what it was supposed to do, Customers raved and a star was re-born.

No, the router loses track because an update causes the Sonos to reboot and get a duplicate IP address from a wonky router. The controller is a very dumb application, all the information is stored on the Sonos units themselves. If the controller cannot reach the Sonos units, then it cannot retrieve any information about the Sonos unit.

Do a network refresh. Reserve IP addresses for your Sonos units so they never again get a duplicate. 99.99% of the time, this fixes what you are seeing.

This thread is fascinating. Sonos techs say the updates are not forced yet, multiple customers are telling you that forced updates are absolutely happening.... and I hate to tell ya, but they are being forced. Initially the updates are suggested but after awhile you are absolutely forced to update else no response from the controller.

This has happened to me multiple times. I have 2 controllers (one on the laptop and one on Andriod phone). Auto update is off and after a disaster update last week, I now have another update that I "should" implement. Of course I would never volunteer for the pain of losing the system/music with the update on my own, but rest assured, in some near-term date, the controller will stop working unless I update. Sonos...this is real and the stale response that updates are "not forced" is absolutely not true. Maybe you should say "Not forced Initially...".

You could greately simplify customer pain and possibly retain the Sonos panache if you simply let sleeping dogs lie for legacy systems and update those newer systems where, for some unknown reason, users want to talk to their speakers rather than listen to them.

Google has been brilliant with this. 2 years updates for their flagship phones then the madness stops. My old Pixel phone (backup) works great, no update hassles and all the apps are still working in their legacy stage. So so so simple.

Sonos you would do well to avoid repeating the Microsoft fiasco whereby the forced updates and implemented useless features that caused all sorts of customer grief .... eventually sending customers into Apple's open arms.

I just bought a vacation home in South Florida. SONOS will most definitely not cross my front door threshold.

Sonos can contine to blame customers for not being technically savvy or what have you...but there are significant problems with the update process, policy and approach and I think pointing the finger at customers is a HUGE mistake. Yesterday I spoke with my cash...i just ordered a $4K sound system for my vacation home and I never thought I'd say this but.... Sonos not in scope. I also ordered a homepod for my 86yo dad so I don't get calls from him ranting about updates and Sonos not working. Good luck


Good luck with your new purchases. Horses for courses applies.

You can likely solve your update hassles by assigning static/reserved IP addresses to your Sonos gear from your router's DHCP page. Usually fairly quick to do, follow by unplugging your Sonos gear and rebooting the router. Plug in any wired Sonos devices one at a time, give it about a minute between each one, then the wireless ones, again one at a time.

If you turn off update notifications you might want to manually check for updates every month or two so you don't get too far behind.

I don't think, 'making it simple' is really a viable option. Sonos functionality/requirements around IP addresses has not changed over the years. What has changed is the volume of devices in a typical home that utilize a wifi network (and volume of wifi networks in general). If all you have is a couple computers along with your Sonos, the odds of running into IP address conflicts are very low. But today, we have dozens of devices in the home that use IP addresses and thus the odds of conflicts are a lot higher.

Can Sonos somehow maintain the same stable multi-room audio system and change it's use/dependence on non-conflicting IP addresses? I don't know.

SONOS should be able to make it simple.
I have a network with quite a few devices. I like playing with computers and automation systems. I have never, even with multiple SONOS speakers, ever had any IP address conflict problems. Almost all, but not all, of my systems use DHCP, some have reserved DHCP addresses. If you are having issues with IP conflicts, then you may need to look at how you are handing out IP addresses. If you have systems with statically defined addresses within a DHCP range, that is a problem. Also check your system that is handing out addresses, if it get confused about who has what addresses that is also a problem. DHCP has been around for a long time and just plain works if it is configured correctly. If you are having problems with address conflicts, then the DHCP configuration needs to be checked.


I'm confused. You're having trouble with speakers disappearing after an update, which is usually do to IP address conflicts, but your familiar with the issue? Have you setup reserved address for your Sonos speakers (not static, but reserved)? If you do have reserved addresses and you're still losing speakers on updates, then it's a different issue. Submitting a diagnostic after the next update could help.


One underlying desire that I have for all systems, is to make them simple to use. If my wife takes more than a couple clicks to get what she wants done, it will get tossed away.
If an update requires me to reconfigure the system, I get very upset.


And that's reasonable. I do think that one downside to all the emerging tech around voice control, smart speakers, and IoT in general that it's too complex right now. That's due to emerging tech, integrating of different products, and so many products potentially on a network.

Not having reserved IP addresses is still likely to bite you when you finally do run an update and also when the router and/or Sonos gear reboots due to a power glitch or other reason.

I finally gave in and did the IP assignments after getting tired of power cycling after every storm.

Updates are not forced, only suggested. You can also turn off the update suggestion or with a bit of work block the updates if I understand some of the other posts on updates.

Not just you but anyone (visitors) with access to your WiFi that has an updated controller can be a problem if you don't want to update.