Skip to main content
Avid Contributor II
February 11, 2023

S2 app behaviour with S1 device

  • February 11, 2023
  • 17 replies
  • 588 views

I would like to revive a discussion , now closed:

Specifically, it concerns how the S2 app responds to an S1 device on a separate network. My S2 network consists of two Fives (stereo pair) and a One, connected via wi-fi. There is also a separate Play:5 (first generation) hardwired via Ethernet and accessible via S1.

Sometimes -- depending on my location in the house, my S2 app ‘sees’ the Play:5 device first. Quoting from the original post:

  • I invoke S2 and get the message Sonos found on <my network name>. This system includes products that aren’t compatible with Sonos S2. (In other words, it’s found my S1 system first.)
  • My options are (a) Open S1 controller or (b) More options
  • Do I want to open the S1 controller? Nope. I’m in S2 and want to get to S2. So that leaves More options.

Let’s examine those options. There are basically two:

  • Forget Current Sonos System. Does this mean forget the S1 system (which the S2 app has just found) or the S2 system (because I’m in the S2 app)? If the latter (which I think is the case), I definitely don’t want to do that.
  • Reset App. Kill the connection and attempt to re-connect to S2, with no guarantee of success? Nope.

Both choices are confusing, and neither is straightforward. As I said at the beginning of this thread, there really should be a third option:

  • Never attempt to connect to this incompatible product again.

The S2 app could place this product’s serial number on a ‘do not connect’ list that it maintains internally. Or, if that’s too drastic, at least

  • Ignore this incompatible system and keep trying to find a valid S2 system instead.

With the S1/S2 approach, Sonos has gone to a lot of trouble to allow people to set up configurations that allow older systems to coexist nicely with newer ones. If that’s a real commitment, it seems to me that ultimately, S2 will have to get smarter about how it deals with legacy equipment.

 

That last sentence says it all. There is no reason why I would ever want to deal with a legacy device on an S2 network. The S2 app should completely ignore such devices, rather than presenting the user with a series of useless, annoying, and somewhat confusing options.

Why can’t this be the case?

 

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.

17 replies

JCBostonAuthor
Avid Contributor II
February 27, 2023

I’m going to tentatively say that the solution described by Ken Griffiths has solved the problem for me. The solution suggested by buzz did not work for me -- the S2 app still sometimes saw the S1 device, as I reported yesterday.

I’ve not experienced the problem after factory-resetting the S1 device and setting up a new S1 system for that product, as suggested by Griffiths.

All of my playlists are set up in iTunes, so when I re-established my library they all properly appeared. And I had only a couple of saved stations under TuneIn radio, so no big problem there, either.

If by any chance the issue reappears, I’ll report back -- but for now I consider the problem solved. And thanks to everyone…..

Airgetlam
February 28, 2023

Honestly, if I were to see an S1 device in an S2 controller, I’d immediately run a system diagnostic, and call Sonos Support to discuss it. It should never happen. I’m not saying it didn’t, though, but providing them hard data to look at so that the issue could be fixed would be my priority. 

Bruce
buzz
Grand Maestro
February 28, 2023

The only way I know of to see the actual household id of any device is using my iOS app (see profile).

Go to http://{address of player}:1400/support/review, open a player, and go to it’s Zone Player Info. At the bottom is HouseholdControllD

I’ll note that my S1 and S2 systems are different. This agrees with Ken’s point and throws some clouds on my controller re-install scheme. 

Local Superstar
March 3, 2023

Honestly, if I were to see an S1 device in an S2 controller, I’d immediately run a system diagnostic, and call Sonos Support to discuss it. It should never happen. I’m not saying it didn’t, though, but providing them hard data to look at so that the issue could be fixed would be my priority. 

Here you go, here’s my S1 and S2 screens….

S1: (shows S2 speakers that ‘Needs update’).  All are up to date.

 

S2: (shows Front Room as incompatible)

I arrived at this position by upgrading to S2 while the Front Room S1 speaker was powered off.

Interestingly, each system shows a different HH ID in the Zone Player Info screen.  Without a fuller understanding of how the HH ID is derived, I’d have expected them to be the same as I still have all playlists etc. available on each system.  The Single Play:5 (Front Room) connects to the network through Sonosnet too.

Maybe I need to take the plunge and reset the S1 system and set it up again and lose the playlists etc.😔

 

controlav
Lead Maestro
March 3, 2023

Honestly, if I were to see an S1 device in an S2 controller, I’d immediately run a system diagnostic, and call Sonos Support to discuss it. It should never happen. I’m not saying it didn’t, though, but providing them hard data to look at so that the issue could be fixed would be my priority. 

Here you go, here’s my S1 and S2 screens….

S1: (shows S2 speakers that ‘Needs update’).  All are up to date.

 

S2: (shows Front Room as incompatible)

I arrived at this position by upgrading to S2 while the Front Room S1 speaker was powered off.

Interestingly, each system shows a different HH ID in the Zone Player Info screen.  Without a fuller understanding of how the HH ID is derived, I’d have expected them to be the same as I still have all playlists etc. available on each system.  The Single Play:5 (Front Room) connects to the network through Sonosnet too.

Maybe I need to take the plunge and reset the S1 system and set it up again and lose the playlists etc.😔

 

You can always export your Sonos playlists and play them between S1 and S2 systems with my iOS app.

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

@sjw,

My thoughts are to take the plunge and reset the S1 system, but first I would look around at the 3rd party options online to export/import the existing playlists that you have now and (hooefully) that may help to reduce the work needed to recreate the existing S1 setup.

Local Superstar
March 3, 2023

I don't have (or have access to) an iOS device unfortunately.