Alexa breaking groups (yet again)



Show first post
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.

32 replies

Badge +2
It is not really helpful having lights called 'Living Room Lights' and a speaker called 'Living Room' as those will likely clash. It is important to have unique names for devices/rooms/groups etc... Note if you have registered Sonos speakers as accessories in Apple HomeKit they will need to be renamed in the iOS Home App.

Smart lights and any plugs can be changed in their native App, like Philips Hue or TP-Link Kasa Apps, just as examples.


They have all been renamed since that post (including the Alexa group). But until a couple of weeks ago having SONOS speakers called Living Room, an Alexa group called Living Room, Hue lights called Living Room and a NEST Thermostat called Living Room caused absolutely no problems whatsoever.

The logic of just having an Alexa group called Living Room and all devices controlled from within that group makes a lot of sense, but only if it works (which unfortunately it doesn't). Instead it screws up all your other smart devices.
Userlevel 7
Badge +20
It's like a recurring nightmare or maybe Groundhog day...

Every few weeks it seems SONOS has to release an update which immediately breaks my Alexa/Sonos and I then spend a few frustrating days trying to get it all back up and running. And to make things even more exciting, it never works immediately after I delete and reinstall rooms/skill/devices/preferred speakers it waits a few days before deciding whether it will work or not - just in time for the next update to break it again.

I have over £1000 of SONOS devices. I'm also adding an extension and was going to put in another £2500 of SONOS devices but I have now given up on them.

I jokingly asked my wife how she was going to cope with this Alexa/SONOS fiasco if I died and she replied 'I'll just use the Bose...' Maybe she has a point.

I still suspect duplicate IP addresses could be a cause of this issue, fixed IP addresses would solve/eliminate this.
Badge +2
I still suspect duplicate IP addresses could be a cause of this issue, fixed IP addresses would solve/eliminate this.

A quick check shows that there are no duplicate IP addresses assigned and the hub uptime is 77 days (I've had to do two SONOS / ALEXA resets in that time). I did try this before and it didn't work but I'll give it another go (clinging to straws here).

But for a lot of people IP address might as well be a foreign language and it shouldn't need this level of knowledge to work. Prior to Alexa groups, this was never an issue which sort of points to Alexa as the cause of the problem, but its the SONOS updates that always break groups.



A quick check shows that there are no duplicate IP addresses assigned and the hub uptime is 77 days (I've had to do two SONOS / ALEXA resets in that time). I did try this before and it didn't work but I'll give it another go (clinging to straws here).

But for a lot of people IP address might as well be a foreign language and it shouldn't need this level of knowledge to work. Prior to Alexa groups, this was never an issue which sort of points to Alexa as the cause of the problem, but its the SONOS updates that always break groups.


There is no way to know if you have duplicate IP addresses assigned. By their very nature, they are hidden from the router's assignment table, and thus are unable to be seen on the network.
Badge +2

There is no way to know if you have duplicate IP addresses assigned. By their very nature, they are hidden from the router's assignment table, and thus are unable to be seen on the network.


Thanks I didn't know that. I also ran Fing and that didn't show anything either but I have no idea whether it would or not.

Hey folks- spent 2 hours with Sonos tonight (Oct 28 2019), on this topic. Here’s the scoop.

Bottom line=Software bugs. Also, Sonos doesn’s seem to have an Alexa expert, so support is generic.

Here’s what we tried (so you dont have to spend 2 hours).

-i have 2 sonos 5, 2 sonos 1, and 1 play 1, and 1 echo dot. ALL SONOS FEATURES WORK PERFECT, EXCEPT ALEXA.  IT WAS WORKING A FEW MONTHS AGO PERFECTLY. IT BROKE IN LATER RELEASES.

we reinstalled alexa and sonos. reconnected them. deleted all named groups in alexa. created a new named group. NO MATTER WHAT WE DID..sonos ONLY played music on the Play 1.

Also- even if i grouped all my devices on sonos app, then used voice command to tell alexa to play santana “everywhere” (thats the name of the alexa group), it played on the Play 1, AND i can see IN REAL TIME ON THE SONOS APP, IT ACTUALLY “UNGROUPS” the group of 5 speakers on sonos.

  • THEY ARE REPORTING A BUG HERE- I’M AN EX SOFTWARE GUY- ITS A BUG, AND THERE’S A FEW OF THEM:(
  • THE ALEXA APP CAN NOT “MAKE THE HANDSHAKE” WITH THE SONOS APP.

Hope they fix it- after having voice services, this is like driving a model T car again.

Userlevel 7
Badge +20

Hey folks- spent 2 hours with Sonos tonight (Oct 28 2019), on this topic. Here’s the scoop.

Bottom line=Software bugs. Also, Sonos doesn’s seem to have an Alexa expert, so support is generic.

Here’s what we tried (so you dont have to spend 2 hours).

-i have 2 sonos 5, 2 sonos 1, and 1 play 1, and 1 echo dot. ALL SONOS FEATURES WORK PERFECT, EXCEPT ALEXA.  IT WAS WORKING A FEW MONTHS AGO PERFECTLY. IT BROKE IN LATER RELEASES.

we reinstalled alexa and sonos. reconnected them. deleted all named groups in alexa. created a new named group. NO MATTER WHAT WE DID..sonos ONLY played music on the Play 1.

Also- even if i grouped all my devices on sonos app, then used voice command to tell alexa to play santana “everywhere” (thats the name of the alexa group), it played on the Play 1, AND i can see IN REAL TIME ON THE SONOS APP, IT ACTUALLY “UNGROUPS” the group of 5 speakers on sonos.

  • THEY ARE REPORTING A BUG HERE- I’M AN EX SOFTWARE GUY- ITS A BUG, AND THERE’S A FEW OF THEM:(
  • THE ALEXA APP CAN NOT “MAKE THE HANDSHAKE” WITH THE SONOS APP.

Hope they fix it- after having voice services, this is like driving a model T car again.

This must be a set-up or a location specific bug as my set-up is still working fine. You say that you’ve reinstalled Alexa and Sonos - did you also Disable then Enable the Sonos skill within the Alexa App?