Skip to main content

Sonos 1 System - 2x Sonos 1’s (2 gen), ZP100, Connect OS.S1, Play 3 & Play 5.

Sonos System - 2x Era 100’s.

My Play 3 & Play 5 lost power within 3 weeks of each other (Trying to find someone to repair them but having no luck.)

I decided to invest in two Era 100’s.  Unfortunately I mistakenly thought I could get all of the above to link together.  Although I have read on the forum that I could get the Sonos 1’s to integrate the with the Era’s via the Sonos app.

I successfully set up the Sonos app on my ipad/iphone and connected with my Era’s and my Apple Music, Napster etc. I then wanted to gain access to the music on my Windows PC and Synology server drives as I do with the Sonos 1 App.  However, I could not access the drives via my ipad/iphone and realised that I would need to do this via my PC by uploading the Sonos app.

Sonos App installed successfully but despite many attempts I cannot get my PC app to connect to the ERA speakers over the wifi. It says “Not Connected”.  I have however, connected via the web app but that is not how I want to use the system.  Has anybody got any ideas how to fix the issue?

Thanks in hope and anticipation 

Ok, there’s a couple of things. 

You have, I think, two systems. One running under S1, another running under S2.

There are no Sonos 1s. Sonos has made PLAY:1s, and Ones, but no 1s. 

Sonos has made no changes to access under S1, in fact, they can’t. 

In S2, Sonos has changed the way that their new app accesses audio from shared libraries on the local network. The previous S2 App supported SMBv1 and HTTP protocols for file sharing, but these have known vulnerabilities and are no longer used by Microsoft, Google, Apple, Amazon etc. and all has now shifted to using SMBv2 (or higher) file sharing.  You may need to upgrade your shares… see these links depending on how you share your library tracks…

For MacOS users, see this thread.

For Windows users, see this thread.

Sonos sent out notices both in the S2 app, and in email, about these changes. They also updated the FAQ to reflect the update. While they have stated that the local library system continues to be worked on, I do not expect them to resume use of HTTP or SMB v1 on S2, so if your computer uses them, I’d recommend re-adding your share, as is indicated in the controller, where it says ‘We’ve made security changes to supported libraries. You may need to re-add your library”.

If you’re having trouble finding this area in your controller, open the S2 controller, click on the gear icon at the upper right of the screen, then the word ‘Manage’ under it. Next, click on ‘Music Library’, and the page to enter/modify your local library will come up.

If you continue to have issues, I would recommend that you call Sonos Support to discuss it.


Thanks Bruce. You are correct they are Play 1’s .

I will have a look at the links you have provided.

My biggest issue is that I cannot get the SONOS app on the PC to connect to the Era 1’s which should not need any of the above.  Or am I missing something?


Really need to use the right names for your Sonos speakers or you’ll just confuse folks.

Play 1

One

Era-100

If you meant the Era-100s you might try resetting the Windows Controller (I don’t have it loaded to tell you the steps) and seeing if it shows you both of your Sonos systems.


Not seeing the devices is a completely separate issue from the devices not seeing the shared data, and one I didn’t address in my reply. 

Following ​@Stanley_4 ‘s suggestion is a good start. I don’t use either the web or the Windows controller myself, so I’m less familiar with their issues. But it still sounds like a ‘discovery connection’ problem, and certainly could be resolved by that restart. Or possibly a restart of your router. 

If you decide to call Sonos Support directly to discuss it, I’d suggest keeping to one issue, and not conflating them. Let the CS rep deal with the speaker’s connection to the controller, before confusing them with the speaker’s connection to the music library. Too many things to think about simultaneously. Let them fix issue 1 before moving on to issue 2. 


Most common reason for the Windows controller not finding anything is your WiFi (or Ethernet) network being marked as Public. Change it to Private.


Reply