"Sorry, something went wrong" response from ERA-100 using Alexa voice service

I’m having the exact same issue for a few months now. All of my Sonos devices react this way (One, Beam, and Arc). We have excellent WiFi coverage in an small area and we also have a mixed environment where some Alexa devices are Amazon branded Show devices not Sonos devices.

The Amazon Devices never fail.

The Sonos devices intermittently will say “Sorry, something went wrong.”, and issuing the same request to the same device will succeed in short succession. (Within seconds.)

There’s clearly something going on with the Alexa voice assistant on Sonos, or something with the devices themselves.

Same issue here on sonos one. Started approximately 2 months ago. First command in the morning results in "sorry something went wrong". Repeating the same command immediately after always works fine.

Issue never occurred before. Network, etc... all good.

I've been experiencing this “something went wrong” first thing every morning for several weeks now. My Sonos Ones and routers are all wired by Ethernet, so I can rule out WiFi interference.

The fact it usually occurs first thing each day but is usually better immediately thereafter suggests something may have gone into sleep mode overnight. But I don't know if it's the Sonos Ones, my TP-Link network switches, my BT broadband router, or something beyond my property.

I’m still seeing this specific issue, and I don’t have any of the network devices you list. I am also experiencing the wakeup issue discussed here, that has got worse over past weeks:

I’m suspecting its other Alexa capable/enabled (non Sonos) devices (eg Echo, FireTV, SmartTV, etc) on the network that are affecting these issues, that have had recent update(s) rolled out by Amazon or others.

@AjTrek1 and others suggested it could be a geographical location issue, and I thought they were on to something, eg ‘what is the temperature’ is that central heating or outside, so Alexa didn’t know how to respond. I also have same issue with ‘Alexa, what is two plus two’, first command in morning often fails, subsequent commands are OK, so I have discounted any ambiguity with commands.

If you have the time, best thing you can do is log a support case with Sonos.

I’m encountering the same issue with multiple Era 100 speakers I bought in November 2024.

Always happens the first request I make after time has lapse from the last request. Speakers have excellent network signal. Must be something software based on Sonos side that’s causing the poor experience.

Ultimately, I’m impressed with the speakers but not the software. For the price, Sonos software should be much more polished but that’s not the case. Wish Sonos would do better. First 2 months using their products and I’m reasonably happy if I ignore the voice assistant and intermittent Spotify streaming issues.

I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

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.

I'm getting the same on my Sonos 1s. I've a few of them dotted around the house. "Alexa, make an announcement" "Sorry, something went wrong" "Alexa, make an announcement" "What's the announcement?"....

@Corry P I see you updated the other Alexa thread, are the engineers also working on this issue ‘Sorry, something went wrong’, or do you still need more diagnostics?

Hi @craigski 

That is a good question. My documentation for the issue referred to on the thread linked below does not include descriptions of the “Sorry, something went wrong” error message.

While I can’t say that they are the same issue, the Alexa behaviour seen on Era 100 speakers is somewhat unusual - it would not surprise me at all to hear that these different issue manifestations were linked by the same cause. I’ve consulted a colleague and he thinks the same.

Certainly, if we announce on the other thread that a fix has been implemented and you still see the issue described here, you should get back in touch, but I have a feeling they will both be fixed together.

In short, it’s probably best to wait for the fix rather than to waste more of your time trying to troubleshoot. I’ll tag this thread with the same tracking code for the issue described on the other thread so that both these threads will be updated when a fix is made available.

I hope this helps.

Your positive feeling does help, thank you. 😀