Skip to main content
Contributor I
December 26, 2019
Question

Sonos the way it used to be

  • December 26, 2019
  • 17 replies
  • 1141 views

Good morning

I’ver been a Sonos user for a long time, initially to allow my to play my CD collection from my hard drive. I now have Sonos in 8 rooms and use it with my Spotify and Apple Music services, but I would like to create a separate Sonos set up, to run in parallel with my existing installation, that would JUST play music from my hard drive. I would like to use a much earlier version of the desktop controller, perhaps on it’s own dedicated computer, and not have it nag me to upgrade every time I use it. Initially I would be happy to use this in one room only.  

Can anyone advise me on what would be involved in achieving this goal? 

TIA

Milt

    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.

    17 replies

    December 28, 2019

    I echo ​Kumar's comments entirely.  Playing my music library is fthe same easy process it has always been .

    How hard is it to tap 'Room' and select a room, then tap 'Browse', 'Music Library' and select some music?

    It is equally easy on the desktop.

    Lyricist II
    December 30, 2019

    Amazing how difficult Sonos has managed to make such a simple use model. 

    Apart from the lack of support for SMB2 and above, the limit on the number of tracks (which will only affect a few people) and the withdrawal of functionality from the desktop controller, is it really that much more difficult?

    Yes.  With my Bose bluetooth device I can connect it to my Android phone or iMac and play music using VLC or iTunes on it.  That does not seem possible (or at least easy) on Sonos.  Sonos requires creating a user account an accept their terms of service to use the device.  Bose does not (nor any other stereo company I have used).

    Using the Sonos Android app I was unable using “On this mobile device” to get the app to find the music on the phone.  I was unable to get the Music Library set up to the Samba NAS.

    Using the Sonos Mac app was non intuitive.  Even though the Samba NAS was mounted on the Mac, adding it as “Another folder or drive connected to my computer” and being able to browse to it, it failed because “You cannot select a folder on the network to be shared”.  Selecting Networked device shows examples such as \\MyOtherComputer\Shared\Music (the backslash being Windows syntax, not Mac/Unix) when what it wanted is //<ip>/directory .  With trial and error I was able to find the right syntax.  With that music on the Samba NAS can be played with the Sonos app (but not VLC or iTunes).

    If not for the Samba NAS and iMac (which is the wife/kids, all my boxes are Linux) the Sonos would not be connected.

    As a new customer, this has been an extremely frustrating experience and I am still undecided as to whether to return the Sonos.  As  a Linux engineer, I understand that Sonos is running Linux, that it plays music not by streaming but by playing the mp3 on the Samba NAS.  I don’t mind turning this into a science experiment to get it to work.  But I now understand the limitations.  Sonos (wifi) cannot be used like a bluetooth device to play all audio from a phone or computer.  I cannot use VLC or iTunes they way I can with bluetooth.  Most disturbing reading these forums is the willingness of Sonos to remove functionality in updates, causing previously working customer setups to no longer work.  “Thou shall not break customers” is a Commandment where I work in the tech industry.  Sonos does not seem to have that same commitment.

     

    Sjoop1985
    December 30, 2019

    Sonos (wifi) cannot be used like a bluetooth device to play all audio from a phone or computer.  I cannot use VLC or iTunes they way I can with bluetooth.

    This is is the most important "limitation" of the system and it leads to a lot of misconceptions and disappointments with people who haven't looked into what they are actually buying. I'm always extremely clear to people who ask me about Sonos, that they shouldn't expect it to function as a Bluetooth speaker in any way, I use the example of YouTube or PC audio to illustrate this. It's just not what the system is for. If you want to hold Sonos accountable for that, fine, I don't. Most Bluetooth speakers don't offer all the other functions that Sonos does. I know that Denon Heos and Bose Soundtouch do have Bluetooth, but does that then integrate seamlessly into the multiroom, like the line-in in the Sonos system does? Because only then I would find it a useful addition.

     Sonos requires creating a user account an accept their terms of service to use the device.  Bose does not (nor any other stereo company I have used).

    Bluesound, Denon Heos and Bose Soundtouch multiroom systems all require you to create an account. That is what you should be comparing Sonos to, not to "dumb" stereo systems.

    Most disturbing reading these forums is the willingness of Sonos to remove functionality in updates, causing previously working customer setups to no longer work.

    Compared to other tech products, Sonos supports their hardware for a very long time, and is very cautious about backwards compatibility. In some cases, there is no other way but to remove functionality. Incompatibility or end of life of mobile OS's is something Sonos has only very limited control over. I would remind you that Bose has recently discontinued an entire line of hardware, and the only way to remain supported is to purchase a completely new hardware setup.

    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
    pwt
    Virtuoso
    December 30, 2019

    Selecting Networked device shows examples such as \\MyOtherComputer\Shared\Music (the backslash being Windows syntax, not Mac/Unix) when what it wanted is //<ip>/directory .  With trial and error I was able to find the right syntax.

    Just to avoid confusing others, the advertised backslash syntax works perfectly for accessing Samba shares via Sonos (provided SMBv1 is supported by the NAS).

    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
    December 30, 2019

    There are many reasons someone may want to return Sonos, mostly for not having fully investigated its suitability for a desired use case/s, but that Sonos does not anymore do what it used to isn't a valid one. Which is what this thread started being about. Those other reasons have plenty of threads devoted to them.

    Yes, significant one time set up/set up tweaking functionality now needs a smart phone, but that still does not amount to “Sonos no longer doing what it used to for CDs ripped to a NAS” for those - at a guess 99 percent plus - of the user base that has one. And for that small minority too, for routine use that does not involve set up changes, a computer is still enough for all the necessary user interaction for music play, and for adding and indexing more music to the NAS.

    December 30, 2019

    Amazing how difficult Sonos has managed to make such a simple use model. 

    Apart from the lack of support for SMB2 and above, the limit on the number of tracks (which will only affect a few people) and the withdrawal of functionality from the desktop controller, is it really that much more difficult?

    Yes.  With my Bose bluetooth device I can connect it to my Android phone or iMac and play music using VLC or iTunes on it.  That does not seem possible (or at least easy) on Sonos.  Sonos requires creating a user account an accept their terms of service to use the device.  Bose does not (nor any other stereo company I have used).

    Using the Sonos Android app I was unable using “On this mobile device” to get the app to find the music on the phone.  I was unable to get the Music Library set up to the Samba NAS.

    Using the Sonos Mac app was non intuitive.  Even though the Samba NAS was mounted on the Mac, adding it as “Another folder or drive connected to my computer” and being able to browse to it, it failed because “You cannot select a folder on the network to be shared”.  Selecting Networked device shows examples such as \\MyOtherComputer\Shared\Music (the backslash being Windows syntax, not Mac/Unix) when what it wanted is //<ip>/directory .  With trial and error I was able to find the right syntax.  With that music on the Samba NAS can be played with the Sonos app (but not VLC or iTunes).

    If not for the Samba NAS and iMac (which is the wife/kids, all my boxes are Linux) the Sonos would not be connected.

    As a new customer, this has been an extremely frustrating experience and I am still undecided as to whether to return the Sonos.  As  a Linux engineer, I understand that Sonos is running Linux, that it plays music not by streaming but by playing the mp3 on the Samba NAS.  I don’t mind turning this into a science experiment to get it to work.  But I now understand the limitations.  Sonos (wifi) cannot be used like a bluetooth device to play all audio from a phone or computer.  I cannot use VLC or iTunes they way I can with bluetooth.  Most disturbing reading these forums is the willingness of Sonos to remove functionality in updates, causing previously working customer setups to no longer work.  “Thou shall not break customers” is a Commandment where I work in the tech industry.  Sonos does not seem to have that same commitment.

     

    Tried quoting, but it soon became a mess, I’m afraid...

    Sonos hasn’t supported Bluetooth until the Move, so I don’t understand why you thought that it would.

    AFAIA, the more complex systems (ie. not Bluetooth) do require an account/registration. I share your concerns, though, about the increasing number of settings that need an internet connection to work (e.g. max volume).

    Sounds like you have the syntax sorted out now, which is good….

    You mention the NAS and the iMac as being essential, but nowhere do Sonos list Linux as being supported - so I don’t understand why you thought that it would be.

    If Sonos doesn’t meet your needs, then perhaps you should return it and buy a Bluetooth enabled device, which sounds like it might meet your expectations.

    As regarding functionality removal - yes, I agree in some respects, but Sonos tend to take the approach of protecting their own legacy hardware first - i.e. keeping older kit working. Due to the limited space in these devices, and the constant call for ‘improvements’ just to stand still (e.g. voice) there are limits as to what they can do as far as support for older external devices - e.g. phones, tablets. They don’t even have the space to move to a later version of SMB. So Sonos tries not to break their own customers, but this has an impact on external devices. I’m not happy about this either, but IMHO it’s better than obsoleting older Sonos players. 

     

     

    Stanley_4
    Grand Maestro
    December 31, 2019

    Sonos is happy to use a music library hosted on Linux, mine is happily running from a Raspberry Pi. I find that a safer option than enabling SMB v1 on my “real” NAS device.

    There are Linux controllers available from folks, a search here should turn some up. I don’t have a lot of experience with them recently but when I was looking a couple worked well.

    I miss access to the internal data and am aggravated by the need to access via IP instead of name but neither is more than aggravating.