Skip to main content
Contributor I
Oct 7, 2017 10:53 AM UTC

Why the concept behind Sonos is basically flawed

I thought I would like to share my thoughts on why I would never recommend
Sonos to my friends. After having given it some thought, in my opinion, the whole
concept behind Sonos is basically flawed.

First off, a little about my current Sonos situation. Today I have, and enjoy, a
fully working Sonos system with multiple devices spread across several rooms.
The system is stable, because at some point I decided to cable everything.
The majority of my past Sonos problems could all be related to wireless instability.

Here is why the concept behind Sonos, in my opinion, is basically flawed.

Sonos is sold as a speaker system with flexibility and ease of use as part of its core values.
The idea is simple. The speakers look good, and can easily be moved around
your home in various wireless configurations. I dont doubt that for many users,
this is in fact reality (eventhough the speakers are probably rarely moved around).
However, if you inspect the troubleshooting section of the community, you will see that
many Sonos users are having trouble with the wireless stability of their systems.

The answer from Sonos support is almost always the same - "Your wireless network
is not good enough.. you need to improve or otherwise change it". The user is left
confused, because most often the wireless network is performing sufficiently in all other respects.
Somehow the Sonos system is introduced as the weakest link on your wireless network.
There may be plausible technical reasons for this, but how was the user supposed to know?
And worse: The user has no way of knowing upfront, if this will be an issue on your network.
You may end up lucky, or not, it is a flip of the coin.

The weaksest link in your upcoming Sonos environment, will be the one factor
for which Sonos cant take responsibility - and for which you can never be sure to
fullfill the requirements.

To me this proofs that the whole concept behind Sonos is flawed.
    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.

    46 replies

    Apr 3, 2019 7:28 AM UTC
    @tphren :i agree with the post, I have brand night hawk router with a download speed of 300 mbps . my play 5 sound use to break frequently while airplaying from my MacBook. Yes, it works better when playing through the Sonos app directly using the iPhone. to get rid of this issue I had to hardwire the network and now its working fine. the other issue is being such an expensive speaker they only support 2.5 GHz network which is basically shaming. I also have Bose Soundtouch 30 gen 3 and I find it a lot better and simple than Sonos play 5.To condemn Sonos because it doesn't work well when airplaying from a Macbook is almost funny. For marketing reasons Sonos had to add Airplay, having long resisted this unreliable technology. And it doesn't matter how fast your router is if there is wireless interference, for example. With a bit of effort, your Sonos system could have worked fine with just one Sonos device wired (to invoke SonosNet) or maybe even fully wifi. That is how I, and millions of other users worldwide, happily run our systems. A flawed concept? Not at all.

    There are very good reasons for using 2.4GHz for a multiroom system - better range and wall penetration than 5GHz, in particular. For Sonos HT setups, where low latency is crucial, and wall penetration isn't, Sonos uses 5GHz. Shaming? Not at all. Deliberate and technically justified.
    Translate
    Sjoop1985
    Apr 3, 2019 8:34 AM UTC
    What I find interesting as well, is that while it will always have the inherent vulnerabilities of a wireless system, the added issue of relying on the home Wifi environment was also brought on by public demand.

    What is now called "boost mode" was once the only way to go, you were required to use a Bridge or wire at least one device. This had the advantage of always using SonosNet, which (by the accounts read on this community) has always been the more stable option. It was also relatively easy for Sonos to troubleshoot through their diagnostic system. I've run my Sonos in "boost mode" ever since I bought it, without any significant performance issues, besides my network misbehaving. I'm in the Netherlands where, like in the UK but unlike the US, most houses are brick and concrete resulting in a less than friendly home for wireless signals.

    Because people were being put off buying Sonos due to the "it's not truly wireless!" claims and competitors advertising with "no bridge required", they were forced to implement the Wifi mode, and with that expose the user experience to the unpredictive nature of the users home Wifi.
    Translate
    Life is what happens to you while you're busy making other plans (John Lennon) --- Living room: Arc, Sub, 2x One - Kitchen: One - Bedroom: Play 3 - Office: Beam - Bathroom: Play 1
    Apr 3, 2019 8:52 AM UTC

    Because people were being put off buying Sonos due to the "it's not truly wireless!" claims and competitors advertising with "no bridge required", they were forced to implement the Wifi mode, and with that expose the user experience to the unpredictive nature of the users home Wifi.

    Good point; WiFi mode was a marketing tick the box to address this issue. Wiring one Sonos unit to the router is still the only way to go for stable performance where more than one/two zones are involved. Even where this unit needs to be a Boost, the per day cost of it over a 5 plus year useful life is peanuts compared to what it delivers.
    And the other thing that needs doing for stable performance doesn't involve any cost - reserving IP addresses in the router for all Sonos units including controller hosting devices.
    Translate
    revdv
    Trending Lyricist I
    Apr 3, 2019 9:01 AM UTC
    [quote=Kumar]
    And the other thing that needs doing for stable performance doesn't involve any cost - reserving IP addresses in the router for all Sonos units including controller hosting devices.


    Yes. And my system over 3 floors in an old, stone house (v bad for wireless) is now rock-solid, having had so much input here from the community. Changing channels, using SonosNet, buying a Boost and reserving IP addresses has stabilised everything. But having to go into the router to reserve IP addresses or change wireless channels is not what most users will want to do (but totally worth it). Another advantage of having the phone controllers use SonosNet is that phone wifi coverage is so much better all over the house! No dead spots.
    Translate
    Sonos Roam SL, Play:1s, Play:5, Connect, Connect Amps, Boost. Arcam AVR5. Synology Diskstation. Harmony Ultimate "one remote to rule them all"
    Apr 3, 2019 9:16 AM UTC
    However: in parallel I also use Echo/Dots around the house, some that are wired to the line in sockets on Sonos. While none of them play in stereo paired mode, or in grouped mode except on rare occasions, I find music play from them to be just as stable with nothing wired to the router, nor any IP reservation done for the units.
    Whether this indicates a technology edge that has been eked out by Amazon over Sonos isn't something I have an answer for. I would not use any such progress if made by Amazon to say that the Sonos concept is basically flawed seeing that it was first deployed fifteen years ago. But it does indicate that there needs to be less user involvement for Echo to deliver stable music play.
    Translate
    pwt
    Virtuoso
    Apr 3, 2019 9:16 AM UTC
    But having to go into the router to reserve IP addresses or change wireless channels is not what most users will want to do ...
    The evidence suggests that this kind of intervention is only really required in a very small proportion of Sonos installations. There are many millions of Sonos users whose systems work perfectly out of the box, without recourse to this forum or any other form of support.

    However, if one does encounter issues, this forum is a fantastic resource, with some very knowledgeable and helpful people willing to give up their time to assist.
    Translate
    4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
    Apr 3, 2019 9:25 AM UTC
    All good points from @Sjoop1985, @Kumar and @revdv. I suspect most users don't need to reserve IP addresses (I never have), but if a system is experiencing problems, especially after updates, this can be a useful element in tackling the issues.

    It seems to me that when users do have problems with Sonos, a large proportion of them result from using Sonos in ways it wasn't originally designed for, but which Sonos has had to make possible to remain competitive, for example:
    1. Using it in fully WiFi mode (particularly where extenders are involved)
    2. Playing content stored on a mobile device
    3. Using Airplay
    4. Using line-in for TV audio
    5. Voice control

    Even in these examples Sonos works well for most users.

    One objection I sometimes hear is 'there is nothing wrong with my network, everything else works fine'. This ignores the fact that a Sonos system does make greater demands on a network than 'standalone' devices. Potentially a large number of Sonos and controller devices have to stay in constant touch. SonosNet does that best.

    Edit: good point from @pwt too, but our posts crossed!
    Translate
    Apr 3, 2019 9:27 AM UTC
    [quote=pwt]
    The evidence suggests that this kind of intervention is only really required in a very small proportion of Sonos installations. There are many millions of Sonos users whose systems work perfectly out of the box, without recourse to this forum or any other form of support.

    I am aware of the hospital syndrome, but I am under the impression that not reserving IP addresses is something that will inevitably trip up a Sonos installation - sooner or later - as it goes through its frequent upgrades. Is that not the case? Is it that many who do not do this cope by the power down method used for even computers when things hang?

    The other question I have is that in relying on Sonosnet for most stable performance, is Sonos giving up leveraging the improvements in home WiFi tech over the last 10-15 years? It would seem that kit like Echo that offers no such option, is more stable these days than it would have been a decade ago if launched on a foundation of home WiFi tech then prevalent.
    Translate
    ratty
    Apr 3, 2019 9:29 AM UTC
    A couple of points about IP reservation. These days a number of routers don't simply allocate IP addresses sequentially; they hash the MAC address into the available pool, which tends to result in a device always getting the same IP. (In the event of a hash collision the router would pick the next available IP.) This results in a kind of 'reservation by default', though it's not as guaranteed as a fixed MAC-IP mapping.

    Where IP conflicts do occur, for most devices which simply talk to the outside world it's rather a case of "the internet's slow today". A day later the IP leases have renewed, the conflict's been purged, and the problem is forgotten. Sonos however is more sensitive to IP duplication because the local devices are remorselessly talking to one another, as well as to the controllers. Packet loss due to IP conflict is therefore much more significant. In groups latency is critical for sync, so re-transmission may result in dropouts. And for those who want their music systems to be dependable and instant-on, waiting for a little local network difficulty to clear on its own is all too much.
    Translate
    Apr 3, 2019 9:33 AM UTC
    I am under the impression that not reserving IP addresses is something that will inevitably trip up a Sonos installation - sooner or later - as it goes through its frequent upgrades. Is that not the case?
    I would say it is not the case, based on having a large number of friends and family with Sonos systems who have never had problems, despite never reserving an IP address, or even having heard of IP addresses in most cases.
    Translate