Answered

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

  • 15 March 2024
  • 60 replies
  • 2708 views


Show first post

60 replies

Sonos employees are duly marked as such, so you can drop that feverish conspiracy dream.  Reality is, you might have to actually question if your melodramatic reaction is really warranted, rather than looking over your shoulder for the black helicopters. 

Userlevel 2
Badge

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. 

Userlevel 7
Badge +16

Wow… that‘s getting worse over here blaming Sonos for hypothetical reasons to let this Alexa issue happen and exist as long as users buy new hardware. Come on… do some reality check. What kind of problem are we talking about!? There is a temporary outtage of Alexa on S1. Sonos knows about it, communicates it and is working on it. They will give an update as soon as there are things to share. 
Some of you are talking about that, as if it’s the biggest thing ever. 
To take part in that plot I would ask myself if some of you are employees of bo**, yam*** or any other company that wants to discredit Sonos. 😉

Sigh.

Userlevel 2
Badge

sure, because at this point, i am convinced they are letting people with S1 systems suffer until they feel compelled to spend more money with them and upgrade hardware to S2

LOL! what a response. you act like there is no mechanism for updates by those involved with fixing something to relay back to a task force over 3 days. what BS is that? I also work at a large company that is involved with high impact incidents all the time. you need to manage a task force and communication to affected users / customers. if there is one guy turning the wrench on everything and giving updates at a company, they have some major problems. i hope your $6 billion dollar organization functions better than you suggest. 

 

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?

Userlevel 2
Badge

Regardless of blame, it’s still been three days since a high impact outage with no update and that’s utterly unacceptable 

 

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. 

LOL! what a response. you act like there is no mechanism for updates by those involved with fixing something to relay back to a task force over 3 days. what BS is that? I also work at a large company that is involved with high impact incidents all the time. you need to manage a task force and communication to affected users / customers. if there is one guy turning the wrench on everything and giving updates at a company, they have some major problems. i hope your $6 billion dollar organization functions better than you suggest. 

Regardless of blame, it’s still been three days since a high impact outage with no update and that’s utterly unacceptable 

 

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. 

Userlevel 2
Badge

Regardless of blame, it’s still been three days since a high impact outage with no update and that’s utterly unacceptable 

Userlevel 7
Badge +16

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 had the problem occurring on my Sonos Ones before I loaded the S1 update. Friday evening 15th March working fine. Saturday morning 16th March it wouldn’t work.

Badge

I’ve seen a notification for several days now at status.sonos.com, which also drives a pop up when coming to this forum?

Since there has been no change to Sonos’ own software, I’d imagine the fix needs to be done on Amazon’s side. Have you complained to them?

Why do you say that Bruce?  The pattern of discovery from users shows that it is clearly related to a new S1 Update, in fact if you read above it says exactly that.  Had it been an Amazon issue it would have gone bang for everyone at the same time.

Badge +1

I am glad I searched here before I spent any time troubleshooting. 

Userlevel 2
Badge

I also spent several hours troubleshooting this to no avail before i searched here to find this. prior i contacted Amazon, was on the phone for an hour, mostly on hold and they didn’t know what to do.

 

Please appreciate your help fixing this as the devices are what i mainly use for Sonos in the house. Any ETA would be helpful i hope they consider this a P1 incident, even though on the S1 Sonos system. Thank you. 

Userlevel 7
Badge +16

Sorry, just my personal thoughts… but why do people think complaining would do anything helpful to the progress. Imo Sonos knows about the priority of the issue anyway. 
And talking about loss of an essential function of the speaker doesn’t really hit it. All options like Airplay, CEC communication and also Alexa depend on external functionality too. If something is getting worse on Apples side, tv manufacturers firmware or in this case maybe also on Amazons side, it‘s not only on Sonos to fix it. 
Sometimes taking it easy will result in the same time and kind of fix. 😉

But hey… as said just my opinion. 

I’ve seen a notification for several days now at status.sonos.com, which also drives a pop up when coming to this forum?

Since there has been no change to Sonos’ own software, I’d imagine the fix needs to be done on Amazon’s side. Have you complained to them?

It’s four days now - and people are still posting asking for solutions as Sonos haven’t had the courtesy to advise customers the system is down. How do you raise a complaint directly with Sonos - cant spot a complaints procedure in the forum?

Userlevel 1

Could Sonus please issue an email to all registered users once they have issued the fix

No one rolls out API changes without notifying their users. SONOS either didn’t pay attention or didn’t test the new update. They now join the long list of people who wasted the trust of people who gave them a great deal of money in good faith for longevity. Not a big deal for them to turn out to be like everyone else, just a little disappointing.  Bought in because I thought they were better, when will I learn? 

Sonos, please fix this! Longtime loyal customers with speakers that are only supported by S1 are struggling. 

Userlevel 1

The first reports of this surfaced on 15 March. I install Sonos S1 updates manually rather than automatically, and didn’t install the current update until yesterday evening (16 March). Alexa was working fine before the update, but hasn’t worked since then.

Clearly, something in the Sonos update has broken the interface with Alexa, and it should therefore be within the capability of Sonos to roll the change back out for the time being until they can figure out exactly why it didn’t work as expected.

Userlevel 7
Badge +16

Low prio due to S1? Time to shift to Google Home?

Why do you think the issue might have a low prio? I cross my fingers it’s a problem Sonos can fix without Amazon because imho things take more time if Amazon is involved. 

Low prio due to S1? Time to shift to Google Home?

Userlevel 7
Badge +16

There‘s a big red popup showing any current problem, if you visit Sonos page and also community page. 
Besides you always can check manually on…

https://status.sonos.com/?utm_source=embed

Its in Sonos to inform the user!

Spend hours of trying to fin a solution!

Do you think our time is free of charge?!

Total disappointed!

Reply