Headliner III

Answered

Overlap of S1 in S2 App

Forum|Forum|5 years ago
October 6, 2021
8 replies
227 views

Happens more frequently now but when I open S2 it gives me a found my network, upgrade to S2 or else the S1 speakers pop in. I either have to just exit out and back a bunch of times or else have to reset my phone or sometimes that doesn’t work and I have to find an S2 device and manually start it in hopees it show up. A little frustrating especially as it’s been getting progressively worse over the past few weeks.

Sonos S2

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Best answer by Ken_Griffiths

Sounds like a situation whereby the current S2 system was created (as an upgrade) from an existing S1 HH and that both therefore have the same HouseholdID - so both systems are operating in what is usually referred to as ‘mixed mode’, rather than two entirely separate S1/S2 systems.

Usually, after upgrading, the S1 devices to S2, the S1 devices that are left behind should ideally be factory reset, as should the S1 App too.. and from that a brand new S1 HH ideally should be created, which will then have an entirely separate Sonos HouseholdID to the S2 system.. and when doing that, (as the saying goes).. "Never the Twain shall meet”. See this support link:

https://support.sonos.com/s/article/4845

But, there are issues with this, as the setup for a new S1 Household is now a slightly more difficult process these days, particularly if the S1 Household still has S2 compatible devices and the S2 App is also installed on the mobile controller that’s to be used for the S1 setup - but those issues are covered in other posts/threads on the forum. In summary, it’s best to switch off the S2 HH devices and remove the S2 App before setting up the S1 HH, which can only be done with an S1 (only) compatible product, such as a Play:5 (gen 1), just to mention one example. The S1 (only) compatible devices are mentioned in this Sonos support link: (see ‘S1 Required’ products list):

https://support.sonos.com/s/article/4786

Jeffrey_35Author

Headliner III

Sorry overlap. Bad typing and no spellcheck prior to saving.

“The true sign of intelligence is not knowledge but imagination.”

Airgetlam

Interesting. I can’t think of any particular reason why that should occur, other than some device having a lingering knowledge about the previous state of things.

I’d certainly try a network refresh, by unplugging all Sonos devices from power. Once they’re unplugged, reboot your router. When the router comes back up, plug back in your Sonos devices.

It may be that a reload of all the various OS’ and network devices will fix the issue.

Bruce

Jeffrey_35Author

Headliner III

They are on the same Network but different Sonosnet Channels. Under “Manage Networks” it says “update networks” and then when I click on it asks me “do you want to add a trusted network to Sonos or make a change to an existing network?” I did replace my modem a few months back but not my router.

“The true sign of intelligence is not knowledge but imagination.”

Ken_GriffithsAnswer

Sounds like a situation whereby the current S2 system was created (as an upgrade) from an existing S1 HH and that both therefore have the same HouseholdID - so both systems are operating in what is usually referred to as ‘mixed mode’, rather than two entirely separate S1/S2 systems.

Usually, after upgrading, the S1 devices to S2, the S1 devices that are left behind should ideally be factory reset, as should the S1 App too.. and from that a brand new S1 HH ideally should be created, which will then have an entirely separate Sonos HouseholdID to the S2 system.. and when doing that, (as the saying goes).. "Never the Twain shall meet”. See this support link:

https://support.sonos.com/s/article/4845

But, there are issues with this, as the setup for a new S1 Household is now a slightly more difficult process these days, particularly if the S1 Household still has S2 compatible devices and the S2 App is also installed on the mobile controller that’s to be used for the S1 setup - but those issues are covered in other posts/threads on the forum. In summary, it’s best to switch off the S2 HH devices and remove the S2 App before setting up the S1 HH, which can only be done with an S1 (only) compatible product, such as a Play:5 (gen 1), just to mention one example. The S1 (only) compatible devices are mentioned in this Sonos support link: (see ‘S1 Required’ products list):

https://support.sonos.com/s/article/4786

Airgetlam

Ah, I see I misunderstood the setup. For some reason, i didn’t process that you have both an S1 and an S2 network running simultaneously. I’ve not run such a system, so I’ll defer to the most knowledgeable @Ken_Griffiths here :)

Bruce

controlav

Lead Maestro

I think Ken has got this all figured out: reset the left-behind S1 devices and set them up as a fresh household.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.

Jeffrey_35Author

Headliner III

When you say fresh household are you talking about setttup different email and login etc..?

“The true sign of intelligence is not knowledge but imagination.”

James L.

Retired Community Staff

When you say fresh household are you talking about setttup different email and login etc..?

No, you can use the same Sonos account. You would just need to set them up as a new system, as opposed to adding them back to the existing one. This will give that group of players a new ID and keep them separate :slight_smile:

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.

Sign up

Login to the community