Contributor I

Alexa Sonos Roam

Forum|Forum|5 years ago
April 21, 2021
64 replies
9422 views

Alexa will not connect to my sonos roam correctly- it will respond but then not play news, flash briefing, or music. All of my sonos devices (roam, beam, and move) will not play spotify through alexa. I have called support twice, and already tried the following:

On sonos app: disconnect and reconnect devices
On alexa app:
- Disable sonos skill and enable again
- Disable spotify skill and enable again
- Delete all sonos devices and add again
- Deregister all sonos devices and register again

None of these things have resolved the issue. I was told to post on beta community but I don’t have any projects open so cannot post on that board.

One of the reasons I bought the roam was for handsfree use of Alexa and to play music with spotify- none of these things are working.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

L

Lucas_Nt

Lyricist I

I’m one of the many out there that face the same critical issue with the Alexa feature. Spent a lot of time trying the various workarounds over and over but without any luck. The speaker consistently fails to play requested songs despite acknowledging the command. This is highly frustrating as I specifically invested in the Roam for its Alexa functionality. It is so disappointing to see this persistent issue without a conclusive resolution or official updates after all this time (noticed thread is 2 years old). For context, I also own a Sonos Beam with Alexa, which has not encountered similar problems, highlighting that this is a specific concern related to the Sonos Roam...

Ken_Griffiths

I’m one of the many out there that face the same critical issue with the Alexa feature. Spent a lot of time trying the various workarounds over and over but without any luck. The speaker consistently fails to play requested songs despite acknowledging the command. This is highly frustrating as I specifically invested in the Roam for its Alexa functionality. It is so disappointing to see this persistent issue without a conclusive resolution or official updates after all this time (noticed thread is 2 years old). For context, I also own a Sonos Beam with Alexa, which has not encountered similar problems, highlighting that this is a specific concern related to the Sonos Roam...

My two Roams are working fine with Alexa here…? It’s rare that they fail to play the requested audio. I have Amazon Music Unlimited set as my default music service FWIW.

Maybe check you have unique device names (and groups too) in the Alexa device list/App and that the device components (Speaker and Alexa component) are not duplicated in the Alexa App device list. Sometimes Alexa ‘enabled’ groups can be similarly named and give rise to the issue.

It’s perhaps also worthwhile, removing and reinstalling the Sonos Skill in the Alexa App aswell, after removing, or renaming, anything Sonos-related within that App.

L

Lucas_Nt

Lyricist I

I’m one of the many out there that face the same critical issue with the Alexa feature. Spent a lot of time trying the various workarounds over and over but without any luck. The speaker consistently fails to play requested songs despite acknowledging the command. This is highly frustrating as I specifically invested in the Roam for its Alexa functionality. It is so disappointing to see this persistent issue without a conclusive resolution or official updates after all this time (noticed thread is 2 years old). For context, I also own a Sonos Beam with Alexa, which has not encountered similar problems, highlighting that this is a specific concern related to the Sonos Roam...

My two Roams are working fine with Alexa here…? It’s rare that they fail to play the requested audio. I have Amazon Music Unlimited set as my default music service FWIW.

Maybe check you have unique device names (and groups too) in the Alexa device list/App and that the device components (Speaker and Alexa component) are not duplicated in the Alexa App device list. Sometimes Alexa ‘enabled’ groups can be similarly named and give rise to the issue.

It’s perhaps also worthwhile, removing and reinstalling the Sonos Skill in the Alexa App aswell, after removing, or renaming, anything Sonos-related within that App.

After four days of attempting the suggested workarounds, including enabling and disabling the Sonos skill in the Alexa app, clearing devices and groups, I've only managed to get Alexa to work twice. Both times, it stopped functioning without any apparent reason after a while—no changes to the network, Alexa or Sonos app, and without closing the speaker (in fact, I disabled battery optimization to keep it active as much as possible). This is incredibly frustrating and appears to be a critical issue affecting a substantial number of customers, as one can see by searching the issue online. It's particularly surprising for a product of Sonos' quality, especially considering I don't encounter similar problems with other Sonos speakers I own (Beam, One). I eagerly anticipate an official update from Sonos on this matter, as it is a crucial problem that urgently needs resolution. Come on, Sonos...

Ken_Griffiths

After four days of attempting the suggested workarounds, including enabling and disabling the Sonos skill in the Alexa app, clearing devices and groups, I've only managed to get Alexa to work twice. Both times, it stopped functioning without any apparent reason after a while—no changes to the network, Alexa or Sonos app, and without closing the speaker (in fact, I disabled battery optimization to keep it active as much as possible). This is incredibly frustrating and appears to be a critical issue affecting a substantial number of customers, as one can see by searching the issue online. It's particularly surprising for a product of Sonos' quality, especially considering I don't encounter similar problems with other Sonos speakers I own (Beam, One). I eagerly anticipate an official update from Sonos on this matter, as it is a crucial problem that urgently needs resolution. Come on, Sonos...

If you’re not able to sort the matter then it maybe best to quickly reproduce the issue and then immediately submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and then contact/chat with Sonos Support Staff via this LINK and see what the Staff can perhaps suggest to resolve the matter or of course you could speak to Amazon Customer support. In my own case, everything is (and always has been) working fine here. Still works first time, every time, but maybe you have a hardware, or account fault. Give the customers services a call.

Sign up

Login to the community