Further sidelining of NAS Music Library in new Sonos App??

I think this would be a problem for S1 owners only, because S1 does not allow for SMBv2 to be used. S2 useres should not be affected by this as S2 does SMBv2.

That's such a confusing message.  It mentions specifically the removal of support for SMB1 on S2 products.

What , specifically, is being removed in the coming months for S2 products?

I agree the wording is confusing. On a first read it implies the whole music library feature is going to be removed. In light of the posting above a second read could be only those protocols are going to be removed. A little too vague. Should have been more specific. I was about to have a heart attack at the thought music libraries might be removed. The posted pop up above is exactly what I saw. I was going to screenshot it if it came up again but no need now. 

S2 still supports smbv1 so likely this will mean you must have a nas that supports smbv2. IIRC there was at least one smbv2 Sonos bug that affected indexing with some devices (needed to switch to smbv1 to index), hopefully this is fixed. 

To me it is quite clear that http and SMBv1 support are going to be removed form S2 because of safety concerns. SMBv2 is not mentioned, so no changes there. How is this unclear?

I saw a pop up, too, and didn’t get a screencap. But my takeaway--which may or may not be accurate--was that Sonos was discontinuing system access to a library on a computer because of security concerns. Instead, only NAS libraries were going to be supported. Did I dream this?

I emailed the CEO of Sonos, Patrick Spence.  Below is what I wrote.

Dear Patrick,

I wish to protest at the recent announcement by Sonos to end support for SMBv1 and (HTTP) which appeared in the Sonos app this weekend.  (See screenshot at end of email.)

I have two NAS devices, both of which are so old, they only support SMBv1.  One device holds a digitised copy of my music collection (for use with my Sonos system), the other holding files, family videos and photographs etc.

Although I agree that both SMBv1 and HTTP protocols are less secure than their successor technologies, the decision to use them rests with the customer and not with Sonos.  The use of SMBv1 poses no risk to Sonos, only to me, and that’s my decision.  Sonos is not the judge, jury, and executioner of how I choose to access my own music via my Sonos system in my own home.

I do not use music streaming services, so any change that renders SMBv1 unavailable to me effectively renders my whole Sonos system obsolete.  By all means warn the user that SMBv1 and HTTP are dated, less secure,  and “may” pose a security risk, but do not prevent their use. 

As a recently retired, 68 year old, I don’t have the money to simply purchase something for the sake of it, especially when the NAS devices in question are still perfectly serviceable.  Unless Sonos would like to reimburse me for the 10 Sonos devices I currently use in my home, or buy me a new NAS device so I may continue to enjoy my music, I suggest you rethink an ill-conceived draconian policy that will not win you any support, and alienate some of your existing customer base.

@nsd3 excellent and well made points, but I doubt it will have much effect, seeing that you are a vanishingly small part of the user base.

I still do not know if this will affect me, using S1 as I do for listening to my music in my NAS. If I stop taking anymore updates for S1, I don’t suppose it can, but what if I do let in these updates to S1 in future?

@Corry P - any reaction to the questions above?

The reason it's not clear is due to points raised above and you yourself saying this will only be a problem for S1 users when these users are not mentioned in the message in the App.  You also mentioned that S2 uses SMBv2 so should not be affected which is obviously not correct otherwise there would be no need for the App’s popup. S2 still supports SMBv1 that some users rely on.

Been playing today with my large (35k tracks) local library and tried to change to SMBv2 on my ASUS router and got the usual failure to index messages so this is not fixed. Removing SMBv1 will render my system useless to me unless this can be resolved. Is this just a ASUS issue and if so does anyone have any suggestions?