Skip to main content
Contributor I
October 5, 2017

Multiple Echo and Sonos - play everywhere not an option

  • October 5, 2017
  • 60 replies
  • 23887 views
I have 4 echos in my house grouped to the “everywhere” group through Alexa. I added my Sonos Play 1 and it works fine by itself with any simple alexa commands. However, I tried to add my Sonos speaker to my everywhere group but it doesn’t seem like this is an option. Can anybody tell me if I can play my music on ALL of my echo devices AND my Sonos at the same time? If I can’t add Sonos speakers to the everywhere group along with my Echo devices, I’m less likely to purchase an additional Sonos like I planned. Isn’t the whole point to be able to play music in all the speakers at the same time?
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.

60 replies

Lyricist II
November 13, 2017
If you are using the line out into a receiver for your Echo and a Play 5, set that input to have 70 milliseconds delay in your receiver. Some can have the delay different for each input. Some can’t which will ruin any video playback and isn’t worth it. As Amazon develops Amazon Music Unlimited and adds it to the Alexa App, finding the music you want without having to say the right thing to the Echo will be an option. I’ll probably be getting Connects either way but I can’t afford them now and this option connected all of my home theater systems and Sonos together.
Lyricist II
November 26, 2017
Most dissapointing to me is that even if alexa is part of sonos one, we cant still play audible directly. I have several sonos but im frustrated that after almost 3 years they cant fix this issue, specially now with the integration. If the sonos one and my echos could be be together on the "everywhere" group, i wouldnt mind having to add or group my sonos from the app as long as it still played my content
Contributor III
December 6, 2017
Have read comments with interest. Have a pair of Play 1's in lounge (great!) and have linked them to Alexa/echo dot in kitchen, which I connect to a decent Vita amp/speaker via aux in. I want to play music through all together, and the previously mentioned problem of a combined Echo/Sonos group doesn't work.

However, you can play the radio through both at the same time - not ideal, but a start! I did try Adam's solution of trying to enable 'all rooms' from the Sonos app, but it doesn't work. Is this workaround coming out early 2018 really going to fix this problem? Any other ideas or solutions?
December 7, 2017
I'm curious if anybody has tried the obvious "brute force" method of combining Echo and Sonos groups?

Plug a Dot into a Play5 or ZP120

Group the Play5 or ZP 120 with some other Sonos players

Create an Echo group including the Dot and some other Echos

Play something on the Echo group.

The music should play on all of the grouped Echos and all of the grouped Sonos players. There would be a little delay between the Sonos and Echo groups but that might not be an issue depending on the length of delay and how much the two areas overlap.

I'll probably try this out for myself but was wondering if somebody already has and has some feedback on how well it worked?

I have set this up; the delay makes this a deal breaker if used in one open space. But in adjacent rooms where sound does not pass across in a significant, this will work. Line in needs to be uncompressed though.

But there is a little feature here from Amazon that makes this very useful; I have a Dot wired to the Line in on a Connect Amp, with an Echo to provide music for casual listening in an adjacent space. When the Dot and Echo are grouped, the Echo can be comfortably used for music play commands just for the Dot + Connect Amp, without having to shout over the sound of the Connect Amp speakers - the Dot in their vicinity struggles to do this while the Echo is many feet away and does not need to be shouted at. Instead of specifying group name to the Echo in the command, the name of the Dot needs be used to get just that to start. I have to check this out, but there also is none of the irritating ducking and waiting for that to happen before uttering the command to the Echo.
December 7, 2017
Since my earlier post I have now had a chance to try this as well. I mostly have ZP120s but I also had a fair number of little Blue Play1s that I have since replaced with S5s (Play5 Gen1s) so I have line-in jacks to work with. I have found lots of cheap sources for Dots, some as little as $10 when included in bundles so I have lots of them now too. I also have regular Echos and Echo Shows around because that is what the rest of the family prefers to use. I use Alexa grouping of the Dots rather than grouping through Sonos because that gives me persistent groups with unique names that I can use with voice commands. I can play music on any individual Sonos player or group of players by referencing the name of the corresponding Dot or Alexa group in the voice command. The command does not need to be given through the attached Dot but rather through any convenient Echo device so I avoid issues of the music drowning out the command. Also pleased with the way ducking works in this arrangement (I do not have the Sonos skill enabled). This will work fine for me while I wait for the Sonos skill to get out of beta and the missing Alexa features to get implemented through the new Alexa API.
Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever
December 7, 2017
I have line-in jacks to work with.

I have found lots of cheap sources for Dots

The command does not need to be given through the attached Dot but rather through any convenient Echo device so I avoid issues of the music drowning out the command.

wait for the Sonos skill to get out of beta and the missing Alexa features to get implemented through the new Alexa API.

Key takeaways quoted. Using any Echo device to command a Dot attached speaker works really well to address the "music drowning out the command" issue.

And it isn't just the missing Alexa features; the little I was able to try of Sonos Skills in an admittedly unofficial and distant India leads me to still believe that at this time, the line in but direct comms route for voice commands works better than the Skill enabled one that needs commands to go into the cloud to one server, thence to another where necessary, and thence back down to the home. Feels clunky to me compared to the line in route; but that could be the server distances affecting comms. And the ducking is missing - a good thing.
December 7, 2017
A glitch has just surfaced - I am not able to command the grouped Echo to play standalone. Even if I do not suffix the group name after the command to it, music play will start in grouped mode and that, for reasons of the line in delay, does not work. If the name for the Dot is suffixed, it works ok, only the Dot will play.

This is a change in behaviour from a few hours ago, and I am in touch with Amazon. Hopefully, the new way of grouped play starting even if not specified to in the command, is a glitch and not an added feature by Amazon. Because I do not want grouped play to start when the voice command does not suffix the name of the group to the command.
Lyricist II
December 7, 2017
This entire setup is ridiculous… It’s obvious that there would be people who have both products and would expect them to play at the same time. They (Amazon/Sonos) should have been more explicit that both speakers would not play together at the same time. I as well as others it seems expected them to both to play together at the same time, nothing gave the impression otherwise. I also don’t want to spend hours fiddling around with this stuff trying to get it to work.
jgatie
December 7, 2017
This entire setup is ridiculous… It’s obvious that there would be people who have both products and would expect them to play at the same time. They (Amazon/Sonos) should have been more explicit that both speakers would not play together at the same time. I as well as others it seems expected them to both to play together at the same time, nothing gave the impression otherwise. I also don’t want to spend hours fiddling around with this stuff trying to get it to work.

I never had that impression, and will be surprised if the new SDK can actually make it happen. There are significant technical differences in the way they sync, not to mention it would cut into either side's sales. I'm quite mystified that anyone would think it was possible, but YMMV.
December 7, 2017
@ Kumar- I don't think it is a new feature as I have seen this quite some time ago. It seems to be connected to the way the Echo tries to anticipate what you want to do. Once you start something in a group it assumes any subsequent commands to a group member are intended to also be applied to the group. I think this "grouped state" times out after some period of time after group playback ends. I have also been able to force a return to individual function either by suffixing the name of the specific dot I am talking to (only have to do this once to break the group state) or use a command that does not support group play. The second method is not as reliable because some commands break the group state while others will speak on the specific Dot but then resume group activity. I don't think there is any documentation on all this so I will be interested to hear what Amazon support has to say about it.
Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever