Suddenly alexa is not working with my voice enabled Sonos Speakers S1 app

Even if the issue occurs after a Sonos update, it can be necessary to fix it on Amazons side. Two partners have to adapt their software each other to get something working like Alexa. Sometimes A has to change something and sometimes B… But imo also if Sonos has to fix it, why don’t just wait until it’s fixed. Blaiming someone or complaining doesn’t make work on it faster.

I’m a lead software engineer in charge a $6+ Billion a year OLTP transaction engine.  Anybody interrupts me for an update in the middle of a high impact outage, they are losing their frigging job.  Period.  You will get an update when there is something to update. 

So you want a press release type update to give you the warm fuzzies?  Well, we give those out all the time.  Hell, I'm surrounded by people who will do that just to keep the hounds at bay.  Doesn't have diddly to do with the actual status, but doesn't seem like that matters, does it?

Sigh.

wow… nothing as sinister as such a conspiracy theory!  More indirect, they are not adequately resourcing the support for customers on S1, imagine this happened on S2?? I would bet this is solved by now….

they are OK making that resourcing decision because we are no longer top tier customers to them? I hope not…. we invested a lot in Sonos and can’t just throw the non S2 compatable stuff away.

To be clear, i’m sure the people working on fixing this are working hard. Are there enough people doing it? i am not sure…

Also btw… a bit surprised by the number of staunch corporate defenders on this forum too now hitting back? how are posters like that employed? by sonos? just looking for neutrality and focus the problem. look i love the sonos equipment when it works too, but this has become an important functionality for anyone using some home automation. 

Anyone who remembers the complete hash Sonos made of their EOL announcement will know they don't do comms to customers well. 

They wanted to change their model to get customers to keep upgrading. I'm sorry, forking out thousands on hardware doesn't make it easy for most to bin old for new. People invested in a brand and ecosystem. I've been a Sonos customer for almost 20 years (yes I had a gen 1 CR100 conroller 😆). Over that time I have upgraded and changed some devices (including that controller). Ive kept others. But the key was, I was never forced to upgrade. 

Their uturn of, sorry your devices are no longer supported, to a we bad, they will be but in a limited fashion (and here's and email from our COE saying sorry) was messy and poor. Customers dont forgot. The whole S1 was only created due to the backlash they got from their customers.  

I get it, you can want to have customers always on the latest version, spending more money with you. But hardware and software aren't the same. And a Sonos music device is not as important as a mobile phone to users, so pushing people to upgrade was wrong. 

If they wanted more revenue, a better model might have been to create a premium service that worked across all their ecosystem (maybe even Alexa dare I say it), ragher than segregate their hardware. You would get users who would pay a subscription to get those extra services. Others who dont could happily stay in their standard world. People would have also naturally upgraded some obsolete hardware over time, just like I did. So more revenue. 

Where am I going with this? Well Sonos created a 2 tier system for customers at that time.  Everyone knows S1 support and updates are second class to S2. Anyone who says otherwise is in cloud lala land.

It may not be that cynical, but at the end of the day they want you on the latest hardware. So resources to develop, test releases etc will be less than S2.

As some have said here, S1 customers are being treated poorly, but...

1. Did they cause the outage on purpose as a a ploy to upgrade? Very Doubtful. Did they cause the outage? Absolutely. 

2. Nothing was shared out to the "loyal" customers. We all had to find out ourselves after trying to fix it. Now we are self supporting others.

3. This is a global major outage (as Sonos report). But the length of time it's taking to resolve is frankly shocking. If you caused it, then make sure you fix it quickly. 

In summary, all this outage is doing is further showing the gap between their 2 tier system. And many probably didn't need any more proof of that.

Agree on the slight religious tone here from some - Think your comment is very balanced and spot on;

Love my Sonos stuff and repeatedly surprised by the level of service i get upon contact even with my old stuff. Nevertheless a bit surprised on this outage. It is not like they are about to send a man to Mars, so assume there is some dependency to Amazon that lag out.

I use the S1 app for my Sonos speakers.  Recently my voice enabled Sonos Move speaker is not working with Alexa.  I can control my speakers in the S1 app but not with Alexa.

When I look at the Alexa app the voice enabled Sonos speakers are showing offline.

• I have disabled and re-enabled Sonos Skill in Alexa
• Alexa does not find any devices when I re-enabled Sonos skill in the Alexa app
• I have removed and added Alexa voice enable to each speaker
• I have powered off and on the speakers

Please repair this issue.  I don’t want to move away from Sonos.  Thank you.

I can’t believe Sonos hasn’t notified users of the outage… only a deep dive search revealed there’s a problem.  This is going to be a good test Sonos.  Do you fix this quickly (How about roll out the previous update so we can revert back!?!?) or do you leave us hanging and chosing to never buy another Sonos product again?  This is a bigger issue than they are recognizing.

Does not work for me ! Still same issue

I opened the Sonos app / settings/ system updates and did an update.  Alexa integration appears to be working properly now.  

If only the cover art, artist, and album information was working as it should I would be truly satisfied.

Thank you Corry for you and your teams efforts.

I installed the update, disabled and enabled Alexa , and it is now back working. 
 

BUT….

Prior to these issues when I said “Alexa” there was an audible noise, which indicated “she” heard me. Now that is gone. It otherwise works but any ideas how to get that back?