Trending Lyricist I

Question

Sonos Move - existing sonosnet

18 replies
6987 views

Hello,

I understood from several messages that the Sonos Moce will not be incorporated in the Sonosnet mesh network and if I continue using the sonosnet basically will not be able to included the move in groups and plkay synchronized music.

I have an existing network with 10 + speakers, consisting of play 1 One, play 3 play 5 (1ste and 2nd gen) beam and sub, .
Till now the clear message was that for such qty of speakers the only good option was the Sonosnet.

My network is build up from with ubiquiti material (USG / managed switches & 2 accesspoints)

Basically buying a Move would push me from the Sonosnet to wifi, will this setup be as stable as the sonosnet ?

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.

pwt

Virtuoso

I don't think this is correct. You can have some of your speakers on SonosNet and the Move on WiFi, and they'll work together as normal.

4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300

ratty

I understood from several messages that the Sonos Moce will not be incorporated in the Sonosnet mesh network and if I continue using the sonosnet basically will not be able to included the move in groups and plkay synchronized music.

That's incorrect. Unless it's in Bluetooth mode (when it would be operating standalone) the Move would be able to join groups just like any other Sonos player.

The fact that it uses WiFi when the rest of the devices are on SonosNet merely puts the system into 'mixed mode'. WiFi is just another connection method, like SonosNet or Ethernet. The Move would still be part of the same IP subnet.

K

koen71Author

Trending Lyricist I

Hello Ratty & pwt

Thank you for the clarification.
At the moment I have here a setup where a play 5, a play 3 and a beam + 2 x play 1 + sub are used for 80% in 1 group, 1 open area so any out of sync between speakers is noted fast. I would exchange the play 3 with the Move or simply add the Move, depending on sound experience.

1) Will this mixed mode network be able to give the same experience ?
2) how about multicast, now I have 1 wired connection from my network to the boost and all speakers connected via Sonosnet, will this mixed mode not generate an extra stress on the network ?

Koen

bockersjv

Local Superstar

I run in mixed mode in my garage and cabin and it syncs with the house speakers(on Sonosnet) perfectly. The only issue i sometimes get is a failed update but that normally works on a second attempt.

ratty

1) Will this mixed mode network be able to give the same experience ?

I don't see why not, assuming your WiFi coverage is up to scratch.

2) how about multicast, now I have 1 wired connection from my network to the boost and all speakers connected via Sonosnet, will this mixed mode not generate an extra stress on the network ?

I doubt it would make much difference. The amount of additional stress on SonosNet caused by the addition of a WiFi-based group member ought to be minimal.

(I've no idea what might happen if the Move was the first 'room' in the group, since in theory it ought to become the 'group coordinator' serving traffic to the other group members. Sonos staff might like to comment.)

K

koen71Author

Trending Lyricist I

Thank you for all the feedback, I was not aware of this mixed mode.
Time to think about pre-ordering the Move

D

denix

Lyricist III

Actually, this little “feature” (rather a bug to me) is not mentioned anywhere. So, I bought a new Move under the assumption I would be able to add it to my existing SonosNet, consisting of 10+ speakers. Half of those speakers are hard-wired and all of them are in a separate subnet. I don’t have a WiFi access to this subnet for many reasons, security being one of them. Also, I don’t want to add Move to my main protected WiFi network, also for security reasons. And even if I do, Move won’t be able to see the rest of speakers in SonosNet. What a bummer!

jgatie

Actually, this little “feature” (rather a bug to me) is not mentioned anywhere. So, I bought a new Move under the assumption I would be able to add it to my existing SonosNet, consisting of 10+ speakers. Half of those speakers are hard-wired and all of them are in a separate subnet. I don’t have a WiFi access to this subnet for many reasons, security being one of them. Also, I don’t want to add Move to my main protected WiFi network, also for security reasons. And even if I do, Move won’t be able to see the rest of speakers in SonosNet. What a bummer!

It’s not a bug, it’s by design. All Sonosnet capable speakers need to be unplugged to be moved anything other than a short 3’ distance. When they are plugged back in, they go through a setup sequence during which the Sonosnet mesh is recalibrated to account for the new location. They will not play until this sequence is complete. On the other hand, the Move is able to be moved long distances without powering down, and while playing music. This means it would have to recalibrate the mesh constantly, on the fly, which is not practical and would lead to dropouts in the music. This is why the Move was designed to be WiFi only.

D

denix

Lyricist III

It’s not a bug, it’s by design. All Sonosnet capable speakers need to be unplugged to be moved anything other than a short 3’ distance. When they are plugged back in, they go through a setup sequence during which the Sonosnet mesh is recalibrated to account for the new location. They will not play until this sequence is complete. On the other hand, the Move is able to be moved long distances without powering down and while playing music. This means is would have to recalibrate the mesh constantly, on the fly, which is not practical and would lead to dropouts in the music. This is why the Move was designed to be WiFi only.

I realize it’s not a bug, but a technical limitation. But it is a deal breaker for me! And it is not mentioned anywhere in the marketing materials for the product. So, I now need to return it for refund, as I can’t really use it w/o compromising my setup… A technical limitation of a major functionality that is not disclosed - if I knew about it upfront, I wouldn’t have spent $400!

jgatie

I realize it’s not a bug, but a technical limitation. But it is a deal breaker for me! And it is not mentioned anywhere in the marketing materials for the product. So, I now need to return it for refund, as I can’t really use it w/o compromising my setup… A technical limitation of a major functionality that is not disclosed - if I knew about it upfront, I wouldn’t have spent $400!

You have a decidedly unique environment. For 99.9% of the installs out there, the Move’s WiFi vs Wired setup issues would be transparent to the user and therefore not a “technical limitation”. I imagine that is why the “limitation” is not prominently disclosed.

Show more replies

Sign up

Login to the community