Skip to main content
Avid Contributor III
August 27, 2024
Answered

Switching all S1 Devices (CR200 Included!) to Sonos Net from Wi-Fi after Bridge Failure -

  • August 27, 2024
  • 13 replies
  • 692 views

The Saga continues……                                                                 

My System consisted of 2- Play 5’s, 1- Connect Amp, 1-Play One, a Bridge, and 1- CR200 Controller… This had worked successfully for a many years and then recently I kept had intermittent  connection to the Play One….  and after the Help Desk had me switch to Wi-Fi (removing the bridge) all now works… except the CR200 Controller….  

When S2 was introduced, I was told specifically that the CR200 MUST have the Bridge to operate as the 200 only has SonosNet.. and it did … until now.  It provided great convenience for us when it was used. I was thinking about getting another Bridge or Boost, but trying to find a working one may be a challenge. But now I’m reading contradictory threads of users who have successfully reintroduced the CR200 without a Bridge… and using S1, saying it only requires at least one of your Speakers be connected to your Router.

If this is correct, I would really like that confirmation, and more importantly obtain the specific steps needed to switch from Wi-Fi S1 to SonosNet.

Is it really just Disabling the Wi-Fi for each separate Device in the System Page of the S1 App???

I’m being cautious here as swapping from SonosNet to WI-FI was not a smooth process, as I always had the Sonos on a separate Network where I have all my IoT Devices as I’ve had to use the vulnerable lower SMB Setting to gain access to my NAS’s Music Folder.… My Main Network (such as my NAS/PC’s/etc.) which my Mobile Phone is on has the S1 App… but that's where it gets weird. When setting up the Sonos on Wi-Fi, I had to use the IoT Network… but when done, I go back to the mobile’s the “main” Wi-Fi Channel… Initially access was no problem, but then it would intermittently lose all contact and I had to swap back to the IoT Network. It seems stable at this point… 

If you’ve done this, I’d appreciate any hints you might have on how you successfully made this work.

Cheers!

 

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 John B

Just connect one of your speakers by Ethernet to your router.  Do NOT disable Wifi on any of your speakers.  Doing so actually disables Sonosnet.

Give it a minute to reconfigure.  You may need to power off Sonos devices and router, then power on the router and let it come fully back up.  Then power on your wired device, then other speakers.

To go back to using WiFi, just disconnnect the Ethernet cable.

13 replies

Avid Contributor III
August 28, 2024

Good Day John…

I have been that much more due to your help…. And finally (for the most part?) wrapped my head around its architecture….

Misinformation is abundant,,, and its easy to misdiagnose the problem and label a device defective….

When looking at each devices System information in S1 for example, it shows “Wi-Fi is Enabled”..… SonosNet is shown separately only in the NETWORK page...and says “In Use”...I’ve not used S2, so I’m unaware if any improvements were made to help the user when issues occur in connecting…

S1 works for me… 

Cheers!!

 

August 28, 2024

Many regular contributors on here, myself included, have been urging Sonos for years to change the terminology on this item.  For “WiFi” read “wireless”.  “Disable WiFi” actually disables the wireless radio on the unit, making it incapable of connecting wirelessly over WiFi or SonosNet.  For 99.999999% of users this setting is best left “enabled” on all devices.

This has caused so much confusion……

Sonos is gradually dumping SonosNet from S2.  Recent speakers have neither an Ethernet port nor the ability to connect to SonosNet.

I don’t have S1, but in About My System you used to have an indicator:

WM:0 - connected by SonosNet or Ethernet

WM:1 Connected by Wifi

WM:2 Sub or surround connected connected to soundbar in a system with no SonosNet

Hope that helps.

Avid Contributor III
August 28, 2024

Everything Helps.. and I have no doubt that others who have issues such as this will be hopefully be led to this Thread and solve there problem..

And while we’re on the subject of issues….  before  I lost overall connections, I was checking Alexa…as I found the “Ducking” Functionality stopped. I then found a Red Banner in Device Settings (in Alexa) claiming a speaker was “offline”… The same banner appeared for every linked device…. 

 

 

Calls to both Sonos and Amazon yielded Zero help as both pointed at the other…..

My typical Fix for Ducking issues was to uninstall each Sonos device from Alexa, then Uninstall the Sonos App from Alexa… then Add everything back…. and that would always restore Ducking…  But no more.

I thought at this point Ducking was now on the scrap pile of user Functionality and would be no more……

But today, I wondered.. after regaining all SonosNet operation….. would it work again?  And it did… Ducking works again!

But it now appears the “Device Offline” Banners, that are still present… have not revealed why and what it claims are offline…. Another mystery…..

 

marc