10 ms·

Got a Sonos One for free when I bought a new phone once. So many issues with setting it up with WiFi. Gave up and used an ethernet cable. It's absolutely usel

by yuye 2y ago

Got a Sonos One for free when I bought a new phone once. So many issues with setting it up with WiFi. Gave up and used an ethernet cable. It's absolutely useless without a network connection, as it lacks bluetooth. You can't use it as a speaker for a Windows machine, only for MacOS (using AirPlay). I only use it for Spotify. Wouldn't ever buy any of their stuff.

ssl-3 2y ago
I've had a bit of Sonos gear: A Play:1, a Bridge, and a fancy jog-wheel remote that I forget the marketing name of. They deliberately bricked the jog-wheel remote around a decade ago. ("We aren't just not going to support these anymore; we're actually going to remote-brick every single one of them.") Upgrading the Play:1 to S2 broke the Bridge. (It wasn't bricked, but it was incompatible with their S2 and thus became useless to me; they didn't care.) Lately, the Play:1 has distortion in the woofer. Sounds like normal audio stuff; a torn surround, maybe. I don't know how to open it to even do a visual inspection. At 0/3, I've got a lot to complain about with Sonos. But the one thing I'm not complaining about is how it worked (when it worked): It is a networked loudspeaker, with network datagrams on one side and audible music on the other side. Once music is playing (started by an app or computer software or UPNP or whatever), it continues to play that music all on its own. It continues to play music if I take my phone and wander off, or take a call, or if I reboot my PC. It lets someone else control the music that is playing. Other than control, one or more Sonos speakers comprise a standalone system that is dependent only upon having the network behave. I have a very effective LAN in my house, just as I have also had in other living situations. That's an advantage and I want to use it. I definitely don't want things like this to be burdened with Bluetooth's problems.
- yuye 2y ago
  >It is a networked loudspeaker, with network datagrams on one side and audible music on the other side. Once music is playing (started by an app or computer software or UPNP or whatever), it continues to play that music all on its own. This has been my experience, too, as long as you don't touch it. Using the controls to skip a song has caused issues before, as well as unpausing after you've paused it for a while. That said, most of those problems have been solved by just using ethernet instead of WiFi. Even with my access point being 1~2m away, I've had connectivity issues. I wouldn't throw it away nor sell it, as it works fine when it does work.
  - ssl-3 2y ago
    I hear you. I generally always had good results with my regular wifi, but I had more-predictable results with a Bridge (which just produces a dedicated 801.11 "SonosNet" network), when that device still worked for me. When I occasionally installed Sonos professionally (a long time ago), we always installed a Bridge into a system or made sure that one Sonos endpoint/speaker was plugged into Ethernet by design. In doing so, this allowed the Sonos-widgets to form their own meshed wifi network that generally behaved just fine. (And no, none of that is quite ideal. These days I'm mostly divorced from Sonos. But I sometimes have issues with my various Google Home and Alexa devices that connect with wifi. To combat this, I also plug my old-school tiny-ass Chromecast Audio into an Ethernet adapter, as well as the CCwGTV on my main BFT. I do this just to be sure, because having consistent audio is very important to me, and it does work. But these devices don't make their own mesh like Sonos can do. [Well, maybe Alexa devices can if combined with an Eero router to steer the whole ship, but I don't want that at all.])

by yuye 2y ago

ssl-3 2y ago

I've had a bit of Sonos gear: A Play:1, a Bridge, and a fancy jog-wheel remote that I forget the marketing name of. They deliberately bricked the jog-wheel remote around a decade ago. ("We aren't just not going to support these anymore; we're actually going to remote-brick every single one of them.") Upgrading the Play:1 to S2 broke the Bridge. (It wasn't bricked, but it was incompatible with their S2 and thus became useless to me; they didn't care.) Lately, the Play:1 has distortion in the woofer. Sounds like normal audio stuff; a torn surround, maybe. I don't know how to open it to even do a visual inspection. At 0/3, I've got a lot to complain about with Sonos. But the one thing I'm not complaining about is how it worked (when it worked): It is a networked loudspeaker, with network datagrams on one side and audible music on the other side. Once music is playing (started by an app or computer software or UPNP or whatever), it continues to play that music all on its own. It continues to play music if I take my phone and wander off, or take a call, or if I reboot my PC. It lets someone else control the music that is playing. Other than control, one or more Sonos speakers comprise a standalone system that is dependent only upon having the network behave. I have a very effective LAN in my house, just as I have also had in other living situations. That's an advantage and I want to use it. I definitely don't want things like this to be burdened with Bluetooth's problems.

yuye 2y ago
>It is a networked loudspeaker, with network datagrams on one side and audible music on the other side. Once music is playing (started by an app or computer software or UPNP or whatever), it continues to play that music all on its own. This has been my experience, too, as long as you don't touch it. Using the controls to skip a song has caused issues before, as well as unpausing after you've paused it for a while. That said, most of those problems have been solved by just using ethernet instead of WiFi. Even with my access point being 1~2m away, I've had connectivity issues. I wouldn't throw it away nor sell it, as it works fine when it does work.
- ssl-3 2y ago
  I hear you. I generally always had good results with my regular wifi, but I had more-predictable results with a Bridge (which just produces a dedicated 801.11 "SonosNet" network), when that device still worked for me. When I occasionally installed Sonos professionally (a long time ago), we always installed a Bridge into a system or made sure that one Sonos endpoint/speaker was plugged into Ethernet by design. In doing so, this allowed the Sonos-widgets to form their own meshed wifi network that generally behaved just fine. (And no, none of that is quite ideal. These days I'm mostly divorced from Sonos. But I sometimes have issues with my various Google Home and Alexa devices that connect with wifi. To combat this, I also plug my old-school tiny-ass Chromecast Audio into an Ethernet adapter, as well as the CCwGTV on my main BFT. I do this just to be sure, because having consistent audio is very important to me, and it does work. But these devices don't make their own mesh like Sonos can do. [Well, maybe Alexa devices can if combined with an Eero router to steer the whole ship, but I don't want that at all.])