Have you searched for error code 913 to discover what it means? 

https://support.sonos.com/en-us/article/error-913-when-adding-a-music-library-share
 

It’s usually the library folder sharing protocol is not correct. If using HTTP or SMBv1 shares, you need to switch the source device to use SMBv2 (or higher).

If you search the community threads here, there’s information on how to do this for Windows, MacOS and various NAS boxes (the latter of which have settings that vary by make/model).

Hi,

Thanks for your help, I did look into what error code 913 means and it`s way over my head, I cannot find a button on the app that mentions HTTP or SMBv1 or anything related ? 

Why are the people at Sonos so pig headed this isn`t rocket science I just want to play my music on my system what`s so differcult !

Edwin

Wow. You seem to be very reluctant to impart information (if you’re asking for help rather than just venting).

You originally managed to follow steps in order to set up your library in the first place, so it wasn’t too far over your head last time. “To fix this error, follow the steps below to add your music folder…” Did you try to follow the steps?

No, it’s certainly not rocket science - unrelated to the Sonos App itself, you just have to setup the library folder share. Error 913 usually means you’re well on your way, but using the wrong sharing protocol. As mentioned, you likely need to ensure your PC/Mac/NAS is using SMBv2, or higher (by default). 

How did you create your library folder share in the first place? (before you even added it to your Sonos system?) .. I assume it’s a read-only folder share with an assigned device user account-name and password added to the share. The folders and files below inheriting the shared folder properties… all of which of course is nothing at all to do with Sonos, as numerous Apps can go onto securely access that same share over the local network from phones, tablets, computers, TV’s etc. 

The Sonos bit of then adding the library is much easier, you just add the path to the share and user credentials via the Sonos App.. and let it scan/index the library. It’s probably the easiest part of the whole process. If it’s the wrong type of share though, then that’s when you usually get the 913 error.

Cheese onion is not just venting even if s/he has every right to do so. I have used a Cocktail Audio X10 for many years with my Sonos speakers perfectly well until last Spring when Sonos decided to disable access to it. Despite numerous emails to them they have still not sorted out the problem. You give them all the information they want, you hear nothing from them and then out of the blue they send an email saying if you do not reply within 24 hours we will close your case. It is the most appalling customer service. It is no good saying that NAS devices must support SMB v2/3, my setup worked fine until SONOS disabled it. My music server manual has no information on what file sharing modes are used and is too old to find out from the company. Sonos caused the problem and Sonos should sort it out. I can connect my Windows 10/11 laptops with my X10 without a problem, the only problem is Sonos. I have heard of a number of people getting so fed up with Sonos that they have sold their Sonos speakers! I also have no interest in streaming commercial services, all I want is to play the music on my X10. I have even tried downgrading my speakers to work with the Sonos 1 app to see if that works but despite following the instructions to the letter all I get when I start the Sonos 1 app is “You need to downgrade your speaker first”.

​@Robert of S,

This link infers the Cocktail Audio X10 uses SMBv1, as the protocol appears to needs enabling in Windows in this link…

https://www.tenforums.com/network-sharing/101935-my-media-players-cant-access-shared-folder-pc.html

I understand it was way back in 2019 that Microsoft were warning to not use the SMB v1 protocol due to its security vulnerabilities. It’s why Microsoft, Apple, Google & Amazon etc. are not supporting it too. Sonos have chosen not to incorporate it in their latest App. Hence SMB v2 or higher needs to be used, if only for security purposes.

Some links about the SMB v1 vulnerabilities:

• https://appuals.com/what-is-smb-1/
• https://www.cisecurity.org/insights/blog/commonly-exploited-protocols-server-message-block-smb
• https://social.cyware.com/news/what-is-smb-vulnerability-and-how-it-was-exploited-to-launch-the-wannacry-ransomware-attack-c5a97c48

Personally speaking it is the sensible option to not include the vulnerability in their all new Sonos App.

I’m also not sure if it’s still the case, but I seem to think you may need an S1 only product to create an S1 System, but others have claimed they’ve managed to create an S1 Household with a hybrid device.

I do not use my X10 with Windows, I have always connected it direct to my Sonos speakers using the app. I also do not connect to the internet with it so there are no security issues. The only connection to the internet is when Sonos want to change the software in the speakers and alter the app. As for using the S1 app I have spent many unhappy hours trying to downgrade my speakers following the instructions on the Sonos website but the instructions do NOT work. My speakers are two Play 1’s and a Play 3. I also have a soundbar but have kept this switched off when using the X10 with the other speakers. The simple solution would have been for Sonos to make available a “downgrade” upgrade for those who wish it taking the S1 app and older speakers back to before the May 2024 update ( It was certainly not an upgrade).

So perhaps just use your Windows PC with Sonos instead and share the library from that device - that at least is one way forward for you,

An SMB v2 (or higher) shared library definitely works okay with the new Sonos App, as shown in the attached recording from my own Home Sonos setup. So it’s worth going that route with a Windows PC.

Ken, while I know you are trying to be helpful that is not a route I should have to follow. Why should I and many thousands of others have to pander to Sonos and their unreasonable behaviour. They should have made last May’s changes optional so that those who were happy to make the changes could do so but those who would be adversly affected could opt out. I have never had to have my laptop switched on to use my X10 so why should I have to now? To copy my X10 library would also involve me buying a much larger ssd drive for my laptop, go through all the aggravation of migrating my operating system and files and programs to the new drive, and all because Sonos decided to affect many thosands of us adversely. Having adversely affected so many customers instead of doing something about solving the problem  they have effectively washed their hands of the matter to let the customers suffer the problems of their (Sonos) making.

You need to pose that question to the small but vocal contingent calling for SMB v1 sharing to be dropped.  They are the ones who mounted a campaign to denounce Sonos’ use of SMBv1 here and in the press, even though there isn’t one documented case of any hacker breaching a Sonos system or library due the the use of SMB v1 (or HTTP) sharing. 

​@Robert of S 

I remember a similar debate when analog TV broadcasts were switched off in the UK and we reverted to plugging in Digital TV boxes - there’s almost always a workaround and that’s why I suggested that the PC could perhaps host the local library and to just leave that powered on instead of the X10 - I wouldn’t change the hard-drive,  maybe plug-in a USB drive instead, but if you have a Sonos Home Theatre, or an analog line-in, to Sonos, then perhaps see my comments later in this post.

Other options are to use the ‘free’ iBroadcast service on Sonos, or even use Plex. I’m sure that other users here would be able to suggest some other alternatives too.

Unfortunately for some of us though the tech. around us ALL does not usually standstill for long and our options are really to move with the times, that’s if you plan to stay aboard, what is, a moving train. Some may choose to get off at a station, but that’s entirely a matter for yourself.

Just to say my Son waited after the May 7th update for quite some weeks, before deciding to upgrade his system to use the new Sonos App and he went a slightly different route with his locally held music. He got himself a Sonos Arc (not Arc Ultra) for use with his main ‘smart’ TV and he put his local library onto a USB stick (connected to the TV) and now uses the built-in TV media player to play his music to Sonos - so that’s how he resolved his local library issue, although I’m sure he will upgrade and switch to using a NAS at some point. Another option of course is to play the music on Sonos using either Bluetooth or line-in, but these things of course each depend on what devices (if any) you may have in your Sonos system already that can utilise these type of connections and be able to play your locally held tracks.

My NAS is old and only supports SMB1. Sonos used to support SMB1, they should provide backwards support. Default to SMB2 but allow an override for the user to go back.  Simply turning it off completely was heavy-handed.

You are preaching to the choir.  However, once again ask the vocal security freaks why they insisted there would be no solution accepted which did not completely eliminate support for SMB v1. 

Not just support for it they want any code that could support it gone.

Samba folks took the middle ground here so you can have it or not when building your server’s code.

https://gitlab.com/samba-team/samba/-/merge_requests/2421

This patchset adds the options --with-smb1-server and --without-smb1-server. Setting --without-smb1-server will, for example, disable smb1 in the smbd server.