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

Same problem here with an Era 100. 

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.

Same thing here. I’m in the beta programme and got the tech support people there to look into it - result “it’s an Alexa issue”.

Either way, it needs to be fixed. It’s the only thing stopping me from buying three Era 300’s to replace what I have around the house.

Alexa is broken after the version 15.2 app update. Doesn't work on my Beam.

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

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.

This hasn't helped and it's actually worse now because I can't reconnect my Beam to Alexa (see screenshot). Why is Sonos so unreliable?

 

Finally connected but Alexa and all music services are inoperable in the Sonos app with version 15.2…

Why do we need a computer degree to operate Sonos??

I’m having this exact problem today with my brand new Sonos Roam 2.

Looking for clarification:

Is this yet another variation of the above bug that many of us fought for several years on ERA 100?

Is it really fixed for the ERA 100?  (I gave up trying over 6 months ago and haven’t dared tried to use my ERA 100’s in this way as no time to experiment)

Is this perhaps a stupid limitation artificially imposed on the Sonos Roam 2 because it is battery-powered?  (I have it on a Sonos overpriced charging base and was hoping to use it in a bedroom to control the lights by adding it to a an Alexa group like I do with everything else).

Just set it myself, all sorted!

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.

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.