IIRC this is normal for non ‘Alexa’ enabled devices, eg Sonos speakers that do not have Alexa functionality.

Have you tried to be more specific “Alexa, play xxxx in Kitchen Sonos”? ie direct function to the specific named device?

Yes i always specify the sonos zone as part of the command.

Fortunately, as of this morning, it is now working again, despite still playing up yesterday. Technology.

Even though Alexa is now working, my bet is the Sonos speaker is still showing as offline in Alexa App, if so, this is as expected, as per my previous comment.

Yep, you’re correct on that. Thanks for the responses.

I can no longer control my Sonos system through alexa and i’m tearing my hair out. Note, i’m referring to control via an echo device linked via an alexa skill, not adding a voice controller directly to a speaker.

I request a song, alexa states the name of the song, and the zone where i’ve requested it to play, but followed immediately by “hmm, I’m having trouble playing that right now”.

I have been through the following steps multiple times based off reading people who have had similar, if not identical problems, but it has not resolved my issue.

• Disable Alexa Skill
• De-register all Sonos devices from my Amazon.co.uk account (4 zones in total)
  • I’ve tried this via the Amazon web UI and directly through the Alexa app
• Remove any voice controllers configured directly onto a speaker (in my case, removing alexa from 1 Sonos Move)
• Delete the devices from Alexa following the de-registration - did this only on my 3rd and final attempt to sort this
• Log out of all amazon.co.uk accounts, and alexa app
• Re-link the sonos skill
• Re-register the devices to my alexa account (signed in via my amazon.co.uk details)

Doing this, the devices all get re-added successfully to my alexa account, and show as “Online” via the top level “Devices” menu, but when i select one of the sonos zones via the Alexa app UI, I’m presented with a “Device offline. Some settings may not be available”.

I’ve tried doing on a 2.4ghz network only, having 1 sonos device wired via ethernet, having all sonos devices connect via wifi only, but nothing has worked.

Any other suggestions for things i might try?

 

Did you do anything beyond the steps you have listed or did it just magically right itself, as tech is annoyingly prone to doing? I am in the exact same situation as you at the moment and have tried all basic steps. Trying to determine if I should try some patience before I disappear down the rabbit hole. 

I am having the same problem with Alexa on all my speakers. Uninstalled everything, updated modem firmware, skills disabled and reinstalled etc and still no luck 

Have you (re)set up Alexa in the Sonos app, not the Alexa app?

After further testing, my issue seems to be limited to Apple Music. If I ask Alexa to play anything via Apple Music, the attached is the message I get in the Sonos app; after a few seconds Alexa then says “I’m having difficulty playing that”. If I ask for music via Amazon Music, it works fine. I can also start playing from Apple Music via the Sonos app with no issue, and Alexa will pause/stop that if asked. 

Same issue. Amazon Music works through voice commands. Only Apple Music fails when initiated from Alexa through voice commands.

Same issue playing Apple Music from Alexa.  I’ve gone through all the steps of registering the device, disabling and enabling the skill.  

The issue only occurs trying to play Apple Music from the Alexa with Sonos.  If I play songs from Apple Music directly from the Sonos app, that works perfectly fine   

posting on this thread, so that it gains additional visibility of being a wider issue. 

Same issue here. Apple music is my default music service. When I ask to play something via a voice command to an echo it pauses  then says “hmm I'm having trouble playing that right now." Other music services work fine. If I ask the echo to play amazon music, it works. 

Looks like there’s a major issue with playing Apple Music through Alexa on the Sonos right now… This isn’t the only thread to highlight it.

Not that it’s much help but having the same issue, tried the same, basically resetting everything and no luck. Playing music via the Sonos app using Apple Music is fine, playing music through an Alexa device is fine it’s just playing Apple Music through Sonos via Alexa which is pretty much half the purpose of having the Sonos smart speakers.

I agree.  I am seeing it all over “X” as well.  However, I haven’t seen a single person acknowledge it from sonos/apple music/or amazon...

​@bob78 

The majority of today’s posts on the various threads about this issue have now confirmed that it has been fixed, or fixed itself. 

Seems to be fixed

​@bob78 

i.e. posts such as this.

Just tested and can confirmed fixed as well.  Did anyone see anything that indicated where it broke?  Was it Sonos, Amazon or Apple?

No it is absolutely NOT fixed. I get tired of Sonos technical support not knowing anything about these problems and yet I come on here and find this thread.

If your system isn’t fixed, but many others have been, that certainly suggests an entirely different issue your system is experiencing. Unfortunately, you’ve not told us anything concrete, so the best we can do is suggest you call Sonos Support directly to discuss it. Despite your reservations. 

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

It is the same issue. as it happens and A link to this discussion was copied and pasted into the chat I was having with Sonos as they tried to walk me through all the troubleshooting I had already done for the past week.  Only after showing them this thread did they put me on hold for five minutes and came back and agreed and said “it’s an error and they are working to fix it. “ 

I see. It’s seems to me to be a different issue from those whose systems have been fixed already, otherwise your system would be fixed as theirs seems to have been. Unfortunately,  it presents to the user as the same. Sonos is, according to your post, aware of the issue, and is working on getting it fixed. Thanks for the update.