Skip to main content
Wobind
Avid Contributor I
December 11, 2023
Answered

Sonosnet and Wifi issues. WM0 and WM1.

  • December 11, 2023
  • 14 replies
  • 716 views

Hello all. Wondering if anyone can help. 
 

I’ve been trying to build my perfect system for a while. I’ve been using Sonos to amplify my sound system (turntable/ tapedeck/ cd player etc) and streaming through the house. I’ve wanted to have both analogue and my Sonos system so I have upgraded my main system with a traditional integrated amp and speakers and I have just bought a port to get the signal through the house. 
 

Hooked it all up and I have an issue. I placed my entire system on SonosNet for stability, WM0, and all worked well. I have one Roam which is on WM1 because it doesn’t do sonosnet. 
 

Problem I have is the Port signal keeps dropping and is currently unusable. When I checked, for some reason the Port is on WM1 with the rest of the system on WM0. 
 

I suspect that is my issue but - how do I get the Port onto SonosNet and why has it installed in this way. 
 

Any help would be valuable. 
 

Thank you in advance. Robin

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 ratty

I thought that the ones and fives make up a mesh for SonosNet. The Port is in a room with two fives. Would the fives not be extending a signal for the port to connect into SonosNet. 

They should, though if the Fives are wireless the Port might instead choose to connect to the nearest wired Sonos node instead. It’s strange that it’s doing neither and using WiFi.

I’d suggest a factory reset on just the Port, then add it back again.

14 replies

Show previous replies
Airgetlam
Airgetlam
December 11, 2023

It deletes all information stored on a device. Which includes network settings, playlists, and most importantly, any error logs that exist that Sonos Support can use to look at why there might be an issue. More often than not, a factory reset obfuscates a problem, at best postponing a recurrence. We encourage people to only use it when told to by Sonos Support, for 99.99% of the issues, it’s an unnecessary step. 
 

That being said, @ratty is as reliable a source as anyone, if he’s recommending it, I’d do it. 

Bruce
buzz
buzz
December 11, 2023

Each SONOS unit stores a copy of all important data. (Music library index, SONOS Playlists, music service registrations, Room names, etc.) Controllers do not store anything important. Factory Reset of one unit, then adding it back to the system does not destroy any globally important data, only the player diagnostic data. Factory Reset, while it might accidentally, temporarily work around an issue, rarely results in a permanent fix and is simply a waste of time.

It’s best to Factory Reset only on the advice of a senior Community or SONOS Staff member.

    Ken_Griffiths
    Ken_Griffiths
    December 11, 2023

    My thoughts were to try ‘temporarily’ wiring the Port to a nearby speaker, or wireless AP, to see if that may make it switchover to SonosNet too.

      WobindAuthor
      Avid Contributor I
      December 15, 2023

      Thank you to all who contributed. Interesting to think the port may bypass the mesh of the fives to try to connect to a wired SonosNet source to get WM0. 
       

      I took the advice not to factory reset and instead moved the port to a less ‘cluttered’ space and when I did it happily hooked into WM0 telling my I must have had interference in the original placement. 
       

      I adjusted a few things around and now it’s perfect. 
       

      Thank you to all - I appreciate it. Robin

        Terms & ConditionsAccessibility statement