I would look at the mDNS settings on the Cisco AP’s and make sure that it is enabled as the new Sonos App seems to now need this. (There appear to be quite a few settings there so could take some experimenting.)

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/csbap/CBW_Admin/Admin/en_US/b_Cisco_AP_Admin_Guide/b_Cisco_AP_Admin_Guide_chapter_01001.html#id_129506

Also anything that might prevent SSDP discovery could cause issues. 

If you are using the two bookshelf speakers for surrounds to the soundbar, I think (others will confirm) that they need to be wirelessly connected to the soundbar. 

On your 3750, make sure any discovery protocols are also enabled. You may also want to ensure that the switch is acting as an STP root instead of the Sonos kit and that it has a low root bridge ID or 8192 or possibly 4096. 

Network engineer can’t figure it out, what hope do us common folk have? 

Possibly a little bit more as we don’t have enterprise grade gear with a myriad of options to configure correctly to get it going… we just rely on someone else having made some decent choices on our behalf. 

 I would leave them all wireless.

Nice thank you @Ian_S ,

I did try to turn on mDNS, but it did not change a single thing. I will dig around tomorow, do you have any technical specs of what sonos devices uses and how? Same for SSDP.

Not using bookshelfs as surround, those are added to other rooms.

See where are you heading with STP setting. The famous sonosnet. Well actually I turned on wifi on sub and the system was dead unstable for abou an hour. Running ping from then and it seems stable now, tho I can not play music cause kids in bed… So I thing those hicups where from migration of mac adresses to sonosnet as it seems both wireles and wired interfaces have same mac adress, and now I can not see any of those 4 devices connected to APs, but can see them in router device table. Have to check switch if those are hidden behind one ehetrnet port.

It is such a shame that there is no whitepaper about system requirements and setup easily obtainable. Every troubleshoot I have come around, even from sonos employees is just blind trying, no extensive research…

For example, played music fine on beam and bookshelfs, without mDNS turned on while sub wifi turned off (tho no sound from sub), but why there is an obtion to turn it off when it is crucial for proper function??? It seems to mee that mDNS is not the cause of my problems.

This :D

Wire means less response times → that is always better, wonder if Sonos guys know that stil prefering 2,4GHz spectrum …….

You buy complicated gear you have to expect complicated issues and solutions. I used to love having all kinds of fancy stuff for my network, now I want stuff that just works while providing the services I need.

I haven’t dropped back to using an ISP supplied router or even a consumer grade one but the rest of my stuff is as simple as I can keep it.

And yes to WiFi only, Sonos has clearly indicated that is the future.

You will need mDNS on once you get past whatever the current issue is, as the new app uses it now for discovering the speakers. 

I don’t know if this thread is of use as it sounds like when you connect the Sub over ethernet *and* enable WiFi, it is trying to create Sonosnet and STP may then be causing you stability issues. 

You’ll need to look at your switch and AP’s at a guess to make sure it all aligns. 

If you’ve not done so, it may be worth setting fixed ip addresses for your Sonos devices. They do otherwise seem prone to issues with duplicate ip address conflicts. 

 I thought the sub works off 5GHz from the soundbar.  No need for Ethernet.

I´ll definitely do that.

I addresses are stabili assingned without any changes.

My frustration comes from Sonos not using my perfectly stable wifi and network….. I did not have time to make more troubleshooting, using this setup just with airplay for now. (everything on wifi, just sub on ethernet with turned on wifi), and it definitely is reaching sonosnet limits in our house, it keeps disconnecting in specific situations.

I will try to make an excesive testing next weak, and will share results.

Hello there,

so I did no extensive testing at all…. But my system is stable and absolutely fine working.

What I did was an extensive research (while sitting on toilet mostly ).

STP has nothing to do with my initial problems. Nor does any setting on my network. I have return averything to default settings now. No mDNS, no multicast proxy, no STP settings fidling. It was just plain old  2,4Ghz not know how good equipment trying to work in conditions where it just can not (even tho there is no other 2,4Ghz wifi than my own).

My steps were simple.

1. connect everything I can with ethernet → Beam, Sub, 1x Symfonisk
2. turned of wifi on every one speaker conected with ethernet (I was strugling to do it on Sub, but found this solution and it worked  what a shame SONOS….. )
3. connected remaining Symfonisk to my own dead stable wifi.

Now listening without hickups, sub connected to beam withou any issues, no network otages, no loss of speakers in app.

My big frustration is comming from lack of the documentation…… From at least 15 years old design with using sonosnet, and lack of documentation how does it work. This is just obsolete now and they should at least document how to avoid using it when having superior network instaled. And about thousand posts on how the sub and beam HAVE to have wifi turned on even tho on ethernet…..  

But it is worth to mention that if I did not connect anything with ethernet and just use my wifi it wolud probably work out of the box .