Have you tried disabling the Sonos skill for Alexa, then re-enable?
And, of course, rebooting the Beam…
I would be surprised if this sort of issue was caused by a fault on your Beam.
This sounds like a naming issue to me. Do you have a device called Bedroom listed in your Alexa App?
Please see my article: Tips and Tricks - Resolve Most Alexa Issues | Sonos Community
This sounds like a naming issue to me. Do you have a device called Bedroom listed in your Alexa App?
Please see my article: Tips and Tricks - Resolve Most Alexa Issues | Sonos Community
It’s not really called Bedroom. It’s called Dormitorio in spanish. I have Alexa in spanish. And bedroom was an example… all the lights at home have the same behaviour.
This sounds like a naming issue to me. Do you have a device called Bedroom listed in your Alexa App?
Please see my article: Tips and Tricks - Resolve Most Alexa Issues | Sonos Community
It’s not really called Bedroom. It’s called Dormitorio in spanish. I have Alexa in spanish. And bedroom was an example… all the lights at home have the same behaviour.
Have you checked for any duplicate names across devices and groups?
This sounds like a naming issue to me. Do you have a device called Bedroom listed in your Alexa App?
Please see my article: Tips and Tricks - Resolve Most Alexa Issues | Sonos Community
It’s not really called Bedroom. It’s called Dormitorio in spanish. I have Alexa in spanish. And bedroom was an example… all the lights at home have the same behaviour.
Have you checked for any duplicate names across devices and groups?
Yes. no duplicates.
What make are the lights?
I have a bunch of tasmota switches all connected through Home Assistant.
I have tested more and it’s not all smart devices, I have found a couple that work.
It works with:
- Smart devices through SmartLife skill (I have a bedside lamp and a power plug only).
It doesn’t work with (device or group not found):
- My own Home Assistant skill (I imported haaska in developer mode, region EU - Ireland).
- Philips Hue Bridge V1
- Nuki skill
- Aigosmart skill
- LG ThinQ skill
- Govee Home skill
It doesn’t work but it says “I can’t connect to the device”:
All of them work fine with all the other Echos at home, this behaviour is only with the Sonos Beam.
I don’t know why SmarLife skill is working and all of the rest don’t work…
Any help would be appreciated.
Another thing that does NOT work is the news or news brief. When I ask alexa for the news she answers that I must define the news sources in the app, but I have already done that, and the other echos answer with the news...
Have you tried disabling and reenabling the Sonos skill for Alexa yet? Then 'discover devices'.
Have you tried disabling and reenabling the Sonos skill for Alexa yet? Then 'discover devices'.
Yes. And also removing alexa from the sonos app, removing sonos beam from alexa devices in amazon web, and staring from the scratch.
I was a bit puzzled by the references to Home Assistant. Is that Google Home and if so how does that relate to Alexa?
Home Assistant is a free software to control smart devices from all kind of brands locally. To acces to your home assistant instance from alexa you have to create a developer skill (there’s one template files called haaska that you just import) and link it to your alexa account. Then you can control all your devices in your home assistant instance from alexa.
I think that the same can be achieved to google home but I haven’t tested because I don’t use google home.
If the integration woth home assistant was the only one failing I could think of doing something wrong from my side, but there are more skills not working and also the news… so I don’t know…
You said at one point '..the other Echos answer me...'
That implies that you think of Sonos voice enabled speakers as Echo devices. But they certainly aren't that and don't claim to be. Perhaps that is not relevant here, or maybe there is some relevant feature that is implemented differently.
Well, I mean the official amazon echos. The Sonos Beam is certified by Alexa, so almost all the features should be the same. Also it worked in the past, but not anymore…
Did you fix this issue? I only use Home Assistant to link in to Hubitat, which then exposes devices to Alexa. These devices can all be controlled by Sonos and Amazon devices, I’m wondering if this is a Home Assistant issue?
No, I still have the issue. I don’t think it is a Home Assistant issue as the problem is also with other smart home skills and also with the news.
Pergaps this is a duplicate IP issue, rather than an Alexa one. Can you check my post here: Tips & Tricks - Resolving random issues impacting Sonos devices.. | Sonos Community
I don’t think so. I have a reserved IP address in my DHCP server for the beam...
February 2024 - and I have the same problem. The Alexa voice command has less “power” over Sonos speakers than over an original Amazon Echo Dot on the same network.
Sockets with Tasmota firmware can be controlled via the Alexa app, can be controlled via Echo Dot, but not via Alexa in the Sonos speaker (Beam, Roam, Sonos One). Every Sonos speaker always only responds: Device “XY” does not respond, please check the power connection. The same command is executed without errors via the Amazon Echo Dot.
