It’s only been 5 weeks, they need more time to not fully beta test the next release /s

It’s been over 6 weeks after the update. The real problem is sonos’s lack of communication and transparency. Sonos said “upcoming” which was very confusing because we though it be in 14.14 but then when it came out nothing was there. All they gave us was a temporary solution and no release date  or estimates. 

That’s okay, consider yourself lucky, the latest update completing borked my system today.

All of sudden, Sonos had no awareness of anything - none of my hardware, none of my music library, playlists, favorites, nothing.

I sincerely hope that the Sonos Dev team is having a really nice long weekend because I spent the better part of Saturday effectively rebuilding my system, one component at a time. Well, almost.

I got to unplug each device and re-initiate the adoption process. I mean, what’s better than a breaking change that actually makes you power cycle everything, right? And, as a valued customer, I guess I deserve special treatment by having to do this seven times. How much fun is that on a Saturday afternoon? I guess my use case is an outlier for their Product Managers - I just want to play music.

So, finally after getting all of the hardware update and setup (again), and having to re-adopt (or whatever) the hardware to my account, I try to reconnect my music library. Which, of course, doesn’t work. Trying to do this from the Windows app, yields the following helpful error message:

Notice something?

Yup, those hard working Devs just copied the error message from the mobile app and pasted it into the Windows app, which of course has a different menu structure. But why bother with any form of useful doc or release notes when the system is so darned intuitive? And why bother with QA when you can push out amazing updates instead?

I anticipate that the standard response from Sonos Support will be that, despite buying into the Sonos Boost mythology,  I have some form of wireless interference in my network. Interference which magically allows me to use streaming services like Spotify as a source on their system just fine, but won’t keep a sustained connection to my NAS via Samba.

I mean, SMB clients are super exotic pieces of code which have not been around for years and require huge amounts of highly advanced network engineering to develop. And things like inadequate cache size or timeout constraints would never get in the way in an ancient, hardware-constrained system. Especially if that RAM could be better utilized by amazing updates. 

Of course, all of this used to work just fine.

Like a good piece of IoT kit, Sonos used to be just like appliance - it worked when I needed it to, didn't get in the way, and didn’t require much care and feeding. Ah, the good old days. After seven years of pretty much flawless operation for me, Sonos has become like Hotmail - great when there weren’t other options, but now racing towards terminal obscurity. 

Will I ever get this (now) PoS working again? Who knows. I’m going on vacation for two weeks and will either attempt to troubleshoot or just bin the whole cluster f*** when I am back.

But there is zero chance that I will ever recommend this system to anyone I like ever again. Sonos took a long-term customer of some very pricey hardware and screwed the software until it was most def not an appliance. Sadly, they have become another piece of IoT roadkill.

But congrats to the Dev team for pushing out this release and I hope that they really enjoyed their weekend!

Several inaccuracies in your comments. First, Sonos did not push out an update today. You may have chosen to install it today, or yesterday, but it was released several days ago. 

The Sonos devs didn’t ‘copy’ the same path. The Sonos controllers, both desktop and mobile versions, are merely windows to the data/application that runs on your speakers. So any ‘error’ they’re reporting is an error from your speakers, and would be the same error shown on any controller connected to your Sonos system. There is no ‘different menu structure’, it’s the same from all controllers, reflecting the perspective of the software running on your speakers. 
 

I’ll leave it at that. If you’re actually interested in fixing your system, you probably should contact Sonos directly. If you’re merely interested in complaining, you’ve done that, and I am sorry you weren’t able to resolve your issues in a manner that pleased you. I hope you enjoy your vacation. 

Bohemian,

Factory reset might accidentally improve something for a while, but it does not fix fundamental issues, and usually wastes a lot of time.

To me, the original issue suggested a duplicate IP address. Factory Reset of the SONOS system will sometimes clear this, but there is no guarantee. Powering down everything on the network then restarting in the following order is a better plan. Restart in the following order:

Modem or Gateway
Router, if any
Network switches, if any
Wired SONOS
Wireless SONOS
NAS
Everything else

Wait for each step to complete before moving to the next step.

Now, you should “reserve” (some routers will call this “fix”) IP addresses for all regular network clients.