Preferred speaker function in Alexa no longer working after latest Sonos update

Preferred speaker has broken for me also - much more than 3 months ago. I can’t say is was due to an update or not. I have delete the Group and recreated. I removed the Sonos app and restored. I have rebooted the Echo Dot and the Sonos. I did not delete / reinstall Alexa app on my phone. Suggestions?
-A2
Can you perhaps post a screenshot of your 'Alexa enabled group' and your Amazon devices list and I will see if I can maybe assist.

A_Squared

You need to go onto set your Echo Dot (whatever that is called) to 'enable' /'control' the Bedroom Group in the Alexa App .. it’s missing from the top part of the group.

Hope that assists.

Ken,
Bingo! So much for not reading the instructions beforehand. Thank you for straightening me out.
-A2

Ken,
Bingo! So much for not reading the instructions beforehand. Thank you for straightening me out.
-A2
Good to hear your all sorted a2.

I've had this problem numerous times (every time there is a SONOS/Alexa update) and it either sorts itself out or I have to disable/delete/reinstall etc... to get it working. I've spent nearly an hour today trying to get Alexa groups and SONOS to play nicely and managed to get 5 out of 6 SONOS speakers working as preferred speakers but one speaker refuses to become a preferred speaker and I can't be bothered to spend more time on it.

But I'm really getting fed up of having to do this and my days of buying SONOS are over (just deleted the SONOS Move from my xmas list). I will either replace everything with Amazon speakers (I'm not an audiophile so the quality is more than good enough for me) or Bose as I already have some of their stuff.

mvosloo,

I think your matter could likely be easily resolved by adding your Sonos devices IP addresses to your routers DHCP Reservation table.

Hope that works for you.

mvosloo,

I think your matter could likely be easily resolved by adding your Sonos devices IP addresses to your routers DHCP Reservation table.

Hope that works for you.

Thanks. I had that suggestion from someone else so I have just set that up - but I think I have tried that before with no success. I'll let you know if it works this time.

But for a lot of people IP address and DCHP Reservation tables might as well be a foreign language and it shouldn't need this level of knowledge to work. Prior to Alexa groups, this was never an issue which sort of points to Alexa as the cause of the problem, but its the SONOS updates that always break groups.

Yes, I guess you can say the same about a lot of technology, but a little bit of reading, or maybe watching a YouTube video these days, can soon solve a lot of things.

Reserving an IP address for a local network device is not exactly rocket science and most router manuals can often explain it quite easily, in one, or two pages. A bit like reserving the same table at a restaurant, the device is simply given the same network address so that it stays put and is easy to find.

Yes, I guess you can say the same about a lot of technology, but a little bit of reading, or maybe watching a YouTube video these days, can soon solve a lot of things.

Reserving an IP address for a local network device is not exactly rocket science and most router manuals can often explain it quite easily, in one, or two pages. A bit like reserving the same table at a restaurant, the device is simply given the same network address so that it stays put and is easy to find.

I think you over estimate most people's ability or patience..... My wife wouldn't have a clue how to do any of this and would have no interest or inclination to find out how to - as she said, she would just use the Bose even though she knows how to use the SONOS app.

And I'm reasonably tech savvy but have never had to fix IP addresses before. My understanding is that you have to set the static IP address on the device outside of the IP range on your router - but the SONOS app and desktop software don't allow you to set an IP address. So I have assigned a fixed IP address on my BT Smart Hub and rebooted.

But having done this I realised that I should have probably assigned a fixed IP address outside of my hub's normal range eg 192.168.1.63 and powered off the SONOS devices first before rebooting the router? But I can't do that now because I can't access my router after rebooting it...

So you see even for someone who started using computers when the x86 was state-of-the-art, built my own computers and is an early adopter, I'm struggling a little bit...

EDIT - from what I have found, The BT Smart Hub is fairly 'sticky' in allocating IP addresses and tends to match the same address to the same MAC every time. Not sure how true this is.