Hi, I’m a big Sonos fan and have invested quite a bit over the past few years. I just purchased by 14th Sonos speaker, a Move, to join my existing setup consisting of various: Play:1, Sonos One, Play:3, Beam and Connect:AMP (gen 2) devices. All of my existing devices were running on Sonosnet, firstly with a Sonos BOOST, but more recently with the Beam being wired and the root of the Sonosnet. That change (removing the BOOST) was just to simplify as I really didn’t need it.
I tried moving everything onto WiFi a few weeks ago, but it was terrible. Speakers kept dropping out, changes to songs (like skipping forward) or volume changes were laggy, the app UI kept restarting, then stopped showing me all my speakers (even ones that were playing) and took minutes to update them back into the app. It was terrible. I put this down to having a 4-node “mesh” WiFi system. I have a wired backhaul on those APs, so not strictly “mesh”, but they do support steering, 802.11v, etc. to optimise the WiFi coverage in my home. But simply plugging the ethernet into the Beam got everything to reconfigure onto Sonosnet and order was restored -- it’s remarkably reliable in that configuration for me.
Anyway, the Move turned up today and during setup I realised to my horror that it wanted to be on the WiFi network. So, I’m now in mixed mode. Everything else is still on Sonosnet, but the Move is on WiFi. And, sure enough, everything is now behaving badly again. The Move works fine, plays fine, and seems to sync up with the other speakers fine. But then some speakers in the group will drop out, when they normally wouldn’t -- not the Move itself, but others. And then the UI on the Sonos app resets, reloads all the speakers again, some missing, even ones that are currently playing, etc. Just like when tried putting everything on WiFi.
I’ll do more testing later today, but does anyone have any tips? I can’t lock the Move to a particular AP in my setup, and even if I could it would go against the whole point of having a mesh WiFi system. Perhaps it’s better if I start music on the speakers on the Sonosnet first, then add the Move into that group, rather than start on the Move and then add other speakers? Not sure yet. Any other suggestions?
It’ll be very disappointing to have a remarkably stable Sonos system destabilised by adding this additional speaker, so if I can’t find a way to solve this and make it all work as it should, I’ll have to return it (which I really don’t want to do!)