Answered

Mac Sonos S2 Controller app can't find existing network.

  • 9 August 2021
  • 5 replies
  • 594 views
T

I have an existing sonos network consisting of a Beam and Play:1 speaker. The Sonos S2 controller on my Android phone can connect to the system and play music on both speakers.   On my MacBook Pro 2012 (MacOs version 10.15.7) the Spotify app can see both speakers and play music on them. However, the Sonos Controller app (version 13.2) running on the MacBook can’t find the existing system.  I’ve rebooted router, macbook, and speakers and still nothing. I’ve uninstalled and reinstalled the app on the MacBook and that didn’t fix the issue.  The firewall on the macbook is off.  Beam is wired to the router, Play:1 is wifi connected. Phone and MacBook use the same Wifi network (5Ghz) to connect to router.

 

I’ve run out of ideas what else should I check?

icon

Best answer by controlav 12 August 2021, 14:52

View original
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

5 replies

controlav
Userlevel 7
Badge +23

Do you have any so-called “security” software installed? They often block local network access.

Also what router? Some can be challenged communicating between devices.

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
T

MacBook firewall is off. I have the free version of Sophos home (I’ve tried turning off all features, but that made no difference).   I don’t understand how the controller is not working on the Mac but Spotify also running on the mac has no issues connecting to the speakers which would seem to imply the issue is with the S2 controller app and not any security or network issue.

 

Router is an Archer VR1600v - my beam speacker is connected via ethernet, my play:1 speaker is wifi connected. The Router support both 5Ghz  and 2.4Ghz (I’ve connected the MacBook to both and it doesn’t make a difference).

 

Looking in the MacBook log files I can see that the MacBook is sending requests out to an endpoint that is registered with the router as  SonosZP when I try to get the Sonos S2 Controller to connect to the existing system.  These requests are failing with http result 500 - server error. Given the controller on my phone works, the only conclusion I have is the Mac controller app is sending malformed requests to the speakers causing the web server requests to fail.

 

Extract from log around the time that the Sonos App was trying to connect to the system. NOTE:  192.168.1.102 shows up as a SonosZP in my router network diagram:

 

2021/08/12 11:54:36:948  household(1): Beginning to send M-SEARCHES
2021/08/12 11:54:37:038  household(1): Ceasing to send M-SEARCHES: AssocZP:RINCON_949F3ED1A18501400 MS Notify: 1 DD fetch 0
2021/08/12 11:54:44:581  SCZoneGroupMgr(1): ZMState changed from WrongAPExistingHousehold to SystemNotFound
2021/08/12 11:55:06:947  legacy_join_household_wizard(1): State timed out, going to an error page
2021/08/12 11:55:06:948  Wizard(1): Wizard transitioning to State: legacy_join_existing.timeout ID: 7 in Wizard: SCLegacyJoinExistingWizard
2021/08/12 11:55:51:076  Monitored network adapter state did change from SONetworkStateConnected to SONetworkStateNotConnected with WWAN:NO
2021/08/12 11:55:51:110  Global household state changed from SOHouseholdStateConnectedNoZones:UnconnectedHousehold to SOHouseholdStateConnectedNoZones:None
2021/08/12 11:55:51:115  Suspending SCLib networking
2021/08/12 11:55:51:169  household(1): network changed, re-subscribing to UPnP services
2021/08/12 11:55:51:171  household(1): previous network - Rover1:192.168.1.109:
2021/08/12 11:55:51:172  household(1): current network - Rover1_5GHz:0.0.0.0:
2021/08/12 11:55:51:175  household(1): Beginning to send M-SEARCHES
2021/08/12 11:55:51:395  upnp(1): Failed to subscribe http://192.168.1.102:1400/SystemProperties/Event; Logical SID: 4; HTTP Result: 500; SR: 80000007
2021/08/12 11:55:51:442  upnp(1): Failed to subscribe http://192.168.1.102:1400/AlarmClock/Event; Logical SID: 3; HTTP Result: 500; SR: 80000007
2021/08/12 11:55:51:451  upnp(1): Failed to subscribe http://192.168.1.102:1400/MusicServices/Event; Logical SID: 2; HTTP Result: 500; SR: 80000007
2021/08/12 11:55:51:466  upnp(1): Failed to subscribe http://192.168.1.102:1400/ZoneGroupTopology/Event; Logical SID: 1; HTTP Result: 500; SR: 80000007
2021/08/12 11:55:51:472  upnp(1): Failed to subscribe http://192.168.1.102:1400/MediaServer/ContentDirectory/Event; Logical SID: 0; HTTP Result: 500; SR: 80000007
2021/08/12 11:55:56:044  Monitored network adapter state did change from SONetworkStateNotConnected to SONetworkStateConnected with WWAN:NO
2021/08/12 11:55:56:046  Resuming SCLib networking
2021/08/12 11:55:56:048  resumeNetworking()(0): IPAddress: 192.168.1.109
2021/08/12 11:55:56:055  household(1): network changed, re-subscribing to UPnP services
2021/08/12 11:55:56:058  household(1): previous network - Rover1_5GHz:0.0.0.0:
2021/08/12 11:55:56:061  household(1): current network - Rover1_5GHz:192.168.1.109:
2021/08/12 11:55:56:062  household(1): Ceasing to send M-SEARCHES: AssocZP:RINCON_949F3ED1A18501400 MS Notify: 0 DD fetch 0
2021/08/12 11:55:56:064  household(1): Beginning to send M-SEARCHES
2021/08/12 11:55:56:218  household(1): Ceasing to send M-SEARCHES: AssocZP:RINCON_949F3ED1A18501400 MS Notify: 1 DD fetch 0
2021/08/12 11:55:56:221  Global household state changed from SOHouseholdStateConnectedNoZones:None to SOHouseholdStateConnectedNoZones:NoDevices
2021/08/12 11:55:57:154  reporting(1): reporting xml configuration update skipping update due to older rev
 

 

controlav
Userlevel 7
Badge +23

Failed to Subscribe means something is blocking speaker->Mac communication, likely Sophos. Get rid of it. This is classic over-zealous firewall behavior. Sonos will not work with this blockage in place.

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
T

Gone (even though it had been there for years and the Sonos App had previously worked with it).  Sonos App still can’t connect, but at least the Spotify App still can.  My basic question is why is it that the Sonos app can connect to the speakers with no issue, yet the Sonos app running on the same machine can’t?

 

Update: 2nd reboot after removing Sophos seems to have fixed it.

 

K

I had same sort of issue that started a few months back.  Muiliple Sonos devices that I can still see from my Mac as being on the same network, but the Sonos app on the Mac couldn’t find them.  Ironically, Mac could use Air Play to connect and play through the system.  2nd Mac had same pattern.  3rd Mac was still able to have App find system.  I went through typical checks of firewalls, router reboots, etc.  I spent 1 hour in chat with Sonos help to no avail.  

More recently, download speeds were a little slower than usual: 60-50 mbs vs 100 mbs; not enough to notice without a test.  System profiler reported out a lot of new networks from neighbors, several of which were using the same wifi channels.  I changed my router to unused channels and now Sonos App can find the system again and speeds are back up.  

Terms & ConditionsCookie settings