So my system is made up of old kit - ZP’s, Play:1 & 3’s etc - and after spending hours yesterday finally getting it all updated and connected again after months of not being able to get it all to work, I went into the S1 app today and opened on a page telling me to use the S2 app!!! It’s now stuck on a page telling me to switch to the S2 app and there is no option to ignore this. Closing and reopening the app simply goes to the same page!
It says all my kit can be controlled from the S2 with an upgrade, which it obviously cant be (ZP’s!!), and clicking on the options it gives me on screen there is no way to simply ignore this page and return to the S1 app to start using my system!!! It has options for disconnecting from my network, resetting the app, downgrading products etc etc but no way to get back to the S1 tabs and actually start using the system.
I have to say I nearly binned the lot and swicthed systems several times over the last few months as Sonos seem to have made it close to impossible to keep the old units working as a system despite the hardware being 100% useable, but literally 4 hours of effort yesterday moving every item, cabling it in, updating them and starting again I finally got it working….briefly. Now I cant use it as the S1 app wont actually let me control it.
Last chance Sonos or you lose me as a customer and user forever. This continual push to end me using the stuff I paid a fortune for and is still fine, is totally out of order. Why can’t I just use the S1 app as you promised and have it keep working as I want it to? I don’t want or need all the additional crap of the S2 products - I just want to play my music as I was able to for years.
Page 1 / 1
These are the screens I cannot get past - they appear as soon as the app starts now.
This is what options are available from that screen…. no way to simply get back to the main app UI
Hi @DamonL
Welcome to the Sonos Community!
I’d normally give other Community members a chance to respond before I do, but in this case, you left out an important piece of information - that you have a Beam Gen 2 running S2 software.
I think what is likely is that the S1 app could not find your S1 system one day, for whatever reason, but it could find your S2 system. As it has found an S2 system, is it asking that you use the S2 app. What we need to do is get the S1 app talking to the S1 system again.
Please unplug your Beam Gen 2 from power. Then, open the S1 app - if it connects to your S1 system and works, great - just turn on the Beam again and you should be good to go.
If it does not connect, please select Reset App (Forget Current Sonos System may also work) where you’ve shown it above. Once done, close and reopen the S1 app, opt to Connect to an Existing System, and once connected, please turn your Beam back on.
I hope this helps.
Even the Desktop apps have got a lot more aggressive about trying to force impossible upgrades to S2, it is especially egregious for those of us running carefully configured split systems.
The good news is that Corry’s advice above regarding Reset App does work, but its painful especially when it happens often.
Hi @DamonL
Welcome to the Sonos Community!
I’d normally give other Community members a chance to respond before I do, but in this case, you left out an important piece of information - that you have a Beam Gen 2 running S2 software.
I think what is likely is that the S1 app could not find your S1 system one day, for whatever reason, but it could find your S2 system. As it has found an S2 system, is it asking that you use the S2 app. What we need to do is get the S1 app talking to the S1 system again.
Please unplug your Beam Gen 2 from power. Then, open the S1 app - if it connects to your S1 system and works, great - just turn on the Beam again and you should be good to go.
If it does not connect, please select Reset App (Forget Current Sonos System may also work) where you’ve shown it above. Once done, close and reopen the S1 app, opt to Connect to an Existing System, and once connected, please turn your Beam back on.
I hope this helps.
Thanks for your help. It seems very poor that despite me being within 15 feet of a ZP100 and a Play:1 it didnt find them and decided it wanted to connect to the Beam that was literally as far from me as its possible to get on a different floor of the house about 60 feet away!
This has actually worked (Forget Current System was the solution - after worrying it would forget the S1 system….) and unblocked the app, but I’m worried it will simply do it again next time once the Beam is powered on again. It’s ironic that one of the most frustrating steps yesterday was actually getting the Beam to connect to the S2 app and took multiple factory resets, app reinstalls etc before I could get the connection. I went through the audio pairing at least 4 times before it finally connected without an error.
I bought the Sonos kit when it first launched in the UK many years ago and raved about it for years to many friends and family. All but 1 original ZP is still working like new but sadly everything seems to have destroyed the original Sonos experience for me. In the last year I have spent countless hours trying to keep the system connected to the various app upgrades and eventually lost the will to live with it until yesterday when I decided it was time to connect it or bin it. You bricked my original old hand controller with an upgrade that did not warn me it would happen when I installed it. The new S2 app is appalling IMHO yet seems essential. I hate to say it given the speakers themselves seem so good and sound great, but I can’t see myself ever buying a Sonos product ever again I’m afraid.
Even the Desktop apps have got a lot more aggressive about trying to force impossible upgrades to S2, it is especially egregious for those of us running carefully configured split systems.
The good news is that Corry’s advice above regarding Reset App does work, but its painful especially when it happens often.
Luckily I haven’t seen this with the desktop app since I got it working yesterday, so I really hope its not going to happen. If the S1 app keeps doing this then it will have to be the end for me. Of course it always happens when you’re enjoying music and your phone rings with an important call and you cannot then pause or even turn the volume down because the damn app is stuck! Really does seem the user experience & needs has been totally forgotten with all the tech changes. Sad.
Hi @DamonL
It is safe to assume that the S1 app will not repeat this behaviour again, unless it is unable to connect to an S1 system, but can connect to an S2 system. If this happens, it is not the app that needs fixed, however, but the fact that it could not connect to the S1 system in the first place.
Regardless of whether you see any issues or not - and I am not just talking about Sonos in particular - I recommend that you reboot your router every two months or so by switching it off for at least 30 seconds. Routers that can run for years on end without needing reboots cost many thousands of Dollars/Euros/Pounds.
However, given that you now know both the cause and the fix for the issue you encountered, I suspect that this will now be no more than a slight inconvenience for you if it does happen again.
I have never heard of delayed volume control on an S1 system - hopefully the regular router reboots will take care of this for you.
I hope this helps.
Thanks - we do that fairly regularly anyway. As far as delayed volume changes, I was meaning the app wouldnt respond and allow volume changes while stuck on the S2 upgrade page. I have no idea why it didnt connect to the S1 system this time as it was playing at the time, working just fine and I was just a few feet from our wifi router. Never mind, as it seems solid now.
