Skip to main content
IanJShaw
Chromatic Producer I
Jul 17, 2025 11:15 AM UTC

Is the Sonos ecology just too diverse now?

So, many months on from that event and my Sonos system is still best described as “quirky and unreliable”.

 

I won’t produce yet another list of things that go wrong, there’s plenty on here already.  But every time I open the app now I routinely expect, and get:

 - players refusing to join an existing group “try again later”

 - the app refusing to control an existing group

 - music taking up to 30s to start playing across a group of players (I fondly remember the days when I heard the beginning of the first track in a playlist)

 - etc.

 

All of these are resolved with patience and the digital equivalent of “jiggle it about and try again”.  And I usually manage to have a working system that plays my music within about 5-10 minutes of frustration and annoyance at the beginning of every session of playing music.  I’ve come to expect it now.

 

But I’m wondering if one of the problems is that I’ve now got over 20 different players, of pretty much every S2 compatible type, which spans several generations of technology.  Am I really trying to get hardware to work together seamlessly that, frankly, just isn’t up to the job?

 

Now, I know there would be a huge backlash if Sonos came clean and said something like:

“Hands up.  If you really want a responsive, controllable, reliable system then don’t mix products between generations.  So, for example, never expect a Era 100 to play nicely with a first generation Sonos One, they just aren’t fully compatible”.

 

But, given that I have got used to there being some “problem” players in my setup and am almost coming to this conclusion myself, might it not be preferable to the current fiction where we’re told everything “should” or “will” work together and constantly being disappointed?

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.

58 replies

Mr. T
Jul 19, 2025 9:11 AM UTC

So one example from 7yrs ago. Doesn’t appear to be a major issue that you’re implying it to be.

 

Maybe this thread could be another example you asked for, as it appears OP has reserved IP addresses?

I have never said its a major issue, as the vast majority of Sonos users do not assign static IPs, and they have fully functioning systems. If it was a major issue, Sonos would recommend it.

Some users have very unique/specific home network setups with ‘boutique’ type firewalls in a home setup, and may have a work around using reservations, but it does not apply to the majority of Sonos users.

All I’m asking is an open mind, just because something has been recommended in past by a few users with very specific network setups, does not mean it should be the default recommendation today.

I asked specifically around your comment that giving a reserved IP address prior to bonding with a soundbar would “probably fail”.

The OP has not mentioned that as an issue that they are experiencing, so not sure how you are drawing that conclusion.

I have reconfigured rooms with reserved IP addresses and moved speakers/sub from being a stereo pair/sub to a new soundbar numerous times without issue, so I queried your belief it would probably fail as it has never in my own experience.

I wouldn’t say reserving IP addresses is given as a default recommendation. It’s a suggestion given by some users. If there was no benefit to reserving IP addresses why would routers give the option in the first place?

Also can we stop using the term Static IP. Sonos does not implement Static IPs. Static IPs are not the same as reserved IP addresses.

Translate
Local Superstar
Jul 19, 2025 10:27 AM UTC

OK, sorry, maybe I should have used the term ‘may fail’ Lets look at another example:

 

OP says Sonos is working fine no issues, but concerned that they are seeing duplicate IP address in their router web page, this is just the way the router GUI presents the HT devices, its not an issue.

Its suggested that they reserve IP addresses.

Yes, I should have used the correct term IP reservation, post updated, sorry. static is often incorrectly used, even in the BT router page above, but we know what its referring to.

Translate
Mr. T
Jul 19, 2025 10:40 AM UTC

@craigski - We appear to be debating different things. That thread again is not related to your comment I was questioning, so on that basis I will leave this conversation.

Translate
Stanley_4
Grand Maestro
Jul 19, 2025 12:33 PM UTC

Hard to blame my issues on pfBlocker as it isn't installed on my router.

I see no issues with my HT setups with the reserved IP addresses and surrounds or Subs, they get the assigned IP and use it, they don't ask for or get other IPs.

 

Back to the bottom line here, some Sonos setups are unstable without reserved IP addresses.

Reserved IP addresses are easy to assign. 

Once assigned it is easy to observe the difference in stability.

If the addresses cause problems (I've never seen or heard any mentioned by folks I've recommended them to) they are easy to remove.

All the esoteric details don't really matter to someone whoo just wants their Sonos gear to work.

Until someone has a suggestion that works better in practice, not theory I'll keep suggesting it when appropriate. 

Translate
Lyricist I
Jul 19, 2025 12:52 PM UTC

Totally hear you, dealing with that kind of daily frustration just to play music is exhausting. Mixing older and newer Sonos gear definitely seems to cause more issues than they admit. It’d be a lot easier if they were just upfront about what really works well together.

Translate
Local Superstar
Jul 19, 2025 1:39 PM UTC

Back to the bottom line here, some Sonos setups are unstable without reserved IP addresses.

I would argue some network setups are unstable without reserved IP address.

I see the reservation is a recuring theme, so will probably go on and on, from last year:

Its interesting that you said you didn't have issues with your old router:

With my old all-in-one router I was not seeing issues, updated to a much better router and dedicated WiFi APs and was seeing issues until I set them.

 

I concur with you, you need to have IP reservations on your much better router configuration, due to the way its configured to handle DHCP. I still disagree that IP reservations are required today, unless there is some underlying issue with the network.

I’m flogging a dead horse, so we will have to agree to disagree.

Translate
IanJShaw
IanJShawAuthor
Chromatic Producer I
Jul 19, 2025 1:46 PM UTC

Just popping back in to say how fascinating I’ve found this thread.  Thank you everyone for your time and contributions.

 

I’m not an IP or electro-magnetic radiation propagation expert so a lot of this has gone over my head.

 

I have read Sono’s “how to deal with wireless interference” guidance and if I attempted to keep all my Sonos players between 0.5 and 1 meters away from all other wi-fi enabled devices I’d have to put them in the garden.  The rule on consumer electronics in 2025 appears to be “if it can be wi-fi enabled, wi-fi-enable it”.  And everyone in my house carries around mobile phones, tablets, laptops and smart watches.  I’m not going to put hazard tape around every Sonos player or start shouting at my partner when they get too close.

 

There’s something not right in my Sonos installation.  Your comments have proved to me that there are smoothly functioning systems out there and mine’s not one of them.  At the moment the only help I get from the Sonos software is “that didn’t work, try again later”.  Numerous calls to Sonos technical support have offered little more.

 

If the wi-fi environment in my house is the thing standing between me and a functioning Sonos installation I’d really appreciate the option of a bit more information from the software.  Something along the lines of:

“Sonos player:  Bedroom is experiencing a lot of interference, try moving it”

Or

"Cannot add room Lounge to group:  The group is already struggling to stay in sync”

would go a LONG way to helping me out….

 

Am I asking for something that the software will never be able to provide?

Translate
Local Superstar
Jul 19, 2025 2:12 PM UTC

Just popping back in to say how fascinating I’ve found this thread.  Thank you everyone for your time and contributions.

Apiologies for derailing. Did you try my suggestion before the derailment, ie turn off the oldest speakers and/or speakers in less used rooms for a day or so, and see how it performs?

  Numerous calls to Sonos technical support have offered little more.

If the wi-fi environment in my house is the thing standing between me and a functioning Sonos installation I’d really appreciate the option of a bit more information from the software.  Something along the lines of:

“Sonos player:  Bedroom is experiencing a lot of interference, try moving it”

 

Sonos support should be able to advise on that, they can see that info from diagnostics.

Also, what WiFi network devices are you using? Many have a management interface that will show the health of your wireless network down to device level.

Do you use iPhone? Have you tried disabling WiFi Assist:

https://support.apple.com/en-gb/102228

Translate
IanJShaw
IanJShawAuthor
Chromatic Producer I
Jul 19, 2025 2:23 PM UTC

Thanks ​@craigski 

 

No problem about the derailment - I think it’s a great illustration of how any attempt to engage with Sonos performance goes down detailed technical rabbit holes really quickly.  Almost my point in a nutshell.

 

Yes, I have tried turning off the oldest products, power cycling everything and then giving it a day or two.  No noticeable or consistent improvement I’m afraid.  (And that’s part of the problem.  All I’ve got to go on is my perception - some actual guidance from the software in measurable terms would really help).

 

Yes, I agree, Sonos support should be able to see the state of my network from diagnostics.  But my recent experience has been that there’s such a built-in delay between experiencing something with Sonos, calling support, getting through etc. That it becomes an academic exercise.  I would probably have to take entire days off to wait for a specific error to happen (my system is NOT consistent) and then immediately call technical support…  

 

I use four TP-Link Deco XE75s as access points with a TP-Link Archer router doing the IP assignment and connecting to the outside world via a 1Gb fibre connection. The Deco software isn’t the most forthcoming...

Translate
Mr. T
Jul 19, 2025 2:29 PM UTC

​@IanJShaw - I think there is a push to make error messages in the app more informative, but I don’t know if we’ll ever get to the stage where every issue can be clearly identified with a recommended solution. 

Going back to your original post, newer speakers have better processors, better wireless radios and more memory compared to older speakers. I upgraded from Play:1s to Ones to Era 100s in my kitchen as the Play:1s used to have dropouts long before the new Sonos app was launched. In my experience the Play:1s were more susceptible to wireless interference.

i would definitely experiment with having a smaller system as has been suggested to see if your experience improves, then gradually increase the components testing as you go. Obviously, the ideal scenario is to have all speakers functioning perfectly, but the process may identify an issue with one particular speaker/room which impacts on the overall system. If you still have issues with a smaller system, then adding additional components to the system is just going to exacerbate the underlying issue whatever that may be.

Translate