Hi @elziko 

As you can reliably recreate those symptoms on devices other than the Era 100, I recommend you get in touch with our technical support team for some troubleshooting - though I recommend you first try going to the Alexa app and selecting More » Skills & Games » Your Skills (at bottom of screen) » Sonos » Disable Skill and once done, selecting Enable to use to link the accounts once more, then test.

I hope this helps.

@Ken_Griffiths I applaud your tenacity to attempt to break your system 

The problem is the error message “sorry, something went wrong” is so generic, and both Alexa and Sonos are closed systems with no/limited enduser access to debug/log files to know exactly what is going on.

I can reproduce the Era-100 intermittent ‘mic not listening’ issue at any point during the day and initially my thinking was that Alexa saying ‘Sorry, something went wrong’ was perhaps related to that and that’s what initially got me started on this, but I was never able to reproduce the latter and just kept on trying to see if I could make it happen. Then things have moved onto other devices and it’s usually when leaving them stand idle for a while, so I thought I’d give it a try with the Roam and even different account credentials but still no luck at making it happen here.

It’s clear (I think) that it’s not related to the Era-100 ‘mic not listening’ issue and it also seems reasonably clear that it occurs on echo products too, I’m now just a little curious as to why only some Alexa users are affected?

Edit: It is this link that makes me think it’s perhaps more-likely an Amazon issue…

https://www.funktionalhome.com/alexa-sorry-something-went-wrong/

The intermittent ERA-100 wake up appears to be fixed since last night, but nothing official from Sonos (yet) 

However, this morning, the usual ‘Sorry, something went wrong” was the still first response from ERA-100. 

@craigski - Agree, the “Sorry, something went wrong” issue still persists. Occurred on a One this morning.

My use case, this happens every morning on ERA-100 in bedroom, but also in evening if I have been out for the day, and not used alexa for sometime:

1. Sonos alarm - BBC Sounds every weekday morning - works fine
2. 30 minutes or so later, I say ‘Alexa, stop music’ - works fine (now the intermittent issue is fixed)
3. Then I say something like ‘”Alexa, will it rain today”
4. Alexa responds “Sorry, something went wrong”
5. I then repeat command and it works fine.

I can replace the command in (3) with say ‘Alexa, what is two plus two” or ‘Alexa, what is the temperature”, etc same result

I can do multiple ‘local’ commands play/stop music in (2), all work fine before (3)

There must be something different with how type (2) commands (eg Alexa local music control) vs type (3) commands (eg Alexa questions)  are processed, different servers? different networks?

I think my local network is fine as there are no issues with (1) or (2).

Just out of curiosity, what DNS service are you using @Mr. T and @Ken_Griffiths ? I’m using Cloudflare.

Also do you both have multiple Amazon accounts linked to Alexa?

I just use My ISP (Virgin Media) DNS Servers with a Plume Router/Mesh setup (6 Hubs). The servers are 

• 194.168.4.100 (Primary)
• 194.168.8.100 (Secondary)

Yes, I have my Wife’s Amazon account linked to my Amazon account and we each have our own Alexa accounts. Our home (Alexa) devices just use my Alexa login normally. I have used the Wife’s Alexa account recently though to try to test for this issue… but no joy there.

So I can access/see the Home devices through my Amazon Account via - ‘Manage Your Content & Devices’ off the Amazon main menu.

Just to add, both the Wife and I have been looking out for this issue, but not (yet) ever seen the ‘Sorry, something went wrong issue’ here. Thats checking many of the Amazon/Sonos devices that we have here, particularly first thing in the mornings and when devices have not been used for a number of days - but so far we’ve not come across it.

I’ve mentioned to @Mr. T that I will let him know if I do ever see the issue and will certainly post back to this thread too.

Just wondering if you and @Mr. T  are using the same make/model router, or ISP?

@craigski @Ken_Griffiths -

I also have Virgin Media broadband. Virgin Hub 4 is in modem mode and using an Asus XT8 mesh router with satellite. I don’t think the issue is related to DNS settings as the Echo Dot I have does not act in the same manner with the first request failing. That only occurs on Sonos devices and experienced it on a One, Era 100 and Era 300. First request being either the weather or time, not music related.

Only my Amazon account is linked to Alexa.

For whatever reason, the first voice command after a period of time does not get processed/sent to the Amazon cloud/servers as the command does not appear in Alexa app history.

Snap, the something went wrong command never appears in history.

@Corry P The issue was definitely not resolved at around 07:00am this morning. I do have a case open since November where I have been advised Sonos Engineers are working with Amazon on this specific issue, and Sonos support have not advised me this specific issue is fixed.

I can confirm the other Sonos Alexa issue with intermitted wake up on ERA-100 appears to have been resolved.

@Mr. T are you still experiencing the ‘Sorry, something went wrong issue”

@craigski - I concur, it’s definitely not resolved.

Hi @craigski 

Apologies - this thread was tagged with a tracking code for another issue. I’ll remove my previous post and un-tag this thread.

Irony makes me smile. 

‘Sorry, something went wrong’ with the forum tagging of the ‘Sorry, something went wrong’ thread.

Apology accepted! 

Hi @craigski 

Wrongception

This issue is still consistently happening on my Sonos devices. The not understanding why its happing is more frustrating that the actual issue itself 

I have discovered that the ‘Sorry, something went wrong” happens consistently with the first request after a period of time (I think about 8-10 hours) of a certain type of request for each user on Alexa.

Example commands that fail first time may have a location requirement eg “Alexa, whats the temperature” or “Alexa, will it rain today” but also some without a location requirement eg “Alexa, what is two plus two”. Other requests are fine.

Here is one sequence example, that is 100% repeatable first thing in morning. Maybe someone else experiencing this issue can try this scenario or similar, I cant remember exact responses, but Alexa did respond with correct response in green.

@Mr. T I recall you only have one Amazon person/account on your Sonos, but maybe repeat sequence below one morning?

Person2 - “Alexa, stop music” - stops music OK (Streaming BBC Sounds on ERA-100)

Person1 - “Alexa, who am I?” - “You are person 1 ….” OK

Person2 - “Alexa, who am I?’ - “You are person 2, using person 1’s Alexa account...” OK

Person2 - “Alexa, how are you?” - “I’m feeling funny, red nose day is coming up….” - OK

Person1 - “Alexa, wake up” - “Yes, I’m here….” - OK

Person1 - “Alexa, what’s two plus two” - “Sorry, something went wrong” - FAIL

Person2 - “Alexa, what’s two plus two” - “Sorry, something went wrong” - FAIL

Person2 - “Alexa, what’s two plus two” - “Two plus two if four” - OK

Person1 - “Alexa what’s two plus two” - “Two plus two is four” - OK

here is a similar example, 100% repeatable:

Person2 - “Alexa, stop music” - stops music OK (Streaming BBC Sounds on ERA-100)

Person1 - “Alexa, who am I?” - “You are person 1 ….” OK

Person2 - “Alexa, who am I?’ - “You are person 2, using person 1’s Alexa account...” OK

Person2 - “Alexa, how are you?” - “I’m feeling funny, red nose day is coming up….” - OK

Person1 - “Alexa, wake up” - “Yes, I’m here….” - OK

Person1 - “Alexa, what’s two plus two” - “Sorry, something went wrong” - FAIL

Person1 - “Alexa what’s two plus two” - “Two plus two is four” - OK

Person2 - “Alexa, what’s two plus two” - “Sorry, something went wrong” - FAIL

Person2 - “Alexa, what’s two plus two” - “Two plus two if four” - OK

Its always the first request after a period of time of a certain type of request for each user on Alexa service on Sonos.

Hi @craigski,

Agree, only certain type of requests cause an issue. I’ve only heard the error asking for time/weather.

I know there’s no issue with the device connecting to the internet as it can be playing music when the Alexa error occurs.

“Alexa who am I?“ - “I am talking to XXXX, this is XXXX’s account”

”Alexa what’s the time?” - “Sorry something went wrong”

“Alexa what’s the time?“ - “It’s 9:45AM”

Nothing we can do until a fix is implemented to resolve this issue.

I have not had the “Sorry, something went wrong” for past 2 days 

Haven’t used Alexa for a few days, but first “time” command worked just now with no error.