Ryan’s comments seem to me to refer to using Amazon devices for control, not Alexa-enabled Sonos devices, so i don’t think anything we have found contradicts what he said.
But I think in the third bullet point above the intended meaning of ‘Alexa-enabled device’ is ‘Amazon device’, because it is contrasted with ‘Sonos devices’.
I am not sure what you are trying to say. Do you mean they wrote “Alexa-enabled device” but meant “Amazon device” instead?
I was sure I purchased an “Alexa-enabled device” when buying the Sonos One, so I’d expect this feature to work as described in the knowledge base.
Indeed you did. I can only speculate as to what Sonos meant, but I don’t think what is written here is correct where the device is a Sonos device. Either that, or we are all doing something wrong.
Indeed you did. I can only speculate as to what Sonos meant, but I don’t think what is written here is correct. Either that, or we are all doing something wrong.
I’m not doing anything wrong! 
Ryan’s comments seem to me to refer to using Amazon devices for control, not Alexa-enabled Sonos devices, so i don’t think anything we have found contradicts what he said.
But I think in the third bullet point above the intended meaning of ‘Alexa-enabled device’ is ‘Amazon device’, because it is contrasted with ‘Sonos devices’.
I am not sure what you are trying to say. Do you mean they wrote “Alexa-enabled device” but meant “Amazon device” instead?
I was sure I purchased an “Alexa-enabled device” when buying the Sonos One, so I’d expect this feature to work as described in the knowledge base.
Indeed you did. I can only speculate as to what Sonos meant, but I don’t think what is written here is correct. Either that, or we are all doing something wrong.
Hmm okay, I’ll open a support ticket and ask them for clarification. Now it’s kinda easy to explain what does not work
Hmm okay, I’ll open a support ticket and ask them for clarification. Now it’s kinda easy to explain what does not work
Sonos does read these threads. I would be surprised if they don’t chime in sometime today.
Hmm okay, I’ll open a support ticket and ask them for clarification. Now it’s kinda easy to explain what does not work
Sonos does read these threads. I would be surprised if they don’t chime in sometime today.
My last hope usually is @Ryan S
The experience with support for me usually was “you did something wrong, remove all and re-add it, and if that doesn’t work make a factory reset”
Never had the impression they actually tried to reproduce a bug with their own hardware.
Hmm okay, I’ll open a support ticket and ask them for clarification. Now it’s kinda easy to explain what does not work
Sonos does read these threads. I would be surprised if they don’t chime in sometime today.
My last hope usually is @Ryan S
The experience with support for me usually was “you did something wrong, remove all and re-add it, and if that doesn’t work make a factory reset”
Never had the impression they actually tried to reproduce a bug with their own hardware.
Well, it’s 7:30 AM in Ryan’s timezone. I think he might need a couple more hours to wake up.
Hmm okay, I’ll open a support ticket and ask them for clarification. Now it’s kinda easy to explain what does not work
Sonos does read these threads. I would be surprised if they don’t chime in sometime today.
My last hope usually is @Ryan S
The experience with support for me usually was “you did something wrong, remove all and re-add it, and if that doesn’t work make a factory reset”
Never had the impression they actually tried to reproduce a bug with their own hardware.
Well, it’s 7:30 AM in Ryan’s timezone. I think he might need a couple more hours to wake up.
Won’t be an issue, the reply from support was that they have too many mails and need 72 hours to answer. They suggest to post here instead anyway ;)
Hey guys, I’m checking in with the team right now to confirm what the expected situation should be, just to make sure I get you the correct information. I believe that currently the Sonos One should also be ducking devices in that group, though it doesn’t sound like it is right now. I’ll let you know for sure if that’s the case though when I hear back from the team.
Hey guys, I’m checking in with the team right now to confirm what the expected situation should be, just to make sure I get you the correct information. I believe that currently the Sonos One should also be ducking devices in that group, though it doesn’t sound like it is right now. I’ll let you know for sure if that’s the case though when I hear back from the team.
Thanks so much Ryan, helpful as aways 
Just to update you, the expected behavior is as I mentioned, that the One should cause the other devices to drop in volume as well. Seems there’s a bug preventing that from happening correctly and the team is looking into it now. I’ll let you know when I hear more.
Thanks Ryan. Good to know that that is how it should be and no doubt will again be the case.
I wondered whether this could be linked to the other current Alexa issue of not skipping tracks. Seems unlikely though, as that arises only where Alexa was used to initiate play, whereas the ducking issue seems to arise irrespective of how the play was started
Thanks Ryan. Good to know that that is how it should be and no doubt will again be the case.
I wondered whether this could be linked to the other current Alexa issue of not skipping tracks. Seems unlikely though, as that arises only where Alexa was used to initiate play, whereas the ducking issue seems to arise irrespective of how the play was started
I think it’s not related. I first discovered this issue in february when I changed my room setup. The issue most likely exists quite a while already. The skipping issue started two or three weeks ago.
@Ryan S I don’t wanna be greedy or anything, but since your developers are opening their workspaces to fix two Alexa issues already, maybe they can have a look at another issue?
When you ask Alexa to play a song, and then ask to play a song again, while the speaker is answering what is going to be played you’ll receive the answer : “Hmm to do that enable your Sonos Skill in the
Alexa app, After enabling the skill just say, Alexa discover devices.” It also happens if you ask to play music while there is any other speech output.
This is 100% repdroducible, maybe there is an easy fix, it’s quite annoying. Thank you 
I’ll mention it to the team for you, Seeky!
Just to update you, the expected behavior is as I mentioned, that the One should cause the other devices to drop in volume as well. Seems there’s a bug preventing that from happening correctly and the team is looking into it now. I’ll let you know when I hear more.
Hey @Ryan S I’ve preordered the new Arc, do you think the issue might get fixed for the launch of the S2 OS?
I think so, but I don’t have a timeline, just being positive :)
Hey @Ryan S I’ve seen that the issue with skipping tracks has been resolved. Do you have any update on this issue here as well?
Hey @Ryan S I’ve seen that the issue with skipping tracks has been resolved. Do you have any update on this issue here as well?
@Ryan S Unfortunately the S2 update has not resolved the issue. The Arc does not duck other speakers either, like the One doesn’t.
Do you have any progress to share? I got the impression we have a key feature not working here.
Hi @Seeky, the fix for this issue will be Alexa cloud based, not Sonos software, but I’ve heard that some changes that should resolve this are rolling out this week. I don’t have an official all clear yet, but I’ll let you all know when I’ve heard that you should be set.
Hey @Ryan S well done guys, can confirm that the ducking works now 
The other bug I’ve mentioned is still there though. When you try to issue commands while it’s currently announcing the playback of some music, it won’t accept any commands and tell you to activate the skill.
The ducking issue should be all fixed now for everyone. So go ahead and set up your Alexa groups as you want and the Sonos One should duck devices as expected.
Hey @Ryan S well done guys, can confirm that the ducking works now
The other bug I’ve mentioned is still there though. When you try to issue commands while it’s currently announcing the playback of some music, it won’t accept any commands and tell you to activate the skill.
I’m checking in on that other one and I’ll let you know when I hear more.
I have a Play 5 in the kitchen and an Echo Dot (both included in Kitchen Group). The Play 5 no longer ducks when I speak to Alexa or she speaks to me and I can’t hear what she’s saying. It used to work fine. Can you help please. I’ve tried everything.
