Skip to main content
Trending Lyricist I
Oct 5, 2017 11:07 AM UTC

Don't buy the Sonos

I spent two and a half months trying to get this speaker to work. It has been replaced with a Bose bluetooth speaker.
    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.

    43 replies

    Trending Lyricist I
    Oct 6, 2017 8:45 AM UTC
    I think you should spend your money to upgrade your internet, get rid of DSL and get something decent first. Once you got that, Sonos will work for you. Your problem is you have a lousy internet with data rate that is insufficient. Good luck.
    Translate
    Trending Lyricist I
    Oct 6, 2017 9:39 AM UTC
    "Get rid of DSL". Not an option. Not everyone lives in the city. "Data rate that is insufficient". Read my posting further up. Only 400kbps or so is needed for streaming audio on Sonos. My download speed is 10mbps. That's not the problem. The Boost was hardwired into wireless router, and there is no channel hopping on my wireless router.

    What no one (including Sonos tech support) has explained, or attempted to explain, is why: 1) the problem got worse with time; and 2) why streaming the same XM channel through the same WiFi, through the same phone, into hard-wired headphones or my brand new wonderfully reliable Bose bluetooth speaker using SiruisXM's mobile app, works perfectly.
    Translate
    Avid Contributor I
    Oct 6, 2017 12:40 PM UTC
    Get rid of DSL ? What are the alternatives, fibre to the home ? Virtually everyone is on DSL, be it adsl or vdsl, it's very rare (at least in the uk) to have anything else.
    Translate
    Majik
    Oct 6, 2017 1:25 PM UTC
    PSA: It's not DSL.

    I say that from a position of expertise:

    I'm a Telecommunications Engineer with nearly 30 years experience, including substantial experience working on broadband distribution networks.

    I have created designs for, done implementation and testing on, and provided support on major carrier broadband network projects for companies including Cable & Wireless, BT, Eircom, Portugal Telecom, Telekom Malaysia and others. I've studied DSL technology, experimented with it in labs, and seen it deployed in action across millions of users on the projects I've worked on.

    At one point I was reporting to the Chairman of the DSL Forum.

    I've also been on Sonos forums for more than a decade, and have seen and interacted with tens of thousands of Sonos users over that time.

    If there was a fundamental issue or incompatibility with Sonos and DSL I would know about it.

    There is not. There's never been a sniff of an issue that there might be and, knowing DSL technology as I do, there's no reason for there to be an issue.

    ANYONE CLAIMING THERE IS A COMPATIBILITY ISSUE BETWEEN SONOS AND DSL DOESN'T KNOW WHAT THEY ARE TALKING ABOUT

    Cheers,

    Keith
    Translate
    Majik
    Oct 6, 2017 1:35 PM UTC
    Now we've straightened that out, there's lots of reasons why Sonos might not work properly on your setup. None are fundamentally related to using DSL.

    For a start, DSL does not have a higher latency than other broadband technologies. In fact, it tends to have a lower latency than some consumer broadband services, like cable modem.

    If you are getting high latencies then there is something fundamentally wrong with your service. For reference, I'm getting an average of just over 22ms ping time to Google DNS across my DSL service:

    > ping -c10 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=13.6 ms
    64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=24.8 ms
    64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=96.4 ms
    64 bytes from 8.8.8.8: icmp_seq=4 ttl=60 time=13.3 ms
    64 bytes from 8.8.8.8: icmp_seq=5 ttl=60 time=14.1 ms
    64 bytes from 8.8.8.8: icmp_seq=6 ttl=60 time=12.4 ms
    64 bytes from 8.8.8.8: icmp_seq=7 ttl=60 time=14.1 ms
    64 bytes from 8.8.8.8: icmp_seq=8 ttl=60 time=13.3 ms
    64 bytes from 8.8.8.8: icmp_seq=9 ttl=60 time=12.4 ms
    64 bytes from 8.8.8.8: icmp_seq=10 ttl=60 time=12.3 ms

    --- 8.8.8.8 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9011ms
    rtt min/avg/max/mdev = 12.341/22.709/96.447/24.829 ms


    I get similar times to www.sonos.com (on Akamai CDN):

    > ping -c10 www.sonos.com
    PING e7788.b.akamaiedge.net (104.105.51.189) 56(84) bytes of data.
    64 bytes from a104-105-51-189.deploy.static.akamaitechnologies.com (104.105.51.189): icmp_seq=1 ttl=57 time=12.9 ms
    64 bytes from a104-105-51-189.deploy.static.akamaitechnologies.com (104.105.51.189): icmp_seq=2 ttl=57 time=12.9 ms
    64 bytes from a104-105-51-189.deploy.static.akamaitechnologies.com (104.105.51.189): icmp_seq=3 ttl=57 time=13.0 ms


    This, or near this, is what you should be getting.

    If you are getting substantially higher than this, then there's something wrong with your DSL. It could, for instance, be congested. Are you, or anyone else in the house, streaming or downloading large files? This could max out the bandwidth which would cause high latency and packet loss which would definitely impact Sonos streaming.

    I could also be the router you are using is faulty. There have, in the past, been issues with some FIOS services, not because there is anything inherently wrong with FIOS, but because the routers being supplied by the ISP were defective.

    Alternatively, it could be issues with wireless coverage. Do you have issues when streaming from a local source, such as music files saved on a NAS or laptop?

    Cheers,

    Keith
    Translate
    Trending Lyricist I
    Oct 6, 2017 1:39 PM UTC
    I don't doubt your qualifications, and I do believe that my DSL should have been up to the task. It certainly is now with my new setup. But why didn't my Sonos work? No one knows as it turns out. Do you have any proposed ideas as to why it won't work? You seem qualified to at least speculate, since my DSL should be up to the job. Previously unknown flaw in software? Faulty hardware?

    At the risk of being repetitive: why: 1) did the problem got worse with time; and 2) why did streaming the same XM channel through the same WiFi, through the same phone, into hard-wired headphones or my bluetooth speaker using SiruisXM's mobile app, work perfectly?

    If i could find answers to these questions, from anyone knowledgeable, perhaps the problem could be solved. Despite all the diagnostics sent to Sonos, they have no answers after weeks of trying.
    Translate
    Trending Lyricist I
    Oct 6, 2017 1:45 PM UTC
    I didn't see the subsequent reply - my ping is the same as yours, as is the rest of the performance. I contacted my ISP and they find no problem with my modem or my wireless. When I had the Sonos, it worked fine at first, until after two months it reached a point at which I could not even stream music from my iTunes without skipping. There have been no other issues with any other devices using that DSL. Once the Sonos was removed and replaced with the bluetooth speaker there have been no issues whatsoever.
    Translate
    Majik
    Oct 6, 2017 3:31 PM UTC
    If streaming works, on your DSL, then it should work with Sonos. That points to it not being your DSL.

    Have you tried streaming locally, from files on a PC or laptop? Is this what you meant by "from my iTunes"?

    I would strongly suspect issues with wireless, and local streaming issues tend to confirm this. Wireless isn't as simple "as it-works-or-it-doesn't". It can work fine on one device but not on another. In some cases it can be because the working devices are interfering with the non-working ones.

    The other thing to bear in mind is that phones and PCs are designed as general purpose devices with gigabytes of memory. Phone apps, especially, are designed to work in environments with poor data and will tend to buffer a lot to compensate for the occasional spotty connection. Sonos systems, basically being speakers with embedded "smarts" will do this too, but have limited memory space to do this in.

    There's all sorts of things which can impact a Sonos setup in this way, including:
    - The topology of your network (wired/partially wired/totally wireless)
    - Using wifi or Sonosnet
    - The presence of potentially conflicting wireless devices such as DECT phones

    As a general rule, whilst wirelessly connecting Sonos to your existing wifi is more convenient, using the inbuilt "Sonosnet" mesh network is far more reliable. Many home wifi networks are not really built for robust streaming.

    Another test to do, if you haven't got this setup already, is to wire one of the units and deselect wifi in the app settings. This will make the Sonos units form their own wireless mesh separate from your wifi.

    I am surprised the Sonos support staff couldn't help you on this though.

    Cheers,

    Keith
    Translate
    Trending Lyricist I
    Oct 6, 2017 4:06 PM UTC
    "Another test to do, if you haven't got this setup already, is to wire one of the units and deselect wifi in the app settings. This will make the Sonos units form their own wireless mesh separate from your wifi." I did that. I spent another $100 on a Boost, and I had it hardwired in my wifi so the Sonos speaker had 'priority' - they walked me through all of that. It sort of worked at first, but got worse as time went on. We went through all of the checks for interference, changed channels through just about every permutation possible. The tech and I became so close we began to pick out drapes and furniture.

    It's sad, I really liked the system for the first three weeks I listened to it. It has many inherent advantages. The trouble with all these gadgets and their associated software is that it's so easy to get caught up in fixing it, tweaking it, troubleshooting it, that the original purpose of it becomes almost completely obscured: listening to music. Everybody at home would listen and say: "it's skipping again...it did it again!" I'd go to the bathroom and upon my return my wife would give an update of how many times it skipped in the 3 minutes I was absent.

    Sometimes I think the job of software people is to ruin lives and deliberately induce madness. I just want to spend time listening to music, not fixing broken-down shite or tracking down problems. I do that for a living in my lab; I don't want or need it after work, and once you lose my confidence, it's over.

    I see I have earned the badge: "almost famous" (see right side of page). I'd gladly go away if I had my money back. Until I feel like I have gotten $300 worth of moaning and complaining in, I'll stay around a bit, or at least until I get booted. In the weeks it took to deal with tech support back and forth, all of the return warranties had lapsed, and from Sonos (or Amazon) there is no sympathy to be had. I also love it when people chime in and say: "mine works fine and always has since the Cretaceous Era." Great. Mine doesn't and I'm out $300.
    Translate
    passopp
    Oct 6, 2017 4:07 PM UTC
    I'm using a similarly limited DSL broadband connection with peaks of 12.5mbit/s. Sonos works pretty much flawlessly in standard wifi mode. The only ongoing issue I recognized are constant dropouts with a single (rather exotic and small, thus bandwith-limited) webradio station via TuneIn. The stream is dropping every couple of minutes and eventually is fully stopped by the dedicated zone player due to too many recent errors.

    I got around this problem by simply playing this particular radio station through my VU+ box and send the signal into the Sonos environment by using a Connect.

    Apart from that, any connected online music service just works like a charm, may it be Deezer, Spotify, Tidal in hires or even the rather exotic ones like Batanga, Mixcloud and alike. I can even simultanously stream internet videos up to 1080i to my tv without any hiccups while playing online music content on several zones.

    Long story short: I very much doubt that Sonos has a general issue with DSL internet connections. You live in a rural area, the technical infrastructure at your location is most likely to blame. Enjoy the countryside.
    Translate