Unable to set Sonos Era 100 as Alexa-enabled device in room/group using Alexa app

Show first post

93 replies

C

Same. Awaiting fix for this Sonos please. 

Airgetlam

Deleted, I was responding to spam, which has been reported. 

 

Bruce
K
Userlevel 5
Badge +5

A big Thank You to all who submitted diagnostics!

We have enough to work with now.

Corry, can you confirm if the developers are actively working on this? And can you please give us a progress update?

Or you just don’t want any more reports cause it’s getting embarrassing now?

R

I find it amazing that I researched buying an ERA 100 to replace an Echo device in my dining room to circumvent an Apple iMusic issue I have with Alexa. The ERA 100 is advertised as being able to function as an Alexa Echo device.  Absolutely zero caveats about that capability. So, I buy the ERA 100. Tout sweet, I run into this problem. I cannot add the ERA 100 to the everywhere Alexa group, or any group of speakers I try to set up, because while it responds to Alexa commands, it is not classified as an Alexa speaker after enabling the Alexa App skill. I then spend 2 days on the phone with both Sonos and Amazon, with nothing being resolved. I talked to at least 3 different Sonos support people. Not one word about this being an outstanding problem.  Instead my time was wasted by resetting and re-installing those 2 days, with a lot of finger pointing between the 2 companies. I give up, and google the issue and find this thread right on the Sonos site! INCOMPREHENSIBLE!  No one told me that this was an outstanding issue with an open ended ETA on a fix, and with more non-productive finger pointing! In 25 years of  working on getting music technology incorporated into my home you people still can’t get it right, especially across companies, and shame on Sonos support for pretending to scratch their heads over this with me like it was something they never heard of.

R

Not a big social media guy.  Among other reasons, folks on social media believe everything is up for debate, often with an unquenchable need to “enlighten” a deluded or misinformed lost soul, like myself :-).  Well, don’t you sound like a lawyer for Sonos.  Interpreting from thin air limitations implied by the advertised “enabled” Alexa compatability.  Because no such limitations are either stated or implied in the description of the “enabled” capability in Sonos documentation.  In fact there is at least one, if not more than one document avainable online that describes how to include the ERA in an Alexa group of Alexa speakers.  Which, again, does not work. Thanks, but I I needed no “clearing up” of my understanding.  I’m quite comfortable with my understanding of my issue. Something Sonos says works, doesn’t.  You got a fix, great.  I’m responding because your uncolicited comments were so off base.  If you feel a need to weigh in with the last word, please do so. I have nothing more to say.

S
Userlevel 2
Badge

Diagnostic is 365694344

In the screenshots:

Recognized as “Alexa capable” and part of an Alexa defined Group is “Nightstand” which is a Sonos ONE.

Also, “Beam” and “”Roam” are listed in the Alexa-enabled section, but not currently being used in any Alexa groups.

NOT recognized as “Alexa capable” are my devices “ARC” (Sonos ARC), “Kitchen Sonos” (Sonos ERA 100), “Lab Era 100” (Era 100).

Also NOT recognized my brand new Move 2 which I just received and installed today.

Note to Sonos support: I had to remove Alexa voice service from the “Kitchen Sonos” because it is in the same open area as an existing Amazon Alexa and conflicting.

Not specifically this bug, but will we EVER get the ability to use any of the existing Amazon alternative wake words (Computer, Amazon, Ziggy, Echo) with Sonos devices for Alexa?

 

N

Same problem here with Era 300.

Works basically well with Alexa, but adding to a group is not possible.

I
Badge

Today I’ve upgraded my two Sonos Ones with Sonos Era 100s. After adding Alexa to the speakers, I tried to go into the Alexa app to associate them with their respective rooms. I’m able to add them as the room speaker, but I am unable to set them as the Alexa device for that room (allowing for room-specific commands like “Alexa, turn off the lights”, etc).

What’s weird is my Era 100s will show up under the Echo & Alexa devices section in the Alexa app, but they do not show up under Alexa-enabled devices when editing a room/group (see attached screenshots).

I’ve reached out to Alexa support and they were largely unhelpful, they claimed that from their resources Alexa isn’t supported on the Sonos Era 100 (maybe their documentation hasn’t been updated since this is a brand new product?). So they left the conversation there even after showing them that Sonos clearly states Alexa built-in support for the Era 100.

Has anyone else experienced this issue? Seems like a bug in the Alexa app, and their support team is unwilling to report the issue up their chain.

 

 

I am having the same problem with my Era 100 and Beam Gen 2’s. They are not appearing as “Alexa-enabled devices” per the OP’s second screenshot, and cannot be added to the group on Alexa. The Era 100 was a recent addition to my Sonos System. The Beam Gen 2’s had been around for a while but recently dropped out from “Alexa-enabled devices”. I have tried renaming speakers on both Sonos and Alexa apps, reinstalled Alexa on the Era 100, and reinstalled the skill on Alexa, but nothing works. My Arc and Move remain unaffected as “Alexa-enabled devices”, so I can only conclude that something is wrong with the Era 100, and a recent update broke the Beam Gen 2’s.

 

EDIT: I observed the Beam Gen 2’s dropping out randomly and then going back into their Alexa groups. I’m not sure why. Hopefully it doesn’t drop out again. The Era 100 is still not working with Alexa.

Ken_Griffiths

@planigan,

Oh well it was worth trying those things. I could see from you initial screenshots that ‘Office Sonos’ was not enabling the group, but hoped that checking/removing it from all your groups and removing/reinstalling the ‘Sonos Skill’ might have perhaps corrected the issue. Looking at your last post you’ve done all you can, but I would still report this to Sonos Support with a diagnostic report and a reference to your posts here. I suspect it’s more-likely down to Amazon to resolve this issue so it maybe worth reporting the matter to them too, but see what Sonos Support say first.

Anyhow, I hope it gets resolved for you and everyone else affected by the issue aswell.

D

Unfortunately this still is a problem for me. My Sonos Roam works perfectly, but none of my Era 100s show up as Alexa enabled devices. 
 

Diagnostic ID: 1751975722

 

N

Similar discussion in the German forum:

https://de.community.sonos.com/amazon-alexa-und-sonos-223393/era-300-alexa-gruppe-hinzufuegen-6755294

It occurs to me, Era 100/300 have the same Alexa-bug.

N

According to this thread concerning Beam gen2 authorization by amazon might be missing?

 

T

Also having the exact same issue here. I got a new Sonos Era 100 to replace one of my Sonos Ones and can’t add it as an Alexa-enabled device to a group. Please fix this!

J

Diagnostics ID: 1265494006

Have the same issue in the US today.  I have updated the firmware on first setup to make sure everything is updated.  I have also reset the device to factory and tried the setup from scratch with the same result.

Era 100 entry in Alexa app doesn’t show any built-in speaker capability whereas Beam does.  This is what I found to be the main difference that’s causing inability to add Era 100 (its speaker equivalent is Main Bedroom whereas Beam’s speaker equivalent is Family Room in the app) as an Alexa-enabled device.  See screenshots.

 

 

 

Ken_Griffiths

@jslin,

If you select the exclamation icon next to the Sonos entry in the ‘Alexa-enabled’ devices list, does it throw up a dialog box that states “Echo devices can only be in one group” - if so, then you simply need to remove the Sonos echo component device from the ‘other’ group and then go onto add it to the desired group. 

That said, it seems that some users in U.S. & Canada have reported issues with Sonos products not enabling/controlling Alexa groups, but that’s not something anyone here in the Sonos community can help with. You would be best to perhaps speak to Sonos Support, or more likely Amazon Customer Support Staff to resolve the issue, that’s if the Sonos component is not already enabling an(other) group in the Alexa App.

1 Attachment
J

@Ken_Griffiths I was responding to this pinned post by Sonos staff member @Corry P : 

 

As to your question, the “Family Room” speaker is for Beam which is working as intended.  It is added to Family Room.  I was trying to add Era 100 to “Main bedroom” but it’s not showing in the list of Alex-enabled devices; it does show up as a standalone speaker though.  

It looks like Sonos does not have a support email but only has a chat service, so I’ll try their chat on a weekday.

Ken_Griffiths

@Ken_Griffiths I was responding to this pinned post by Sonos staff member: 

 

As to your question, the “Family Room” speaker is for Beam which is working as intended.  It is added to Family Room.  I was trying to add Era 100 to “Main bedroom” but it’s not showing in the list of Alex-enabled devices; it does show up as a standalone speaker though.  

It looks like Sonos does not have a support email but only has a chat service, so I’ll try their chat on a weekday.

Have you checked that the Era-100 is not already enabling a group - it defaults to its own group on install and you may need to delete it from that group to add it to your Main bedroom group.

A device can only enable one Alexa group only, at any one time. If it’s not that, then you can call Sonos Support Staff via the link here (during opening hours)…

https://support.sonos.com/s/contact

Hope that assists.👍

A

Same issue as everyone else with my two new Era 100. Does not show up as Alexa enabled devices. Disappointing to say the least as they are sold as “Alexa devices”…

Reply


Terms & ConditionsCookie settings