Do you mean your firewall on your Mac or router? and where is SONOS approved in your firewall.

Sorry- On the MAC.  

I have reset controller, and all other devices with no luck.

Try going into System Settings, Privacy & Security, Local Network and see if SONOS has permission.

Thanks Peter.  It is listed there as well!  My Iphone is working with SONOS by the way.

Peter- You must have Great Karma!  I turned off the local network and reconnected and now it is ok!  You are the MAN!  Thank you!

Hehe no problem, glad it worked 
Please mark my reply as “answered” 

I hate to sound stupid but I have never done that in here- where do I do that?  LOL

Peter was able to resolve my issue.

Issue Closed 12/14/2024.

Thanks again Peter.  Everything seems to be back to normal!  

I too have this issue after updating to Sequoia 15.2. 

Same message whether Firewall is on or off. (sonos is already enabled)

Tried local network but Sonos not there (the Sonos 1 controller is, but not Sonos 2) How do I add an application to the local network?

Thanks so much

 Peter_254 you absolute chuffing legend! I’ve been losing my mind with this issue! Thank you. :-) 

I am still having ongoing Firewall issues. I have repeatedly checked the Firewall settings and SONOS is is set to “Allow all incoming connections”. I have reset the controller, removed and reinstalled the controller for the MacBook Air, reset the router. SONOS controllers on all handheld devices work perfectly. Only the MacBook Air controller has issues.

If I remember correctly, and I’m not on my Mac right now, the updater is a separate application than ‘Sonos’. Have you opened your firewall to both?

Yes, the FW is updated to allow all incoming connections on both, but still not working. Thank you for the suggestion.

Odd. I suspect you may need to call Sonos Support directly to discuss it.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

There is apparently a bug in the system at the moment.
I have had the SONOS App on my Mac for a very long time and it has worked perfectly.
Now when I opened it it came up with a firewall error.

Tried resetting the App but that didn't work.
Then I deleted the App, restarted my Mac and installed Sonos again. When I opened the SONOS App it asked for permission, I said yes.
Chose connect to existing system and now it works again.

“Local network” permission is a new feature in MacOS, and it is implemented as poorly as it was on iOS, Its state is often wrong, it often forgets the state after an update, and Sonos don’t bother to detect this specific condition to give a decent error message.

SONOS app on my Mac has stopped working too.  I have completely disabled the firewall and I still get “NOT CONNECTED” error.  

YES I’ve tried all of these:

• re-started router and all SONOS devices
• deleted and re-installed SONOS app
• deleted, power cycled, re-installed SONOS app
• deleted, disabled firewall, re-installed SONOS app
• deleted, disabled firewall, re-installed, re-enabled firewall 

And YES, SONOS is set to allow incoming connections on the firewall settings.

Working fine but laggy on my iPhone (as is normal these days).  It literally just took 5 seconds to skip one track forwards.

I’m curious, what did Sonos Support say, when you called them directly to discuss it?

For what it’s worth, ‘laggy’ leads me to believe you have either a wifi interference issue, or possibly, albeit less likely, a duplicate IP address issue. That would be something normally cleared up by rebooting the router while the Sonos are powered down, but not if doing them at separate times. But that wouldn’t explain your Mac issues, unless your Mac is on a different subnet, like sometimes some ‘mesh’ devices create. Which is why I’m interested in what Sonos said. 

Fixed.  Go to Mac Settings > Privacy & Security > Local Network, switch off Sonos, wait a minute and switch back on.  Hey presto everything is visible again. 

Ah. As ​@controlav discussed 9 hours ago, in this very thread. 

The permission was on.

I had to switch it off, wait and re-enable.