Answered

Sonos 5; SonosNet shows WM0, but Netgear says that it is on Wifi

  • 21 July 2022
  • 6 replies
  • 145 views

Badge

My system consists of the following:

  • Sonos Boost connected via ethernet to my main router
  • Sonos Arc w/ Sub (Both showing as WM0 in Sonos app)
  • Sonos Port (WM0)
  • Connect: AMP Gen2 (WM0)
  • Playbar (WM0)
  • Sonos Move (WM1)
  • Sonos5 (WM0)

All of this is connected to my Netgear Orbi 850 mesh system, with the boost connected via ethernet to the main router, and I have two satellite routers. 

All this seems normal to me, but when you go into my Netgear app, the Sonos5 shows as being on Wifi via 5ghz, while the rest of the system shows as being wired.

I have factory reset the Sonos5, but it still shows up as being on the wifi.

Why the conflicting info here? Why does the Sonos App show my Sonos5 being connected via SonosNet, but my router shows it being connected via the Wifi?

icon

Best answer by mholmes205 21 July 2022, 19:47

View original

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.

6 replies

What happens after you power the Orbis off and on again?

Badge

What happens after you power the Orbis off and on again?

I have done that, and no change.

Are you sure it’s the Five which is appearing on the Orbi’s WiFi, as well as the Move?

Go to http://x.x.x.x:1400/status/proc/ath_rincon/status substituing the IP of the Five, and see what that shows.

Badge

Yes, both the Five and the Move are showing as being on WiFi on the Orbi’s.

Here is a screenshot of my matrix. The Kitchen Sonos on the bottom is the Five

 

The Orbi is clearly confused. ‘Kitchen Sonos’ is connected to the Boost.

Maybe it flirted with a WiFi connection before switching to SonosNet, leaving a track.

Badge

Thanks all…

So after a fourth power cycle on both my router and boost, the Five is now showing as “wired” on the Orbi, and as WM0 on SonosNet.

Not sure what I did differently, but it's working now. So odd.

Thanks again!