Answered

Unable to add Sonos Beam to Alexa Group

  • 6 October 2021
  • 50 replies
  • 947 views

Badge

I am trying to add my Sonos Beam to an existing (or new) Alexa group, but it does not seem possible.

I'm following these steps:

  1. On Alexa, go to devices
  2. Select the Group
  3. Tap Edit
  4. Select the Sonos Beam
  5. Tap "Save"

When I go back to that group, the Beam does not appear under group devices. If I try the above steps again, the Beam does not appear selected (part of the group).

 

This is only a minor inconvenience as it prevents me from using commands such as "Alexa, turn on lights". Instead, I need to be more specific such as "Alexa, turn on living room lights". However, it seems like a bug with the Sonos/Alexa integration and I wanted to bring this up.

 

Are others experiencing the same issue?

icon

Best answer by Ken_Griffiths 7 October 2021, 13:51

View original

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.

50 replies

Still not approved by Amazon…

Update:

Known issue for Roam and Beam 2, Sonos are aware, no timeline for fix. Confirmed via their support today.

I guess we just keep waiting.

@GuitarSuperstar thanks! Then something is definitely broken in my setup. I've tried resetting everything and doing it again but the issue is still there sadly :(

Is this the new Beam (gen 2)? If so, it’s possibly the case that Amazon are yet to authorise the device for grouping or ‘enabling/controlling’ an Alexa group… there is usually a delay with new products.

Once the Beam (gen2) is Amazon authorised, you should then be able to add it to the first section of the group (assuming you have installed Alexa VA on the product) to control the devices in that group. Meanwhile you should still be able to add it to the speaker part (third section) of the Alexa group for playback purposes. I hope that assists.

I was hoping for the exact same thing with the new Sonos ‘Roam’ speaker, as that too cannot (yet) be added to an AlexaEnabled’ Group to control the group. That would be helpful too, but perhaps it is possibly ‘by design’ in the case of the ‘Roam’ … as it is a ‘portable’ speaker, but I would have found that a useful (nice to have) feature.
The Beam gen2 though should get authorised, as the gen1 version certainly is authorised and can be added to the Alexa groups. We shall have to wait and see.🤞

FYI, I just added my Beam (Gen2) to an existing group that has been set for over two years.

As an Alexa ‘enabling/controlling’ device for the group (first section), or just as a speaker in the third section of the Alexa group ?

Just to add to this - I have the same behaviour as OP and Ken/others. Unable to add the Beam as a control device to a group (add as speaker is fine though).

I previously used a Gen 1 Beam and adding as a control device works.

Really hope Gen 2 is certified soon - is there any official comment from Sonos on this?

Userlevel 7

You might try starting from scratch by deleting the group and deleting the Beam from the Alexa app. Let Alexa rediscover the Beam and create a new group.

Badge

@GuitarSuperstar can you please share a screenshot of what the room setup with sonos looks like for you? Wondering if it shows under alexa devices or where?

Userlevel 2
Badge +2

Add another with this problem, just upgraded from beam gen1 to gen2 and I can longer set the gen2 as the default Alexa enabled device for my office room. Having searched online what bothers me is how long the roam has been available and also suffers from this issue whilst it hasn’t been fixed. It could literally be months before this functionality which already works is added to the newer products. Also I can say I wouldn’t be happy if I contacted Sonos support and they told me to report to Amazon, as others have said this is something Sonos/Amazon need to resolve between each other and fast! If this is a sign of things to come in regards to Sonos/Amazon playing nice together it doesn’t really bode well for the future!

 

I’m having this exact same problem with Beam Gen 2. I tried contacting support today who told me to contact Amazon. :(

Yes I wish Amazon would sort this too - did Sonos Support provide you with a link as to where to report this to Amazon, as I will report the matter too?… it’s also a feature that’s missing for the Sonos Roam, but can be done with the Sonos Move and being able to use the Roam to enable/control a group would be useful too.

No they didn’t provide anything other than “you need to contact Amazon”. I haven’t even begun trying to figure out how to do that. Feels like something Sonos should be doing, not their customers. 

Add another with this problem, just upgraded from beam gen1 to gen2 and I can longer set the gen2 as the default Alexa enabled device for my office room. Having searched online what bothers me is how long the roam has been available and also suffers from this issue whilst it hasn’t been fixed. It could literally be months before this functionality which already works is added to the newer products. Also I can say I wouldn’t be happy if I contacted Sonos support and they told me to report to Amazon, as others have said this is something Sonos/Amazon need to resolve between each other and fast! If this is a sign of things to come in regards to Sonos/Amazon playing nice together it doesn’t really bode well for the future!

 

It’s so frustrating that this hasn’t been resolved. If you haven’t already I suggest dropping a note to Patrick the CEO ceo@sonos.com If enough of us raise the issue hopefully they’ll respond.

No they didn’t provide anything other than “you need to contact Amazon”. I haven’t even begun trying to figure out how to do that. Feels like something Sonos should be doing, not their customers. 

I assume Sonos have already done that. No harm in a two pronged approach I guess. Here’s hoping that Amazon will listen to their customer🤞:

Maybe try this link to chat to their customer service:

https://www.amazon.com/hz/contact-us/csp

Still not working. I tried it with the new version 13.4.1, no success. Sonos, this is very annoying!

Userlevel 7

Here is a screenshot of my Kitchen group. The “Kitchen” under “Alexa” is a Sonos One. When I say “Alexa, turn on the lights” my kitchen lights and sink light turn on.
 

 

Badge

@GuitarSuperstar thanks! Then something is definitely broken in my setup. I've tried resetting everything and doing it again but the issue is still there sadly :(

Having just upgraded from beam 1st gen to the Beam 2nd Gen ive fallen into this infurating problem! really hope Sonos sort this out!

I literally spent hours trying to work out what was wrong, deleting group, re adding all products, uninstalling app reinstalling, etc etc finally glad ive found its not just me!

It sounds very first world problemy but having to say “alexa turn the lounge lights off” instead of “alexa turn the lights off” is going to bug me for a long time...

Badge

@Ken_Griffiths thats indeed the case! I guess I'll have to give it some time. Thanks for clarifying!!

Userlevel 7

FYI, I just added my Beam (Gen2) to an existing group that has been set for over two years.

It should be the Sonos devs dealing with Amazon to get this sorted, end users contacting Amazon isn’t likely to help. There must be some sort of certification process that Sonos need to do with Amazon.

Userlevel 7

FYI, I just added my Beam (Gen2) to an existing group that has been set for over two years.

As an Alexa ‘enabling/controlling’ device for the group (first section), or just as a speaker in the third section of the Alexa group ?

Group name is Ginger for lights (Table 1 and Tri-Pod).   Room name for Beam 2 is Beam. Added Room named Beam to Ginger with instructions to only play with specific command…” Alexa play music on Ginger”

Badge

@AjTrek1 can you share a screenshot of the room config with the Beam?

Userlevel 7

 

Badge

@AjTrek1 yeah that's the same issue I have.

Userlevel 7

@AjTrek1 yeah that's the same issue I have.

 

Well…mine in not an issue… it works! 😊. I assume you mean “that’s the same configuration”. 

Badge

@AjTrek1 it works for me as well, but not with 100% functionality. Check the picture by @GuitarSuperstar where the Sonos is recognised as an Alexa enabled device. It's not the case for you or me