Well that's Xmas ruined....

Hi ​@ianm_42 

Thanks for your post!

Sorry to hear of this issue you are having with playing your Christmas playlists!

Your email has no system registered to it, and your profile information is not conclusive enough for me to determine which software version you are using. So, when you say “using the old Android app I have rolled back to” are you referring to S1, or are you using a S2 app from before May?

If the latter, please update to the latest app and check your Sonos system for updates afterwards. Your SMB share should be SMBv2/3 or it will not work. You have not mentioned what you Music Library is stored on other than the PC, so I can’t advise on how to do this.

If, however, you are using S1, then SMBv1 must be in use.

In either case I recommend (and in the case of S2, after updating) you get in touch with our technical support team who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports. The speakers will be generating log entries, which need to be looked at.

I hope this helps.

The Sonos is not registered to this account, but as the Sonos's are my wife's they are registered to her, all 4 of them, S2 ones I think.

We are using Android app, V16.1 to have sleep timers and access to our lists of radio stations, which went missing when app was updated in May.

It is the removal of SMBv1 the issue, my Popcorn Hour media server only does SMBv1 and has worked 100% fabulously with Sonos until May, since when ever we got the Sonos (2012 ?).

Unless you are going to restore SMBv1 support (or I get my a**e moving and implement a raspberry pi SMBv1 to v2 bridge or media player) we are stuck using Android phone and JBL Bluetooth speaker, which works wonderfully fine using SMBv1. Use Android Owlfiles to browse SMBv1 shares no issue, thank goodness someone supports legacy systems.…

The dropped support for SMBv1 is not a new issue though, ​@ianm_42  You posted some 6 months back on the same topic : 

Yeah, with 6 months lead time to realize this was coming and/or rectify the situation, one can hardly blame Sonos for “ruining” anything.  Just another case of manufactured drama.