Have you called Sonos Support directly to discuss it? It may be an issue with your caps-lock, some systems are sensitive to that as being a differentiator. Or it might be that your previous access was through HTTP or SMB v1, in which case you should reset up your share, using the new instructions in the FAQ. Certainly if it is the latter, no amount of waiting will resolve that, which is why calling in might be your best bet. The Sonos folks would likely be able to assist you in resetting things up properly. 

Thank you. I was laboring under the belief from what I read there was a local library fix forthcoming. 
 

I’ll try this.

B

22nd July is the date now being suggested. 

Local library fixes are still coming, for some issues. My understanding is that these will not change the removal of http and SMB v1 from access paths to your local files. 

What does that mean?

SMBv1 is annoyed form of making contact between your NAS and Sonos. Since it is deemed unsafe Sonos removed this - coinciding with the new app, thereby confusing a lot of people about why they could not see their library anymore. They wrongly blame the new app. Newer NAS devices can be made to use safer SMBv2 or SMBv3, which do work with Sonos.

If you cannot see your library that is housed on a computer, Sonos also removed http access at the time they removed SMBv1, also for safety concerns. Thus confusing even more users.

The only ways to ad a library on the new app are explained here: https://support.sonos.com/en/article/add-your-music-library-to-sonos