Hi. I have had my Roon Server running on the same MacBook Pro M1 Max for about 4 years. Other than the odd problem I have usually been able to resolve.
Now running MacOS Sequoia 15.1.1 my Roon Server can no longer find my Audio Zones - specifically a NAD M33 with BluOS. Both the MacBook and NAD M33 are connected to my network via Ethernet.
All operating systems, apps and firmware have been updated to latest versions. Rebooting everything does not work (including router).
I’ve tried renaming RAATserver and restarting everything but no matter what I try I am unable to get Roon to see the player.
I restored the entire MacBook to a 2 week old backup and all started working again but as soon as I reboot the MacBook the problem reappears.
Are you aware of anything I can do to fix this. It must be Sequoia and I’ve seen a post about this problem on the forum and the suggestion of toggling Roon on and off under Local Network allowing Roon to connect to devices on my local network has not solved the problem.
Please can you suggest anything I could do to in Sequoia to get Roon working again?
@Alun_Marchant Sequoia appears to have changed some of the Mac’s internal networking capabilities. Have you tried toggling the Roon setting Off then back On in the Mac’s Settings → Privacy & Security → Local Network? This works for many Roon users (me included) to allow my Mac Roon Remote see my W11 Roon Server, and it may help your Mac Roon Server see the Zones.
Hi. Many thanks for you help. Yes I found this on a previous post that has been closed so tried it and it did not work. I have just restored my entire MacBook from a Time Machine backup two days ago (luckily I have not lost anything as there were no new files on the machine since that backup) and it’s working again as it was.
I’m very confused about what caused this as absolutely no work or new software of any kind has happened since that backup so Sequoia may have corrupted something and the restore fixed it. I hate not knowing why it’s suddenly working again as I would not want to be restoring backups every few days or weeks when Roon suddenly cannot find and Audio zones other than the MacBook speakers.
I appreciate your help and did toggle that switch off and on again and rebooted the MacBook then restarted Roon with bated breath and luckily all audio zones are still there.
Rebooting MacBook half an hour ago has caused the problem to reappear. I blame Sequoia but don’t have this problem with Tidal or Apple Music. It seems you need a masters degree in Information Technology to configure Roon. It now sees two separate MacBooks - there is only one - and no other audio zones. Overall this has been a painful and expensive mistake (Lifelong license fee was costly in ZAR). I give up as the problems with Roon have been extremely difficult to remedy whenever they happen - which is more frequent than any other software I use.
The issue with Sequoia allowing access to local network devices by third party applications is typically caused by a reboot.
You need to go to settings/privacy&security/local network and toggle the Roon entries off then back on. Then quit Roon server by clicking on the menu bar item and choose quit, then once Roon server has closed, reopen the Roon app. This forces Roon to rescan the network for devices. Your devices should then reappear (do for me every time)
Do not reboot your Mac after toggling Roon off and on in local network as the issue most commonly occurs after a reboot so the toggle is voided.
This does not occur for Apple Music as it is an Apple application and as such does not require local network device access permission as it is trusted. This setting only applies to third party applications. I assume you are using Tidal via Safari (web player) which will also bypass the Sequoia permissions as an inbuilt application or if you use the app the playback chain is passing through browser functionality as I notice the tidal app requires a browser to function (but I don’t use Tidal so could be wrong on this)
Thank you. That does work. I must have misread the post that mentioned toggling this network switch but I thought this had to be followed by rebooting the MacBook. I was getting frustrated - I should’ve read the first post more carefully.
I don’t use Tidal app unless Roon isn’t working. I have a large library of my own music along with the Tidal subscription so Roon consolidating the music from different sources was a significant motivation to go the Roon route to begin with. Tidal cannot do this.
Much appreciated- thanks for not getting irritated by my rant.
No I don’t think you miss read. I have seen instructions that tell people to reboot after the “toggle” a case of people reposting instructions and getting them wrong.
Ranting is often born out of frustration. I have done so myself in the past. Totally understandable
It seems such a simple thing to do but I’m fascinated that someone discovered this little process would result in audio zones being found again. Was it you?
I found it when beta testing the release candidate of macOS sequoia 15.0. It still occurs in macOS 15.2 release candidate. We live in hope either Apple fixes the issue or Roon can find a workaround soon.
Doubt whether I was the first to find it, I stumbled on this workaround when frantically trying to solve this issue on my Roon system and also with Audirvana on another macOS Sequoia notebook. As the local network device access permission was a new feature in Sequoia it was one of several potential culprits. I did post a bug report with Apple prior to release of Sequoia but they are busy with the incremental release of Apple Intelligence in macOS 15 and I assume this is a low priority for them. Here’s hoping Roon can find a workaround, they are looking at it.
I remain impressed that you found the solution. I would not have the patience to test each little thing like this. I admire your perseverance.
Could I just ask an unrelated question? In your opinion is it worth trying the beta function to allow Roon to continue to work with my MacBook closed. It’s off topic so fully understand if you would prefer not to answer this yet.
I don’t know how the beta (and which beta) function is related to this, but it’s possible to configure the Mac sleep behavior in various states.
You can go to the built-in Mac settings and there are some options to prevent sleep with the lid closed, hard disk sleep and App Nap. It may be more convenient and you have more control by using third-party apps like Amphetamine (in the macOS App Store) or https://caffeinated.app/
Thanks yes I’ve been using amphetamine but I’m not keen on adding to Roon complexity with third party software as it’s probably the most “sensitive” app on my MacBook.
I saw a switch in the Roon App under Setup listed as “Enable Lock Screen Controls (Beta)” and I closed amphetamine and switched this on. It does the same thing - it allows me to continue playing Roon with the lid closed. If it continues to work I prefer this approach in Roon itself.
I’ve only seen this in the iPhone/iPad app but maybe I just overlooked it. Though I doubt this helps if you are not playing with the control app on the Mac but from another device she are only using the Roon server on the Mac