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

    ratty
    Apr 3, 2019 9:36 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.
    This tallies with my comment about 'reservation by default' in some routers. Those supplied by BT in the UK are a case in point.
    Translate
    Apr 3, 2019 9:39 AM UTC
    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 is all too much.
    To the earlier point I made, I find Echo response, even in grouped mode, to be good enough for a music system as described above. Is this achieved without the kind of "remorseless" talking to each other where Sonos is concerned? And if so, making Echo less vulnerable to such issues and therefore needing less user involvement? And if yes, I would call that tech progress made by Amazon - which is also to be expected given the time gap between the two product lines, which is huge given the nature of the tech.
    Translate
    pwt
    Virtuoso
    Apr 3, 2019 9:40 AM UTC
    This tallies with my comment about 'reservation by default' in some routers. Those supplied by BT in the UK are a case in point.
    Isn't it the case that most routers will repeatedly hand out the same IP address to the same MAC address, provided the lease hasn't expired or been explicitly released? (Subject to the router not having been restarted.)
    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
    ratty
    Apr 3, 2019 9:43 AM UTC
    This tallies with my comment about 'reservation by default' in some routers. Those supplied by BT in the UK are a case in point.
    Isn't it the case that most routers will repeatedly hand out the same IP address to the same MAC address, provided the lease hasn't expired or been explicitly released? (Subject to the router not having been restarted.)
    Yes, the client would request lease renewal of its current IP. My point was that even with a cold-started router and a cold-started client the same IP address could always be handed out to that specific device.
    Translate
    pwt
    Virtuoso
    Apr 3, 2019 9:47 AM UTC
    Yes, the client would request lease renewal of its current IP. My point was that even with a cold-started router and a cold-started client the same IP address could always been handed out.
    What happens in the case of a Sonos player rebooting (e.g., during an update)? Does it relinquish its lease prior to shutdown? Does it record its IP address for use in the DHCP request on restart?
    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:50 AM UTC
    Leaving aside the ongoing discussion about some routers dispensing with need for IP reservation, something I don't fully understand: what is remarkable about Sonos is that 15 years on, via having one unit wired to the router, wireless music play is as stable as the best kit designed and made by others today. Of course, users will validly complain about needing the wiring for best performance and/or IP reservation, because they will only look at the state of the art/world today to compare. But that does not take away from the quality of the engineering built into Sonos back in 2005.
    Translate
    ratty
    Apr 3, 2019 9:55 AM UTC
    Yes, the client would request lease renewal of its current IP. My point was that even with a cold-started router and a cold-started client the same IP address could always been handed out.
    What happens in the case of a Sonos player rebooting (e.g., during an update)? Does it relinquish its lease prior to shutdown? Does it record its IP address for use in the DHCP request on restart?

    I've no idea whether it sends a DHCP Release. And one assumes that it has to follow the standard Offer/Request on reboot. I somehow doubt it caches its original IP to use in the Discover. I've never sniffed that exchange.
    Translate
    Sjoop1985
    Apr 3, 2019 10:01 AM UTC
    But that does not take away from the quality of the engineering built into Sonos back in 2005.
    Is this not also a part of the answer to your other question?

    Does Sonos have to forego some innovation in their system to cater for backwards compatibility to older devices, whereas Amazon is working with devices that are relatively recent compared to Sonos?
    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 10:11 AM UTC

    Does Sonos have to forego some innovation in their system to cater for backwards compatibility to older devices, whereas Amazon is working with devices that are relatively recent compared to Sonos?

    Good point/question. And one that will become a larger issue for Sonos as there is more tech progress in areas such as advanced voice control and other smart home stuff. I am glad I don't have to make those decisions for Sonos about managing the two pulls in opposite directions!
    And for Amazon, because their devices are a significantly lower price point, there is less of a user investment to care about in releasing new kit.
    Translate
    Sjoop1985
    Apr 3, 2019 11:10 AM UTC
    And one that will become a larger issue for Sonos as there is more tech progress in areas such as advanced voice control and other smart home stuff. I am glad I don't have to make those decisions for Sonos about managing the two pulls in opposite directions!
    They have already been forced to start differentiating featurelevels between older and newer devices, like with Airplay 2 support, something, as far as I know, they hadn't done up to that point. At some time they will have no choice but to deprecate something more significant than a controller.

    While I understand the outrage at "bricking" a device for the sake of "the ecosystem" tomorrow that is functioning perfectly well today, you could ask if it is really that big of a deal, in this day and age. Try to use a phone or a computer from 2005, you will find it as effective as a brick as well. A lot of people seem to have no issue shelling out ever increasing amounts for a phone every 2 or 3 years, even if their old phone still works fine, so why would it be an issue if a Sonos device gets bricked?

    Somewhat off-topic maybe, but something to think about when contemplating the merits of the concept that is Sonos, especially on the point of the wireless technology it employs and the evolution thereof.
    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