Skip to main content
Contributor I
January 10, 2020

Move - issues with grouping and playback

Hello.  I’ve got an issue with Move -

If I commence playback when all players are grouped together, it will not playback on my Move, but will play on all non Move speakers in the group

If I commence playback on the Move, and then add all other players to that group, then all will play the source music as normal

The non Move players (three of them) are all on a Sonosnet Boost wired connection.  The Move is on 2G wi-fi (not using an extender)

Anyone else having this issue, and an/or any suggestions for a remedy?

Matt

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.

44 replies

AjTrek1
January 10, 2020

Hi MjjW

I have two Moves but have not tested the explanation I’m about to give. So until someone disputes this here’s what I think is occurring…

The Move does not interact with the SonosNet (wired connection). So when you start the music on a speaker that is on the SonosNet the Move can’t see it. No joy.:frowning2:

When you start music on the Move the Sonos that are on the SonosNet can see the Move. Party time! :hugging:

You can call Sonos Tech Support for a definitive answer. Sorry I can’t be of more assistance.

Cheers!

Together Everyone Achieves More = T.E.A.M.
January 10, 2020

I am not really convinced by the explanation  given by @AjTrek1 - my apologies to him if I am mistaken. But SonosNet vs WiFi is just about the paths data takes around the LAN. Everything is on the LAN and I  would have expected everything to be able to 'see' everything else.  

I would be interested to know how things behave if you set the Move up on 5GHz. Also if there is any difference depending on where you place the Move.

Contributor I
January 22, 2020

I am experiencing the exact same issue as described and I have all units setup on my wifi.  I can pause the music from the (paired) moves even though they aren’t playing sound but can’t restart the playback.

Contributor I
January 22, 2020

Not sure if this is the same thing - but I’m having weird behaviour from my new Move (installed for about a week). Besides the “powering back up automatically” issue documented in another thread, when Move is grouped with other Sonos speakers/rooms and I mute Move from the controller (so “x” showing next to Move in the group), Move is still playing.

I then tried to deselect Move from the grouping and even though the checkbox disappears from the list of speakers, Move still plays as if it is grouped and the controller still shows Move as grouped.

I had to power down (hold the power button for 5 seconds) on Move for it to be dropped from the group.

Seems like some software issues for Move, but anybody else finding this thing flaky?

Ken_Griffiths
January 22, 2020

Not sure if this is the same thing - but I’m having weird behaviour from my new Move (installed for about a week). Besides the “powering back up automatically” issue documented in another thread, when Move is grouped with other Sonos speakers/rooms and I mute Move from the controller (so “x” showing next to Move in the group), Move is still playing.

I then tried to deselect Move from the grouping and even though the checkbox disappears from the list of speakers, Move still plays as if it is grouped and the controller still shows Move as grouped.

I had to power down (hold the power button for 5 seconds) on Move for it to be dropped from the group.

Seems like some software issues for Move, but anybody else finding this thing flaky?

I’m not seeing this issue. Are you using a WiFi Mesh System for your home LAN, or do you have ‘other’ access points, repeaters, WiFi extenders? If so, just ensure they are all operating on the same WiFi channel as the main router. Check too that there is no 'isolation’ on any access point and that the mobile controller device is not temporarily switching away to other WiFi networks, like a guest network, perhaps?

Hope that assists.

Avid Contributor II
January 22, 2020

For what it’s worth, I’m seeing a similar problem as the OP with my Move using airplay and other non-Sonos speakers - see here

I’d assumed it was another airplay glitch, but this makes me wonder if it’s a Move thing.  

Contributor I
January 23, 2020

Thanks Ken for the suggestion, but no mesh, no repeaters, etc. I’ve had Sonos products for many years and Move appears to be the most unstable/problematic.

Ken_Griffiths
January 23, 2020

Thanks Ken for the suggestion, but no mesh, no repeaters, etc. I’ve had Sonos products for many years and Move appears to be the most unstable/problematic.

If you have the Move on your 2.4ghz wifi band then switch it to the 5ghz band or vice versa ...and just see if that helps. Then go onto consider a different non-overlapping 2.4ghz channel (1, 6 or 11), but if using SonosNet for your other Sonos products then ensure that the SonosNet channel is set at least 5 channels away from your chosen router channel… 

 

Note, if using SonosNet for your main system and you do move the “Move” onto the 5ghz band, remove the previous 2.4ghz network from “Settings/System/Networks”...that will prevent your main System from falling back into ‘mixed mode’ where signals could potentially hop between SonosNet and your routers WiFi signal.

Contributor I
January 24, 2020

Thank you Ken. I was not aware that Sonos could operate on the 5 Mhz band; all the documentation says 2.4 only. My setup is wireless, nothing wired.

At this point I just turned the volume down to zero on the Move. I’ll wait and try ungrouping again and see if the problem persists. But I shouldn’t have to rely on workarounds.

Ken_Griffiths
January 24, 2020

Thank you Ken. I was not aware that Sonos could operate on the 5 Mhz band; all the documentation says 2.4 only. My setup is wireless, nothing wired.

At this point I just turned the volume down to zero on the Move. I’ll wait and try ungrouping again and see if the problem persists. But I shouldn’t have to rely on workarounds.

Yes, the Move in my case ‘defaulted’ to the 5ghz band on first setup, in fact.