I run a studio for music lovers with numerous Roon Ready devices. This is the second time that I have lost reception to my devices after a requested update in my app. The first time, I don’t know what happened to make it work again. Today, my business is open and I can’t connect anymore. Restarted Roon Core, cell phone. Restarted, restarted all devices. It does not work. These devices no longer appear in the settings either. It is a disaster.
Go to Settings > Privacy & Security > Local Networks, toggle Roon on & off, then reboot. It’s a pain and I’ve had to do it a couple of times now.
1 Like
I have to reboot my MacBook Pro each time Roon updates. Otherwise it will only see the directly connected DAC.
Ever since Sequoia has been released, each Roon update is a mess.
What’s happening?
· Other
Describe the issue
Audio zones not found
Describe your network setup
Netgear Nighthawk Modem (CM2050V), Asus AX6600 Router.
Been there, done that.
The team has a ticket in to investigate the underlying interaction between Sequoia’s network security and RoonServer/RAATServer. You can expect a more permanent resolution soon and I will merge your thread into the appropriate tracking thread.
In Privacy & Security, instead of toggling full disk access, try toggling to Local Network → RoonServer and toggling that instead. Sequoia has more strict network permissions than previous MacOS releases.
Toggling RoonServer’s local network access on/off remains the most reliable workaround. Other users have verified that RAATServer and RoonServer have access permitted in the MacOS Firewall (don’t disable the firewall entirely).
Development will provide updates as available and we’ll channel them immediately to the tracking thread. We appreciate your patience.
2 Likes
Hi @Robert_Stanley1,
Diagnostics show you might be running MacOS Sequoia 15.x on your RoonServer machine.
If that’s the case, make sure you’ve toggled on Local Network access for RoonServer in System Settings → Privacy & Security → Local Network.
You might need to re-toggle this option on/off if you find devices disappearing from your Settings → Audio screen in Roon. The team is investigating this issue. It’s related to more secure operating system network security that Apple introduced with Sequoia:
2 Likes
Thanks Connor. After trying to reboot modem/routers multiple times, I deleted the Roon app from my server and re-installed it. Everything came up as per usual after the re-install. Also followed up on your recommendation and the settings for local area network access were correct. Appreciate your time.
This might well be fixed in macOS 15.2. Had the issue where I needed to toggle local networks for Roon after every reboot. After installing 15.2 it seems to reset the ‘local network permissions’ DB as it asked to verify apps again including Roon.
After a reboot it still retained the correct permissions and Roon now worked without any toggling.
Fingers crossed it’s gone.
Graham, it doesn’t work for me after installing 15.2. Same ol’ thing, have to toggle “local network” to see endpoints. I wonder if you have some other setting that is allowing it to work for you. What happens if you “shut down” the mac and endpoint rather than a simple “reboot”.
Shame, though a reboot of the Mac would be the same as a shutdown and a start.
Even Intel Macs do not us a lot of power, do not turn the machine off at night
On a Mac, you have to login to make Roon server work so after a restart you must login once. I leave my Mac Mini on and logged in all the time. I set it so the screen goes dark after 5 minutes and you need a password to gain access
I don’t know if anyone else is having this issue, but whenever I add a new album to a folder, the rescan involves all the folders, not just one I added to. I don’t ever has this issue on the windows version, using Roon as a core. I am running the latest version of Sequoia on a Mac M2 studio.
1 Like
Me too. I am cautiously optimistic. My Roon Remote is running on a MacMini upgraded to MacOS 15.2 (24C101). Roon runs on Intel NUC.
NO IT IS STILL BROKEN
TOGGLE ON/OFF LOCAL NETWORK is the workaround.
I sent a message to support and then realize this thread. I had Sonoma until yesterday. I always wait to some updates before do a big one to wait Apple to do bug fixes or whatever. Since I updated to Sequoia the Wiim Ultra is not being detected anymore until I plug the ethernet again or reenable the permissions for Roon many times 
What’s happening?
· Other
How can we help?
· None of the above
Other options
· Other
Describe the issue
Recently migrated my Roon Core from a Macbook Pro to a Mac Mini M4 and restored the database. Everything worked fine then the Audio Zones disappeared. I've scoured the community knowledge-base and attempted several of the suggestions with no change.
Nothing has changed on my network and everything else works fine even RoonArc is working.
Short of removing and re-installing Roon Server and restoring the database are there any suggestions to troubleshoot the problem. I've eliminated Firewall and VPN as potential causes. Everything else on my network is working normally.
Describe your network setup
Tmobile Internet G4AR Gateway that connects to an Asus AX-11000 Pro router that has IPV6 passthrough enabled, the Roon Core is connected to that device directly via ethernet. Netgear Network Switch to all other devices including several Roon Audio Devices. All working fine until the migration.
Problem worse on MacBook Pro 2021 running Sequoia 15.2.
All zones on the network not directly connected to the Mac disappear. All of my Sonos gone. Can’t see iPads or iPhone as endpoints. Can’t see PC as endpoint.
I’m also running Tailscale as I use ROON ARC in the car and this was the previous fix. Toggling Local Network permission does not help. Switching wifi on and off does not help. Switching ethernet connection on and off does not help.
Router is TP Link, connected to a switch and also running MESH network from the TPlink in the house. Rebooting router does not work. No changes to house network in past year. It’s very solid. I’ve also run both USB/Ethernet and wifi from the MacBook Pro for a long time, that’s not a change.
This problem began with Sequoia…