Mac and Nucleus connectivity issues post power outage (ref#6GUUC1)

[James_Lewis2 (James Lewis)]

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Is your RoonServer machine running MacOS 15 Sequoia or above?

· I still can't see my endpoints as available Zones.

Is the affected network Zone connected with Ethernet or WiFi?

· Ethernet

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· I believe Saint of Circumstance was playing, at approximately 12 noonPDT when playback just stopped, and roon asked me to select an audio source.

What are the make and model of the affected audio device(s) and the connection type?

· Linn Klimax, connected by Cat 6

Describe the issue

Like another post, I was almost happy to see what a general problem this is … but I’ve spent way too much time this Christmas obsessing over more roon (Mac/roon?)issues.

My Roon server is in a Nucleus, and I am running Sequoia 15.7.3 on an iMac Pro. I'm using an Eero router, andeverything, including a Linn Klimax is connected by cat6 … and until a brief power outage last night had actually been behaving adequately for a couple weeks. I assume the restarts this morning have caused whatever snafu exists between Roon and Mac OS to manifest.

I’ve tried every workaround and check I can think of, including toggling network permissions as discussed on the forum, and will just pack it in at this point, hoping a solution is forthcoming.

I’ll keep looking for answers. I’m super happy some/many? Mac users have success with the network permission workaround … just wanted to let support know that does not work with 15.7.3, at least in this environment, and hope for some help/a solution

Describe your network setup

best I can tell you is above

[vadim]

Hello @James_Lewis2,

Thank you for the detailed write-up — that’s very helpful.

Just to make sure we’re aligned: based on your description, it sounds like Roon Remote on the iMac is no longer properly connecting to the Nucleus, and as a result the Linn Klimax is not being discovered as a Zone, even though it’s reachable and works with other sources.

As a quick sanity check, could you please try the following on the Mac:

1. Fully quit Roon, not just close the window

   • Click the Roon icon in the macOS menu bar
   • Choose Quit Roon

2. Wait ~10 seconds

3. Relaunch Roon and let it reconnect to the Nucleus

After a power outage, we’ve occasionally seen the macOS Roon Remote get into a partially connected state, where discovery doesn’t recover correctly until the app is fully restarted.

If this doesn’t change the behavior, let us know and we’ll dig deeper — but this is a good first step to rule out a stale client-side connection.

Thanks, and we appreciate your patience over the holidays

[James_Lewis2 (James Lewis)]

Thank you, vadim.

I have been, in fact, fully quitting roon after toggling network permissions, and restarting roon both before and after restarts of the Mac system operating the network … so I appreciate your confirmation that that should help.

TBH, I’m loathe to shut things down to fully test this right now , as I’ve got everything up and running in a Tahoe environment, hoping it to be less twitchy with this issue, residing on a laptop, and roon finally, with time, was able to see my audio system.

See, I’ve been consistently bedeviled by a host of connection issues with roon since inception: playback suddenly pausing for no reason, at best, or either roon server suddenly not being found, or my audio system being suddenly unavailable as an audio destination, errr zone? Emphasis on suddenly, with no apparent cause, and only to resolve just as mysteriously with time, anywhere from hours to days. (I did not understand the extent to which these behaviors were possibly resulting from MacOS’s management of my local network, being unsavvy when it comes to networks)

I will continue to hope that this Mac/roon network issue gets fully sorted soon, as I’d love nothing better than a new year of something I’m still waiting on, heading into year 3 of use, roon being stable and robust!

I’ll see what Apple has to say about this sad state of their OS, as well : being unable to manage a simple network … as mine is about as simple and straightforward as it gets, right?: roon server in a Nucleus, directly connected to the same network as the audio system with Ethernet cable, so I’ll do my best to register another voice of concern with them, hoping they do their part, as I’ve also now seen that there are a ton of similar issues Mac users are having with other tried and true software.

So, I think you can go ahead and close this ticket. I can see roon’s working on its end, and I’ll update with any new build y’all think addresses the issue, while I push on the Apple side … a little bit wiser, and with renewed confidence I will soon enjoy the stability that the majority of roon users experience.

I really appreciate the direct support and responsiveness from roon. I still have a ton to learn about roon, so, in closing, I’d appreciate any suggestions for the best learning path from here.

Thank you again, for as frustrating as these repetitive issues have been, I feel a definitely renewed confidence in something I was beginning to give up on.

Happy New Year, Jim

[vadim]

Hello @James_Lewis2,

Thank you very much for the thoughtful follow-up and for taking the time to share your experience in such detail — we truly appreciate it.

I just want to reassure you that our engineering team is actively working on both sides of this problem:

• improving Roon’s resilience to macOS network permission and discovery changes, and
• adapting to recent and ongoing changes in macOS networking behavior.

That said, this work is unfortunately non-trivial. Apple does not fully expose or document large parts of the networking stack involved here, and some behaviors can change between minor OS updates without warning. This limits how directly we can detect or work around certain failure modes, especially after events like power outages or interface resets.

Even so, we are continuing to investigate, refine detection logic, and harden recovery paths wherever possible. Our goal is exactly what you described: stable, predictable operation without requiring repeated restarts or “waiting it out.” While we can’t promise immediate resolution, we are optimistic that continued improvements on our side will meaningfully reduce these issues.

Thank you again for your patience, for sticking with Roon through the frustration, and for your kind words about the support experience — they really do mean a lot to us.

Wishing you a smooth, stable, and music-filled New Year ahead.