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

@Lmarshall,
The Era 300 is working here for me and can be used to enable/control an Alexa Group, that said, I’m based over in the UK.

As a thought, could it be that the Era 300 in your case is already enabling/controlling a different group, as these enabling/controlling devices can just be used for one Alexa group only. Or that the speaker is set as a Home Theatre surround and embedded in the HT device (Living Room) in your Alexa App?

Good to hear our European (and UK) friends are getting fixes! Still doesn’t work for me in the US either. Over here, Era speakers are called “Devices” not “Alexa-enabled Devices”. They cannot control any groups. 

@Ken_Griffiths no, that’s not it. It’s not set up as a surround or in another group. I just got it yesterday and am setting it up now in my office.

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?

Having the same issue here (in the USA). 
 

Diagnostic 2132391858

As for the ‘alternate’ wake words, I think it unlikely that they’ll ever allow them on an ‘Alexa enabled device’, rather than an actual Alexa device. Just so there is a reason for you to buy their hardware, rather than giving all your money to someone else for the hardware, but using their software.

I’m in the US and I’m still having this problem with my Era 100. Diagnostic number 215206880.

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 have the same issue. As new user of sonos, I’m very disappointed, I had high expectations.

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.

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.

So glad I found this thread, but a little frustrated because I bought my Era 100 specifically because it is Alexa-enabled. Hoping for a resolution!

My diagnostic number is 1733313870. I am in the United States. Screenshots and detail below.

My Era 100 is named “Office Sonos” and does appear in the main Echo & Alexa list, along with my other Alexa-enabled devices.

If I select Office Sonos from my Echo & Amazon list, an additional device called seems to be displayed.

Selecting that device displays the device settings that you expect to see in an Alexa-enabled device. Note that this item originally appeared as “planigan’s Sonos Era 100” but I renamed it for clarity. I was able to rename directly in the Alexa app.

However, when I look at the Devices tab, I actually see these two devices listed separately for my Office Sonos. One displays with a speaker icon. The other displays with a generic device icon.

The device settings screen for the “Office Sonos” device just displays generic information when accessed from the devices tab.

When I try to add my speakers to my Office group, neither the Office Sonos device nor the Office Sonos Era 100 device appear in the list of Alexa-enabled devices. 

The Office Sonos device does appear in the regular devices list. However, selecting the checkbox does not persist across saves (i.e., I can select the box and hit save, but the device appears unselected the next time I return to the screen. The device never actually gets added to the group.) 

Despite all of the above, I am actually able to choose the Office Sonos device as the speakers to play for the Office group, even though the device itself is not in the group.

@planigan,

I was initially a little confused by your screenshots, but think I have most of the detail now. There are two components for your Era 100..

• Office Sonos - which is the actual speaker device itself
• Office Sonos Era 100 (which I assume you renamed yourself) - this is the Alexa component part of your Era 100 speaker.  Renaming it did slightly confuse me - I tend to rename mine too, but would have personally called it "Sonos Office Alexa” to show it was the Office Alexa component. 

Anyhow, it is correct that the Alexa component is embedded within the speaker device in the Alexa App, although there are now options in the new Alexa App to change views and see the Alexa device list in a variety of different ways, which perhaps adds to the complication.

I don’t think your Era Alexa  ‘control’ for a group is correctly working here, but what would help is to provide a screenshot first of all showing all your Alexa groups… to do that see the photo below:

It would be helpful to see all the groups you have in the Alexa App. Just carry on then and go into each group and just make sure that "Office Sonos” is not enabling/controlling any of your groups that you have… If it is, then remove it from the group.

Note you are looking for the speaker component only here, not the Alexa component that you called ‘Office Sonos Era 100’ because that is embedded inside the speaker component.

So, if found, remove "Office Sonos" from the first ‘enabling’ section of any group and then see if it will appear as an Alexa enabling device that you can then add to your Office group. If it still will not let you do that, then try removing/reinstalling the ‘Sonos Skill’ in the Alexa App and then give it another go.

Finally, if after doing these things it still will not work for you, then it maybe best to submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and then contact/chat with Sonos Support Staff via this LINK and see what the Staff can perhaps suggest to resolve the matter… and refer them to your post here too.

Hope the above assists.

@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.

Still not addressed in the US

Like so many others I’m having the same issue in the US with a new Era 300. Has there been a solution yet? Diagnostic number: *************. The Era300 works with Alexa, but it’s not showing up in the Alexa app as an “Alexa-enabled device” in the Alexa app so I can’t say general commands for the room/group like “Alexa turn on the lights” I have to use the room name. Has this been solved yet? Screenshots below.

When listing all devices in the Alexa app it shows the Era 300 twice. The first is a default name I didn’t make with the wifi logo, and the 2nd is the era 300 named “New Master Bedroom”

  Neither device name for the Era 300 shows up for Alexa Enabled devices: 

But the Speaker does show up so I can add it as the speaker in the room/group, just not the Alexa enabled device in the room.

Moderator edit: diagnostic recorded and removed

This is such a crazy limitation (that also exists for the Move 2). It really undercuts Sonos’ Alexa integration story, to the point where you should really market these products as being only somewhat compatible on the Sonos website, so that people understand the limitations before spending quite a bit of money on something being somewhat falsely-advertised.

It’s mind-boggling that Sonos doesn’t have the ability to escalate to Amazon to fix something like this. I understand that it takes some time but this thread was opened almost a year ago at this point. Many of us, myself included, have gone all-in on Sonos in large part due to the Alexa integration. It seems like partnership is unsupported at best, and really hard to assume will continue to exist.

Please help make this right.

Joining the group here to say I am also experiencing this problem in the US. Haven’t pulled a diagnostic ID, but I have my office Arc showing up as an Alexa enabled device whereas my living room and master bedroom Era 100s are not. 

Just added an Era 300 and it has the same issue. Calling into Sonos support and will be returning all my Era speakers if this can’t be solved. Bummer because I love them otherwise.

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

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 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.

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.

Just an update to my post: 

Contacted Sonos support.  They have no idea what they are doing either.  Asked me to set timezone; asked whether I have reset it and re-setup; asked me to disable and re-enable Sonos skill in Alexa app (oblivious to the fact that Sonos Beam Gen 2, which is working fine for me, is using the same Sonos skill).  In the end, they ran out of idea and just straight out said controlling lights using Alexa on Era 100 is not supported, only music and asking for time and weather.  

There are many things wrong here:

• Support has zero knowledge of existing Era 100 issues being reported here and elsewhere
• Support makes a disclaimer that is not found on the Era 100 product page (there’s nothing that say Era 100 only supports playing music with Alexa and asking for time)
• This issue has been being widely reported for over a year, yet Sonos failed to make any announcement regarding the status of the issue nor supported Alexa capabilities of Era 100 (or 300) speakers. 
• Sonos continued to advertise Era speakers as Alexa compatible devices w/o caveats

Not knowing whether I am the only few remaining ones who are affected by this, or if this is still a widespread unresolved issue caused me to lose trust in Era line of speakers altogether, and by extension, in Sonos brand itself.  I had high hopes but not anymore.  I will be returning the device at this point and will go with another brand.

It seems like Sonos has given up on supporting Alexa properly. At least their Swedish support is now simply saying that:

The problem you are experiencing is specific to the Alexa-app whom's functionality we have no control over. Our team is focused to fix problems within the Sonos-system, but with these third-party applications such as Alexa, our influence is limited.