You do know you can opt out of updates and have your system on a old version?    It does mean as an iOS user if you buy a new phone or reset you phone you will not be able to use it on you Sonos system with the Sonos app.  There may a 3rd party app you could use though.  Apple doe not allow more than One app per application so there is no opportunity to keep old versions available.

This is a tough one for any wireless speaker company,  If you want people to use their phones/tablets as controllers then you have the consequences of Phone software and firmware issues to deal with, and the relentless retiring of products that still function perfectly enough.

Just another point you need to be aware of…

You can refuse to accept an update as mentioned by @bockersjv so long as you do not try to add another Sonos speaker or change networks. Doing so will force the update. 

Thanks for the feedback. I did have the automatic s/w update option set so that did leave me open to the problem.  However my understanding from what I see on my wife's iPad plus the conversation I have with Sonos support leads me to believe that not upgrading is not an option that will work in the medium to long term - you are forced to upgrade after a while. So I'm back at square one. I know if I had to reset the iPad for any reason then I'd have no choice but to install the latest version but while it is working I would have liked the option of not upgrading and the choice in knowing the pros and cons of doing so.

Dealing with software and firmware issues is pretty much the same whatever h/w you use and knowing the limitations and consequences you face by not upgrading ought to be a choice the user can make.

Hi, thanks for the feedback. Based on the experience as describe in my original post and the conversation I had with Sonos support the option of not accepting an update is, at the very least a short term option. At some point you are forced to accept one. I'd made no changes to my speaker set up or my network. It still comes down to enforced updates removing or depreciating existing functionality.

it would be nice to have the official take on this whole process direct from Sonos, especially as to why users can't choose to become ‘unsupported’ if they wish to retain existing functionality with all the pro’s and con’s that would entail.

Sonos don’t like people running unsupported software versions or networks (e.g. EoP adaptors). However, if you really want to, and are willing to accept the drawbacks, then they can’t stop you - as long as you lock the system down before anything bad happens. Once any part of your system is updated, then it’s already too late - with Sonos, there’s no going back - ever. It’s just the way they do business.

It’s easier to do it with non-Apple kit, as you have more control over it,  but my understanding is that it should still be possible. There was a very helpful document written by a member here a little while ago. If you can’t find it (the search here is terrible) then PM me and I’ll send you a copy. I found it invaluable.

Locking out auto updates doesn’t work for the desktop apps, or for the CR200.  Could someone post the ‘hidden’ document describing how to do this at the router level? 

I’m happy to put it up somewhere. I’m afraid that I can’t ask the authors permission, though, as their name isn’t on the document and I can’t remember who wrote it. Back soon….

My belief is that the original author was kind enough to help other Sonos users, so would probably not object to further distribution of this helpful document. If I’m wrong, then I’ll take it down without question.

This is the main document :-

http://www.amun.org.uk/Sonos/Sonos%20Lock%20Down%20Procedures.pdf

and this is a list of ports that Sonos uses - or did when it was published :-

http://www.amun.org.uk/Sonos/Sonos%20ports.txt

The main document refers to locking down at v8.4, to avoid bricking CR100 controllers, but the same principles apply to later versions - e.g. I was locked down at v9.1 and now again at v10.4

Some routers do not support all of the necessary security features. As I don’t use the radio or streaming facilities - and just want to carry on playing my own music from a NAS - I’ve locked down the update port (4444) on all devices on my network, and locked off all access to the internet on all Sonos players.  

Thanks!

There’s loads of info on web for opening ports for the tp-link Archer C8 router, but nothing on closing ports!  Grrr!  The Firewall settings are simply on or off!   Grrrr.

I was amazed at how limited many modern routers are - they are so biased towards simplistic home use that they are effectively toys. I ended up buying a VR2800, which does have the necessary facilities, but one of their cheaper models also does the same thing. Took ages to work out which ones would work, as TP-Link just gave misleading info.

Thanks Amun, a nicely written and very useful doc, it should save a lot of pain in the future.

@alastair h 

I just wish I could remember who wrote it, to thank them….

I’ve managed to block the websites, but can’t find any way to block the port alone.  Grrr.

If you don’t use the internet facilities (e.g. radio) then most routers will let you black-list devices. Before I managed to find a router that did all that was needed, I got everything working and then black-listed all sonos players and bridge - so that they couldn’t access anything. A very OTT solution, but it kept my system safe for a while.

As I still don’t use the radio side, I now simply lock off all Sonos devices from all ports - slightly more subtle that the above, and more easily switched off if I need to.