Sonos dropouts on Omada network

​@Cornflakes81 

Just a few basics about Sonos systems in general:

• They are very “chatty” as they are constantly communicating across your network
• They can tax even the best configured networks 
• They typically don’t play well with Switches and Access Points (not to be confused with satellites in a mesh network)
• The number of Sonos Units on a system is thirty 32 (click here for more information0

The next links you’ve probably read but I’ll throw then in anyway:

• Known limitations with separate S1 and S2 Sonos systems | Sonos
• Set up separate S1 and S2 Sonos systems | Sonos

I have 31 units in my Mesh Network with no drops. However, I’m not running two systems which I suspect may be creating a lot of cross-talk and interference one to the other. Nor am I using managed switches which can be problematic.

I’d be inclined as ​@Airgetlam alluded to is to try and clean things up a bit. Simplify your Sonos maybe having a split system at the magnitude of 50 Sonos units just isn’t practical. I don’t have the answer so contacting Sonos Tech support is probably your best option.

Good Luck to get things sorted 😊

I’ve seen in some places to assign the sonos speakers to certain aps they are close to. There are 20 APs in this setup so would that help?

Side discussion, likely related, here:

Wow! 20 AP’s...OMG! 

I previously said I didn’t have an answer...and I still don’t. However I have a pretty good idea of at least one problem. 

With 50 Sonos units already talking constantly and 20 AP’s to boot; (not to mention other network traffic and let’s not exclude internal and external interference), there’s better than a 50/50 chance you have created a “Network Storm”. Below is an AI generated definition. I’ll let you draw your own conclusion(s).

A network storm

• Is a situation in which an excessive amount of broadcast traffic floods a network, causing it to degrade or even fail completely. This overwhelming volume of broadcast packets, often caused by network loops or misconfigurations, consumes bandwidth and overwhelms network devices like switches and routers. Symptoms include slow speeds, devices going offline, and flickering switch lights, which indicate the network is struggling to process the traffic

What is a broadcast packet? 

• It's like shouting in a room so everyone can hear you at once.
• A broadcast packet is a type of data packet sent from a single source to all other devices within the same network segment or broadcast domain.

How does it happen?

• Network Loops: The most common cause is a network loop, where data packets get stuck in a continuous cycle between multiple interconnected devices. 
• Misconfigurations: Incorrectly configured network devices can also contribute to a storm. 
• Malfunctioning Hardware: Faulty network devices can send out an excessive amount of broadcast traffic. 

How to detect a network storm: 

• Network Speed Slowdown: The network suddenly becomes extremely slow or feels like it's moving through "treacle".
• Device Disconnections: Multiple devices lose their network connection.
• Flickering Switch Lights: The lights on network switches may blink rapidly and brightly, resembling a strobe light.

It would be good to look at the wifi channels in use and their utilization percentages.

I had a batch of security cameras running that put my channel utilization somewhere above 50% and I was seeing Sonos, and other devices, having issues.

Do people know what ‘treacle’ is these days?

Well this house has 3 full functioning levels to it. Each level is roughly 2700 square feet including the garages. Plus we ran some outdoor APs to cover a very large deck and porches. Finally there is a large metal Buildbig/ shop that we bridged over to with 2 APs out there. There is a Sonos amp out there.