Skip to main content

I started with a Sonos 3 in my kitchen. Worked pretty well, but finicky and needed resetting several time.  I added an older Sonos 5 to my living room.  Same.   Then I added a Move.  Great when it works but an absolute PITA to keep the system running.  I’m forced to use the S1 app because the 5 is too old to use the S2 app but that worked fine until  a few weeks ago when something happened with our router and we had to re-establish everything connected to it wirelessly.  Alexa, the printer, wireless controlled lamps, and (sigh) Sonos.  And it has not worked right ever since. 

For a while, the app could find Kitchen and Living room OR Kitchen and Move, but never all three.  And now it can’t find anything but kitchen despite a router reset and following the “find lost device” instructions.  And I sit here not listening to music AGAIN.  I would never in a million years recommend this system to somebody I like who isn’t a fn networking engineer. 

Sounds exactly like router trouble, which you changed a few weeks ago. So please detail exactly what network hardware you are using.


a few weeks ago when something happened with our router and we had to re-establish everything connected to it wirelessly. 

It sounds like it’s the router rather than Sonos that’s the ‘PITA’. 

It could be as simple as an IP conflict after the router was ‘reset’. Power the Sonos units off and on again. It that doesn’t help then power everything else -- other than the router itself -- off and on again. Or simply wait a day or so and the IP conflict should clear on its own. 


It’s been many days now, we’ve powered all the units off and on countless times to no avail.  We’ll be looking into the IP conflict issue, thank you.  and when I say “we” I mean my IT-literate son


It’s been many days now, we’ve powered all the units off and on countless times to no avail.  We’ll be looking into the IP conflict issue, thank you.  and when I say “we” I mean my IT-literate son

Please also say which router you have, if the answer is, for example, ASUS, we could all save a lot of time on this thread.


the router is a Unify Dream Machine

 


the router is a Unify Dream Machine

 

Ok so you’re a network admin. Make sure STP is set correctly, and the also rules for broadcast and multicast then. Good luck with that.


I’m not a network admin, my son is an amateur net admin.  He got them working but had this to say:

“For reference, I completely wiped their network settings and redid them on each speaker and they work again.  For now.”

Before that, it was:

“I really wish I could, y’know, trigger a factory reset remotely, but that’s obviously too much for speaker giant Sonos”

“these are genuinely the most frustrating pieces of networking equipment I have ever used.  I hate these things.”

 


I’m not a network admin, my son is an amateur net admin.  He got them working but had this to say:

“For reference, I completely wiped their network settings and redid them on each speaker and they work again.  For now.”

Before that, it was:

“I really wish I could, y’know, trigger a factory reset remotely, but that’s obviously too much for speaker giant Sonos”

“these are genuinely the most frustrating pieces of networking equipment I have ever used.  I hate these things.”

 

You shouldn’t really have let your son install a commercial grade router in your home then leave you hanging. Search this forum for the details of getting a UDM working on Sonos. And no, it isn’t straightforward, no wonder you are having trouble. Toss it and get an Amplifi - same company, but out-of-the-box Sonos compatible and you don’t need to be a network admin.


I love my Ubiquity gear but I’d sure never install it or recommend it to a friend!

Sonos used to have a reboot function, they took it away to keep us safe.

Something I had to do here is set static/reserved IPv4 addresses in my DHCP server. Without that I had issues at almost every update or power flop.