Working great for months, I add a port and now my speakers are cutting in and out across the board

Ignore feature?  From Gainsight?  Bwahahaha!

I’ll probably get censored or worse but sometimes things need to be said…

Why do people find it necessary to say “l have business grade” or “Enterprise” grade WiFi. That’s an incorrect statement all day long.

Wi-Fi 7(be) or whatever… is WiFi 7(be) in a home or business. It’s a standard set by the WiFi Alliance in conjunction with the IEEE. I’ll leave it to the OP to research those organizations.

My ASUS Wi-Fi 7 AiMesh frequencies (2.4Ghz, 5Ghz and 6Ghz) is the same frequencies as the WiFi 7 in a government agency. The only difference is the hardware. I will allow that a government agency may use a fourth band not available to mere mortals but for everyone else it’s SOP. BTW…No hardware is immune to network issues. So either provide more information about your network or follow ​@Stanley_4 ‘s and others advice to contact Sonos Tech Support.

Another pet peeve (although not mentioned in this thread) is informing people that one is an “IT Professional” (or other credentialed). Mention of such just begs the question “why are you here seeking advice”. Humility is a virtue.

Things do working perfectly, until they break, most often due to a change. I strongly suspect it could be network related.

I know you have written a Sonos controller, from previous posts (and your username). Here is what I would do:

You have some code that discovers Sonos devices and controls Sonos devices. If I was a coder, I would look to extend my program to provide a ‘Sonos Health’ feature, this could request the support/review pages from each Sonos device, measure latency to each Sonos device, and look at the /sbin/ifconfig section to get some network stats. Poll devices, and show the delta of the packets/traffic/errors for the interfaces on the Sonos devices. Could be displayed on a dashboard type page, which would be opened using a ‘Hot Key’ in your Application, and could help identify any network related issues.

Sonos could do a lot more to aid users in finding and fixing things but it looks like they are only going to provide minimal access, likely a legal department decision. 

It would be nice to have an app that collected what little info is available in a single spot (Good grief!) the number of taps to see something as simple as signal strength at each speaker is beyond belief. Oh and you need a scratch pad to note all the scattered information.

Sonos suffers from both legal and marketing issues, both or either of which trump developer's and user's desires.

I think I am on to something.

I have a fairly large house, with 9 sonos speakers.   I recently added a port to my theater room and thought ‘cool it’s near my switch in there so I’ll hardwire it’.

Well...if I understand correctly, that enabled Sonosnet - and that’s what my system was telling me.  

Then I noticed my phone would drop wifi in the middle of my house - I have 3 Omada Wifi 7 Tri-band APs.  All hardwired.   There should be no place in this house there is no wifi.

Well...my port is in the middle of the house.   Like a lot of you I am sure, I have a lot of things on my wifi - I suspect that my wifi & Sonosnet were battling it out for the frequency range depending on what was going on - most of my system is SL’s so they are all 2.4.   

My current test.  I have disabled two of my APS and left the central one in place. I have disabled the wifi on my port and forced it to be the controller. This has forced my speakers to stop using Sonosnet and use my wifi.

So far, so good.  Zero drop out.  My phone doesn’t drop wifi anymore.   That said, I’ve had the system work fine for a while and then hose up, so we shall see.

I am tentatively optimistic.  

I will report back in a few days.   

Yessir this is exactly what I have done.  I have added a Topology logging system.  Dig it.

An easier option:

Glad you have found the issue, back to coding now. 😁

See if you can ICMP ping and/or http get on the support review page in your ‘Topology’ section, that could be useful to identify any packet loss/latency issues, that would have shown up with your STP loop when you hardwired the Port.

Unless you have a need for Sonosnet it is really better to leave it disabled.

It is older technology than modern Wi-Fi and less reliable.

It requires a clear 2.4 gHz channel, with only three available that limits your other networks.

If it is enabled you need to deal with all the fallout from having multiple network paths available.

Turning off the internal radio, aka disable Wi-Fi, accomplishes the above as well BUT as it disables the radio it is no longer available for other network functions.