Maybe see if this earlier thread link assists with disabling Airtime Fairness etc.

Thanks! But I have tried that, and some other suggestions, still sucks…. I’m sort of really looking for if there are others that are running the same mesh, have tried a lot of stuff without result , then I might throw out the S2 system give up and maybe, maybe put all Sonos units in the garage S1 config

Just to say your Roam and any Sonos One SL devices on S2 cannot be used with the S1 App - if you can’t resolve the matter, it maybe best to reproduce the issue(s) seen and then immediately submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and contact/chat with Sonos Support Staff via this LINK and see what the Staff can perhaps suggest to help you to resolve the matter. 

I have Sonos connected wirelessly to an ASUS ZenWiFi AX XT8 mesh network with Primary node and satellite and have no problem with 20+ speaker connectivity.

Thanks Ken! See now that there has come up a lot of zen related topics that didn’t show up last time I checked (it was a while ago) btw the system came back just a while ago after I switched it to ch6, even though ch 11 wasn’t crowded……Looks like I can do some more of digging during the he hollyday, Merry Xmas!

PS! So I will be stuck with 2 speakers in the garage /workshop for a while then…

Hopefully you can get to the crux of the issue.. it sounds like the Asus mesh setup should work, as it appears to be working okay for others, like ​@Mr. T above, and the user in the thread I linked to earlier.

​@JensHolsteinKrag - have you considered trying to run Sonos wirelessly with the ASUS mesh rather than using SonosNet?

Thanks! Well, that might be an idea…. But I must say that I’m not sure how the speakers interact with each other on th Sonos net, and how they use the mesh… I can’t find anywhere to disable the Sonos net in the settings…. I can’t see any WiFi like activity connected to Sonos when I sweep the bands with my net monitor, so either it is well hidden or some other protocol that does not show up on the monitor. Maybe I should configure an SDR to look at how the RF environment look like Busy holiday ahead…

How they interact is complex and depends on your exact situation. Basic description is if you plug a Sonosnet compatible speaker into Ethernet it will start broadcasting a Sonosnet signal. Other Sonosnet compatible Sonos will try to join. Then you get over my head on special case situations.

There is no “disable Sonosnet” option, you can turn off the entire radio but then all other radio dependent stuff also quits working.

If you are using a monitor that looks for WiFi signal it will not see the Sonos hidden networks. Sonosnet or the 5 gHz surround/sub links. An RF based tool will see the signals.

Unless you have a need to run Sonosnet I can’t see a reason to get into that. I ran Sonos net for many years, not a problem as I had two clear channels, one for my WiFi and one for Sonosnet and all my Sonos were Sonosnet compatible. Now I’ve added new ones that are WiFi only and unplugged my three that were wired. Nothing changed from a use perspective but I do find the signal strength reporting more useful than the grid at the :1400 pages.

Thanks ​@Stanley_4 , well as I thought……

Here we go again! Our Sonos system goes bananas again after being sable and without  any glitches during the whole Holliday, but then suddenly it goes bananas and won’t connect the 3 One SL speakers that covers the kitchen/dining area, the wife is furious and are ready to send the Sonos system to recycling……  I try to restart them, nothing, reboot the main router, check for network interferences , no reaction, now they at least even show up as unconnected, I switch Sonos net over to ch 11 only to do something, I reboot the speakers again, after a while they shows up like teenagers at the dining table , ohh, sorry, forgot, were you waiting for me….. 

The network is just fine, nothing else is making a fuzz……  no it doesn’t looked we will upgrade any speakers in the near future, nothing else Sonos anyway if the wife has to have anything to say about it anyway , and she is the ex software developer in the family……

So here we go again…. Sonos has worked very stable for many days now… Eureka!  But this evening I updated to the S2 version 16.5.1, after the update the system went nuts and wasn’t out of control, no way to control it with the app…. So we gave up and let it be for an hour, then after trying to group the speakers all over again, it started working…… wow it works again, but don’t tell me this is ok that it takes an hour or so for everything to like magic, find each other…… 

If not done already, I’d perhaps try reserving the Sonos product IP addresses in the routers DHCP Reservation table - it sounds like your router is having difficulty reallocating the addresses when they are all rebooted post-update. See if making the addresses fixed/static will help with the issues seen on this occasion.

Sonos updates involve speaker reboots, and IP address issues sometimes arise. Reserving IP addresses in your router for your Sonos devices often greatly improves stability (but no guarantees!).

Comments about no other devices having problems are pretty meaningless. Your non-Sonos devices don't have to stay in constant communication with multiple other devices over the mesh. It's capable of doing so but some extra care is needed in configuration.

Edit. Ken beat me to it!

If you do add the static IP addresses you can force your Sonos to pick them up and use them bu powering down all Sonos, rebooting router and Controller, once they are back up power up the Sonos.

Usually easier to do that than to verify your router is moving the Sonos to the new addresses at the scheduled DHCP renewal interval.

Thanks Ken, but I have been using Static IP addresses for all Sonos units for some while now, think that was one of the things I tried when the app problems started… As I have written earlier, at first I thought I was my mesh network was the reason for the problems because I had just upgraded the system with more units to get better coverage……

Sonos is not using your mesh network as you have a speaker wired therefore your speakers are connecting over SonosNet.

Hopefully my Sonos system wont start goofing around now….. but the last 24 hour everything has worked as expected, ok I’ve been looking into the connections inside the mesh network between my four mesh units who routes the traffic between them and did some minor adjustments to try to optimize the flow…. There are no speakers on cable, all are handled by the mesh network, or do they use Sonosnet as well, have tried to look at the IP flow but it didn’t get clearer….. maybe it’s just coincidence that everything I working so well, maybe the app is doing what it should, maybe the S2 version works well now….. all the same , hope it stays that way now, have a nice weekend

For folks considering wiring a Sonos to Ethernet:

Any time you plug an Ethernet cable into a Sonosnet capable Sonos device it establishes a Sonosnet connection on the 2.4 gHz channel it is set to use.

You can disable the internal radio (labeled Disable WiFi - but kills the whole radio) to prevent a wired Sonos from creating a Sonosnet connection. Disabling the internal radio will also prevent connecting a Sub or Surrounds wirelessly.

All other Sonosnet capable Sonos in range of it will try to connect and use it and Sonosnet, ignoring your WiFi.

Non-Sonosnet capable Sonos will continue to use WiFi.

The Era line does have an external Ethernet adapter available, with it they will use the Ethernet but do not setup or use a Sonosnet connection.