What's new

Issues with Sonos since the latest update

I also have this problem with my sonos setup - ARC SL + 2x One SL + Sub Gen ...
The ARC connects fine but the other speakers wouldn't when I had the IoT Network created without sharing the same subnet...
Currently I have it under the same subnet and all the speakers work - defeats the point of a separate IoT network.

I also tried it with the previous firmware e.g. 3006.102.4 and 3006.102.5 but the results were the same.
Hopefully when Asus fixes the problem with the new firmware, Merlin follows soon after 😁
 
Interesting. I have a GT-BE98 Pro and my Sonos Arc and Sub Mini started having issues. I created a Firestick-IoT VLAN and the Sonos ARC went nuts and stopped working. No matter what I did, the Arc would connect but the Sub Mini would not. It was a S%%T show. TWO hour on the phone with Sonos support, they still couldn’t get it sorted. Then the dreaded, “Reboot your router”.. I have 45 devices connected and not complaining. The dang Sonos would not connect. I just ended up hanging up on Sonos. They were worthless. I did a factory reset on all the Sonos equipment and retried using the VLAN IoT network. It was successful. The VLAN is very basic with no IPv6, small bandwidths and very basic settings. Right now, those are 4 hours of my life I’ll never get back and I’ll keep it where it’s at for now. Aggravating.
 
I'm sorry for all you Sonos-owners troubles, but I've been quietly enjoying the read, and glad to see you all have been able to make some headway on this.

To document my own journey, I used to be an avid Sonos fan, and had about 9 or 10 devices. Then came the S%%T show (as @Webheadfred so eloquently put it) in May of 2024, where Sonos basically hosed all functionality on the app by forcing you to S2, and basically made controlling devices or playing music from locally stored music libraries completely useless. I gave them a month or 2 to see if they would fix/revert, and when it only got worse, I decided to ditch Sonos completely because of no longer having confidence in their vision for a path forward. I ended up selling most of it (kept 1 x Play:1 for testing), and started playing with a couple of different alternatives, namely Bluesound, Bose and WiiM.

I ended up replacing my entire setup (and more) with WiiM. Compared to Sonos, it works remarkably well, is stable, always available. Sounds quality is on par, and surpasses in some cases. When I was running into constant connectivity issues even with a much simpler setup on the Sonos equipment, WiiM had absolutely zero issues with the same exact environment. WiiM has grown with me as my networks changed and got more complex, and they haven't missed a beat (no pun intended).

Like I mentioned, ever since Sonos' appocalypse, I have tried seeing how things were going off and on throughout their promises to make things better using my Play:1. I can tell you, their S2 app was ridiculously bad, and still had major disfunction a year+ later. When they added the functionality to allow you to downgrade your equipment and app to S1 again, that was the magic moment when things started working reliably again.

There are also some fantastic threads dedicated to this on Reddit and even Sonos' own community forums, and nobody has ever really been able to pinpoint or come up with a solid fix. It always fascinated me that there were so many people out there with crap tons of varieties of different networks and hardware out there all experiencing the same problem. The standard point-the-finger blame game response that Sonos fanbois always continue to repeat is "iTs yOuR nEtWorK"... or "just go through and reboot your router when this happens", or "you just need to go around and factory reset all your speakers every day". Cracked me up, and so glad I didn't have to deal with all that.

So my advice to you... downgrade to S1 if your equipment is capable (not all newer equipment can), but that would literally fix 99% of your connectivity issues and other functionality problems. Just wanted to share my pain... and give my 2 cents. ;)
 
Personally never ever had any Wi-Fi issues with Sonos One and One SL, using four (4), all on Sonos OS S2. Not using Mesh, simply connecting to dedicated 2.4GHz band, works for 5 years with RT-AX86U and always up to date firmware on both Sonos and router.
Never had luck with dual band, best to keep the bands separate, use wired access points for larger homes...
 
Last edited:
I also have this problem with my sonos setup - ARC SL + 2x One SL + Sub Gen ...
The ARC connects fine but the other speakers wouldn't when I had the IoT Network created without sharing the same subnet...
Currently I have it under the same subnet and all the speakers work - defeats the point of a separate IoT network.

I also tried it with the previous firmware e.g. 3006.102.4 and 3006.102.5 but the results were the same.
Hopefully when Asus fixes the problem with the new firmware, Merlin follows soon after 😁
You could also try another workaround that I have tested and it has been working for a couple of weeks for me. With that workaround you can have a guest/iot network enabled with different subnets.

Take a look at my post here

 
You could also try another workaround that I have tested and it has been working for a couple of weeks for me. With that workaround you can have a guest/iot network enabled with different subnets.

Take a look at my post here

Thanks!
I will try it out and see if that resolves it.

In the meantime I have been experimenting with the IoT network option and when I move all the speakers over to the IoT network with a different subnet, the speakers all work without any issues…
 
You could also try another workaround that I have tested and it has been working for a couple of weeks for me. With that workaround you can have a guest/iot network enabled with different subnets.

Take a look at my post here

This fixed the problem!
Thank you very much - I as well included the command in the startup script and it works.


Update: the problem returned... unfortunately this also didn't work 😩
was constantly getting the following messages in the system log:

Jan 9 20:50:42 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:31:b2
Jan 9 20:50:42 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.103 48:a6:b8:5a:31:b2
Jan 9 20:50:51 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:2f:42
Jan 9 20:50:51 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.104 48:a6:b8:5a:2f:42
Jan 9 20:50:54 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:2f:42
Jan 9 20:50:54 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.104 48:a6:b8:5a:2f:42
Jan 9 20:50:56 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:31:b2
Jan 9 20:50:56 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.103 48:a6:b8:5a:31:b2
Jan 9 20:50:57 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:31:b2
Jan 9 20:50:57 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.103 48:a6:b8:5a:31:b2
Jan 9 20:50:57 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:2f:42
Jan 9 20:50:57 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.104 48:a6:b8:5a:2f:42
Jan 9 20:51:01 dnsmasq-dhcp[4193]: DHCPDISCOVER(br0) 48:a6:b8:5a:31:b2
Jan 9 20:51:01 dnsmasq-dhcp[4193]: DHCPOFFER(br0) 192.168.50.103 48:a6:b8:5a:31:b2

The speaker One SL's and Sub would show as not connected in the Sonos app and no sound was coming out of the speakers...
Arc were connected without problems.

Connected all speakers to the IoT networks by updating the network on the Sonos app and now all speakers are connected and working.
 
Last edited:

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top