Skip to main content
Contributor I
Sep 16, 2025 9:36 PM UTC
Answered

Sonos dropouts on Omada network

I have many Sonos speakers at a home site.  Around 50.  They are split between two systems.  THe internet at this place is using Omada TP Link.  They are constantly experiencing dropouts on the sonos speakers or music just stops altogether.  Sonosnet really isn’t an option as most speakers are in home theater setups, or they are the new era speakers.  I have assigned each speaker a static IP and on all the managed switches enabled STP not RSTP, and MGMp snooping.  Now, I know enough about this stuff to be dangerous, but so far my tricks havent helped much.  Any help?  Do i assing the speakers to a specific nearest AP next.  Very frustrating.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Stanley_4
Stanley_4Answer
Grand Maestro
Sep 17, 2025 1:47 AM UTC

I don't think most users have 20 APs, a call to Support might be your best bet.

18 replies

Airgetlam
Sep 16, 2025 10:02 PM UTC

The max on a Sonos system is supposedly 32. I’ve never been that close, although I think ​some users here are (@Ajtrek1, maybe?) (oddly, the system isn’t working for tagging, he’ll likely read this anyway). 

But it’s still possible that you’re not hitting that, as you have them split into two systems. But that doesn’t remove the potential for the wifi interference , no matter what the router make is. I’m not familiar with any particular issues with Omada, in the grand scheme, but that doesn’t mean there isn’t a setting you may need to adjust, either. I think I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. Don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Translate
Bruce
Airgetlam
Sep 16, 2025 10:06 PM UTC

​@AjTrek1 

There, that worked, it appears. 

Translate
Bruce
Airgetlam
Sep 16, 2025 10:10 PM UTC

Dropping this here for reference:

https://support.sonos.com/en-us/article/incompatible-network-hardware

I note there’s no mention of Omada with any endemic issues, but there’s no date associated with that list, and things do change over time, which is another reason to call Support. 

Translate
Bruce
Contributor I
Sep 16, 2025 10:11 PM UTC

Ok ill give that a go unless I hear otherwise on this forum.  Thanks

Translate
Contributor I
Sep 16, 2025 10:22 PM UTC

is the max 32 devices per system, or 32 across however many systems you have?  THey have multiple places with soundbar, sub and rear surrounds, so that eats up a lot of devices.

Translate
Airgetlam
Sep 16, 2025 10:39 PM UTC

I think it’s an addressing thing, so it would be across a single system, and not across multiples. Based on the 32 number. 

Translate
Bruce
Airgetlam
Sep 16, 2025 10:43 PM UTC

I suppose it would be relatively easy (by some definition of ‘easy’) to test, merely by unplugging until you got down to, say, 30 or so, then testing. But I’m 98% certain it’s a per system number, and not affected by multiple systems. 

Translate
Bruce
Mr. T
Sep 16, 2025 10:45 PM UTC
Contributor I
Sep 16, 2025 11:10 PM UTC

Ok that’s what I thought. The second system has no issue that I know of. Most of the devices on that system are within home theater setups. So not a lot of music streaming. 

Translate
Airgetlam
Sep 17, 2025 12:15 AM UTC

Likely correct, most ‘crosstalk’ between speakers on a home theater ‘setup’ is local, and not through your WiFi, although they do receive IPs through the soundbar as a proxy. 

Translate
Bruce