Sonos One saying it is offline and unable to use voice control

My “Move” and “Beam” both updated this week and neither are responding to Alexa.  I’m also using S1 as I have an older device on my setup.

@blacknick can you post the link for the release notes please, so I can follow too?

Thanks, David

I am on Sonos S1
Same here - Alexa Services show offline.

@dmparnell The support person I chatted with said there was only a link for the S2 release notes.  Based on the post from @Corry P I think you just need to continue monitoring this thread for an update.

I’ve got this problem too. Why can’t we just downgrade the firmware, surely it can be rolled back while they troubleshoot the issue? It’s not OK to just say ‘oh yeah we broke it, it won’t work until we fix it at some unknown point in the future’ even if user downgrade isn’t an option, at least push out the last good version as a new release. 

I can relay this affects more people.

Overnight, on the 13th of March, a friend’s Sonos ONE setup was affected. At the end of the night on the 13th one of the Sonos ONE’s listened to a command to the inbuilt Alexa to turn the lights off, on the morning of the 14th it would not do anything - no acknowledgement beep from the speaker or any reaction to voice commands at all.

No changes were made overnight, obviously.

In the Alexa app it clearly states that the device(s) are offline. There are two Sonos ONEs only in the system, both on S1. Both are now out of action. Re-enabling the Skill etc. - and other things - has been tried without success and in a way it is reassuring to know that Sonos themselves broke it and there is no action that we can take as users to get it back.

For the time-being my friend can control Sonos (to play and stop music etc.) by using Alexa on the phone - so saying: “alexa, play X in the Lounge” will work, the Lounge speaker springs into action… but I am told that “Lounge” needs to be specifically said because the phone is not aware of what room it’s in… whereas the Alexa within the speaker would be.

A real shame they didn’t seem do any comprehensive testing before releasing it to the wild, of course. I will follow this thread on my friend’s behalf.

As I said, the two Sonos ONEs are on S1. I don’t know why this was picked on initial installation.

I see that both:

• One (Gen 1)
• One (Gen 2)

Are S2 compatible. I don’t know what Gen the ONEs are - but both are covered anyway - and there are only ONEs in the Sonos setup, nothing else at all… would moving them to S2 remove this problem at the same time?

The more I think about it, the more Sonos not having an ETA for something they broke, and could choose to revert in a day or two, seems more and more pathetic. Break your older stuff, so that folk are forced to use your newer stuff (even if it’s just the app/OS every little helps - and it’s a short step away from the revised messaging that “ONEs using S1 no longer support Alexa”, isn’t it?

@Hippogriff

Indeed updating your system to S2 will solve the current Alexa issue. S2 is the full supported Sonos system and I strongly recommend using it. 
Supporting S1 any longer even just for fixes will become more and more difficult in future. 

Thank you for the confirmation. I might recommend that route… after some time… I’d like it just to revert back to working soon, if that’s going to happen at all.

Why has the outage affecting Alexa voice control still not been sorted out. It has now been 2 days and not been resolved. It’s not good enough and I feel I have purchased a Sonos speaker that cannot now deliver what it says on the tin.