Contributor I

Answered

This disastrous new sonos update is appaling

Forum|Forum|1 year ago
January 1, 2025
17 replies
540 views

Why can I not access / play or add my own audio files in the music library settings ? error code 913

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.

Best answer by Ken_Griffiths

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).

Show previous replies

Ken_Griffiths

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.

R

Robert of S

Lyricist II

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.

jgatie

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.

Ken_Griffiths

@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.

K

KurgerBurger

Contributor I

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.

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.

jgatie

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.

Stanley_4

Grand Maestro

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.

Sign up

Login to the community