Cannot add a Sonos player to a system that I’ve kept on S1

Attached is a Mac screenshot though; does not the PC controller have a similar S1 designation?

Sorry I was confused as you jumped into someone else’s thread. Your Mac S1 app looks just like the PC S1 app. What is the problem then? If you want to move to S2 you need to install the S2 app. If you want to stick with S1 (which i recommend personally) then you are set.

The matter that needed clarification was the quoted bit above that suggested to me that PC/Macs do not have the restriction present on mobile phone S1 controllers, that prevent inadvertent upgrades to S2.

It seems to me that the restriction on Mac hosted controllers is there to the same extent as it is on mobile phone hosted ones; both will not move to S2 via using the update now feature within it. And based on your latest post, the same applies for the PC S1 app.

Hi @bamber2001 - Did you manage to get a solution to this? - I also have encountered this issue today. As soon as I select “Add Product” on my iOS S1 Controller I get promoted to upgrade to the S2 Controller which I can’t do because I still have Gen 1 speakers on my S1 Sonos network.

BTW I also have the S2 Controller on my iOS device for a separate S2 Sonos network.

Try uninstalling the S1 controller.  Temporarily power off your S2 system speakers).  Reinstall the S1 controller and choose ‘connect to existing system’.  Then add your product.  Then power the S2 system back on.

I tried that but as soon as I select “Add Product” I’m asked to log into my Sonos account and provide the Controller certain permissions whereupon I’m then prompted to upgrade the controller to S2.

I’m wondering if the problem might be related to the fact that I’m using the same Sonos account for both my S1 and S2 Sonos networks.

I deleted both controllers from my iPhone, reinstalled the S1 Controller and did factory resets on all my S1 System speakers. But the S1 Controller would not allow me to create a new Sonos system and add any speakers. In the end the thing that worked was creating a completely separate Sonos account for my S1 System, then I was able to create a new Sonos system and add back all my S1 System speakers. I then reinstalled the S2 Controller and connected that to my S2 System speakers. I don’t recall seeing any mention of having to use separate Sonos accounts when setting up separate S1 and S2 Sonos systems, but it’s all working again (for now).

Glad it is working. Separate accounts should not be needed. I am running S1 and S2 systems on a single Sonos account. 

Admittedly I haven't tried to add an extra speaker. 

In my case having a single Sonos account for both my S1 and S2 systems worked fine for over a week so I know that works. But then something happened (I don’t know what) and setting up a different account for each system was the only thing I could do to get everything working again. I know there are other people with this same problem, so maybe this workaround will help them too. Anyway it’s too early to tell yet whether this will provide a permanent fix.

Hi @ShaunRF I was getting really angry last weekend trying to accomplish excatly what is mentioned here: S1 App (no upgrade/update want) a couple of speakers that would be S2 compatible AND the need to add a sonos connect - but the app just wants to force me to get the upgrade. Darn frustrating, glad to see you got this working with 2 accounts, will try this asap.

thx,

phabean