SonosNet does not activate when it absolutely should. I have talked to Tech support several times and followed that “converting to a wired setup” instructions procedure a dozen times. I’ve audio recorded the “click” that I hear when I plug my Ethernet cable into my one plugged in device more times than I can count, just to ask a friend and ensure that I did in fact hear the magical “click” sound.
When I check my setup, a half dozen speakers are in, hooray, “WM: 1”! If I remove my WiFi network from the app, all those speakers VANISH forever. It’s like they’ve given up on life and have no will to live. Even though supposedly there is a magical SonosNet blasting around everywhere. The only fix is to plug my physical Boost back in, and they magically re-appear! This Boost must have the magical key that gets them to connect.
The fix for this? RESETTING my entire system one-by-one. Tech support told me not to, their forums as well. But the moment I finished spending 30 hours trying to diagnose the issue, and switched to 2.5 hours resetting my 20 Sonos nodes, BAM it worked! My Beam became the node that every other speaker connected to. It’s the most central, newest, and most cable device that I own. Over SonosNet! All WM: 0
After a few weeks of fiddling with stuff, I’m back to where I was before. Half my speakers are green in the status panel and labeled WM: 1. Sure, my Orbi provides a lot cleaner signal than SonosNet, but I’m really just trying to get my 20 Sonos nodes to not cut. out. every. 10. milliseconds.
Can someone tell me why there is not a more forceful way to disable using home wifi? I want this prevented and never allowed. But then when I drop my WiFi, “some” of the speakers get dumb and forget how to connect to SonosNet. Why do they lose their ability to connect? I’ve power cycled each and all 20+ times. Once in a while they work with no rhyme or reason.
What gives? Why is this so complicated and confusing, even tech support was confused and thought that somehow my router wifi was interfering. Well guess what, after a full Sonos reset (going against all advice from tech/online) it worked flawlessly right away. Something is getting into a bad state.
Why did my Beam go from having colored boxes connecting it to every Sonos node to now having no colored boxes in the status table web page? It was doing exactly what it needed to, being the root node (albeit labeled Secondary for some unknown reason) and connecting to every Sonos node flawlessly. The system even performed halfway decent! I was able to stream HDMI audio to every zone pretty much perfectly. Until other nodes started taking over and then some hopped onto my home WiFi. Back to total disaster again. What gives? Why is there no more advanced configuration when you know the auto negotiation mechanism is failing and making bad choices.