Hi @press250 , thanks for the reply, but unfortunately it doesn’t help.  My local music is on a Synology NAS running DSM 7.  I also have a Windows Desktop and Laptop with the latest Sonos Windows app on there.  When I remove the Sonos app from my mobile device, shut it down and then reboot/reinstall it, as well as connecting to the speakers in my system, I would expect it to pick up the same local library configuration as in the PC & Laptop.  It doesn’t.  If I manually add the music library into my Android app with the same settings as the PC & Laptop, whenever I tap any of the music library options (Artists, Albums, Folders…) the mobile app always shows the message “Something went wrong”.  The Android mobile app (running on Android 14) does not work with my NAS (min SMB 2). 

We set up our music library as an SMB2 share on a Windows computer using the Windows app. While the latest Android app now includes some support for a music library, it's not detecting the existing one - it only shows the "+ Add Shared Folder" button. We're signed in to our Sonos account in the Android app.

Any idea why the existing (and working) music library share isn't appearing in the app? We're reluctant to add it again in the Android app, for fear that it will mess things up for the existing library, or create a duplicate. 

Our issue seems to be somewhat similar to the one marner reported in the previous post in this thread.

If the library is showing up in the old app and not in the new, it is probably still being shared via HTTP, which is no longer supported due to security reasons.  Delete the old library using the PC app, then follow these directions to add an SMB v2/v3 share to the system:

https://support.sonos.com/en-us/article/add-your-music-library-to-sonos

I would also double check the link to setting up a share in Windows, there may have been something you missed.

Thanks. As we wrote above, the existing music library share is an SMB2 share, configured as described in the article, and it's working fine in the Windows app.

It woud appear that Sonos does not want local file playback supported. Is that true SONOS? Unbelievable that such a basic but major problem is still not resolved. I have wasted half a day on this,thank goodness for ROON and all the others. Thankfully I only have one sonos speaker and that’s going.

Sorry to say, but if it is working fine in the Windows app and not in the mobile app, it’s not using SMB v2 sharing.  It’s probably using HTTP, which is the default for the Windows app.  Delete the current share using the Windows app, and follow the directions here (make sure you use the link for installing a share on Windows):

https://support.sonos.com/en-us/article/add-your-music-library-to-sonos

Aa we wrote before, we followed the directions, and our music library is definitely an SMB2 share. We can connect to it from both VLC for Android and the Network Storage feature in the My Files app using SMB.

The fact that the library isn't recognised by the latest Sonos app update means that the app is still faulty, just like marner described in their post above 5 days ago.

Hi @The Krollmanns, quite a conundrum! A few things you may not have tried …

• Have you performed a system update to the latest firmware? I would check that from the Windows desktop client, it is the most reliable vehicle. The v16.3 firmware cleaned up local music libraries for quite a few users.
• Adding your music library in the Android app strikes me as low risk: if you do run into a snafu, you could repair it in the Windows desktop app.

Just because you can connect via SMB does not mean you are using SMB v2 or v3.  You need to get your drive using SMB v2 or v3 only.  If it is still running SMB v1, it may not work. 

Yes, the share is SMB2/SMB3. SMBv1 is disabled on our Windows computers, as it has been the default for a long time now. Get-SmbServerConfiguration returns False for the EnableSMB1Protocol.

All our six Sonos products are running firmware version 16.3.1 (build 80155240).

We were thinking about what you are suggesting - trying to add the music library in the Android app, until we read the reply by @marner at the top of page 2 in this thread that it didn’t work for them and threw the infamous “something went wrong” error.

The Android app (80.05.07 from 26-Jul 2024) does recognise the queue that we populated with one of our playlists from the Windows app, and it shows correct metadata (but no album art) for the songs, so it is at least partially aware of the content. Adding an already existing configuration item a second time doesn’t seem logical in this scenario, and as marner’s experience shows, it’s not working anyway, so we have to assume that the app is still faulty or incomplete with regards to music library support.

Suffice it to say, our trust in the Android app is virtually non-existent by now, so we will continue to play it safe and wait for further updates to filter through, particularly as we don’t seem to be alone with this issue. We are unwilling to risk losing what little functionality we still have at the moment by playing around with our system, to try and make features work again that are apparently still not supported fully or correctly.

UPDATE,

Following an upgrade a couple of weeks back my Music Library “appeared” on the home page again.  I duly went into the “Manage” option and was able to add the path to the share.  ALthough at that time the “Detect Music Library” return an error.  I suspect this was becasue the library was bening scanned and indexed (slow time) becasue a day or so later “Music Library” magicall appeared on the Home page, and joy of joys, it showed all my music (albeit with the VERY) annoying problem of showing each track of a compilation album as an album in it’s own right !  And I was able to play selected music

However some days later I had a message that my speakers needed an update and I foolishly complied thinking it would be an improvement.  The result is that this upgrade removed Music Library from the Hom page of my iPhone and iPad apps again.  The NAS share still shows as added Music Library path although “Detect Music Library” returns the not found error. This really is exasperating beyond words.

Is it too much to expect that a mobile app, released to the public, should either work, or allow downdrading to the previous working version?   PLEASE Sonos, follow the pigin Latin and “Extractum digitalis” and provide us with a workable app or useable workaround !

Before this debacle I was on the point of comtting to a new speaker with “Line in” facility so that I could play some of my vinyls but at the moment that is RIGHT ot of the window 

I have the same issue one Album for each track of a compilation album also I can only re index using the Windows Controller - the button on the Android App appears to do nothing. Scrolling through a large library of albums is a nightmare as the is no alphabetical scroll bar to the right. No add to queue. No moving tracks up and down the queue. No "add to Sonos Playlist. No Album artwork.

Really hopeless at the moment.

I am testing the new App using a single Sonos Roam and a Raspberry pi with Openmediavault set for SMBv2.

The rest of my system I was able to downgrade to S1 - working perfectly and totally reliable.

And that really does take the biscuit doesn’t it

@marner @jgatie @press250 @essenby The latest Android app update (80.06.04 from 1-Aug 2024) is now showing the UNC path to our existing music library, which is what we were hoping for (that it would reappear). We did NOT try to add it in the earlier version of the app. This proves that there was never anything wrong with our library, no HTTP or wrong SMB version or whatever theories were offered - the earlier app versions just didn’t pick up the existing library, which is what we suspected all along, given the slow incremental process we’ve seen across these successive app updates.

@marner @essenby We’d be keen to hear if you are able to see your NAS shares again, too, once your devices have installed this app version.

We haven’t played around with any music library settings or content yet, but we’ll give this a go over the next few days . Given what others have already posted (one album per track, usability issues etc.) we don’t expect anything pleasant yet… but we’ve regained a glimmer of hope.

@The Krollmanns Thanks for reaching out here.  I’ve also seen the Music Library picks up the path to the library, so a small step in the right direction.  However, when trying to access the music library options to play music, all I still see is “Something went wrong”.  Like you say, “a glimmer of hope”.

BTW, the Sonos release notes page shows version 80.06.04 was released on 6 August 2024.  Something not quite right there.  The version I have installed is also from August 1.

Might just be the build date of the latest app version, not the release date ... which could suggest that this version had been tested for at least a few days before it was let loose on us.

Not very encouraging what you've experienced so far - yet another "something went wrong". Ah well. Patience.

If you don’t have auto re-indexing enabled I wouldn’t press the re-index button, firmware 16.3/16.3.1 makes a right mess of the index anywhere where the artist and album artist fields are different (and album artist isn’t empty...) This is usually seen most on compilations, but will also show up when you have guest artists on songs (correctly) tagged under artist too. 

IF you don’t need to re-index on 16.3 I would hold off until we get a fix, or life gets even more painful. Lack of queue editing really doesn’t help here either. 

Thanks for that, Ian. We indeed have many songs where the Artist and AlbumArtist tags differ, so we'll refrain from changing any library content or re-indexing it for now.

Makes you wonder who keeps making all these rookie coding mistakes, and what the frick went wrong at Sonos with these new apps. Feels like someone was given free reign who didn't know what they were doing.

We'll take that back. This morning our music library is gone again, like in earlier app versions. It appears to have been a fluke that it was shown yesterday.

@The Krollmanns Absolutely no offence guys, I know how frustrating this is, but you’d cry if it wasn’t so ridiculously funny.  This morning the Sonos app on my phone took ages to connect to my system.  Never experienced that before. 

@The Krollmanns 

Unfortunately my app is on an iPhone and iPad and currently the latest version is 8.06.03.  In that version the library path shows as //{nas-drve}/{path} and despite it being accessible from my desktop Windows app and the web based controller Music Library is conspicuously absent from the Home screen of the apps

@The Krollmanns If your music library (not settings) does appear again, can you inform us if you can use it please?  i.e. Select and play something from Artists, Albums, Folders, etc.?

@marner Will do.

In the brief time mine was visible for me I can confirm that I was able to select and play individual tracks,  However, I didn’t try to use it hat much becasue of the absolute mess it had made with the indexing (compilations etc)