Roon unable to detect Lumin D2 after Mac OS Tahoe 26.3 update (ref#O6MSN9)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon no longer finding Lumin D2 after upgrade to Mac OS Tahoe 26.3

After my Mac automatically updated last week Roon no longer sees my Roon Ready Lumin D2 player in Settings/Audio and my Roon Player cannot select my Lumin D2 (nicknamed Living Roon) as an output zone.

In the past a simple restart wakes the network brain and everything goes back to working as expected.

I have confirmed the following:
All devices on same Network and Subnet connected via Ethernet
Mac OS Tahoe 26.3 Settings / Local Network - Roon is allowed to discover local devices
Roon update to latest version 2.61 build 1639
Lumin D2 updated to latest firmware 21.1b

I do believe this is a Roon issue and not a Lumin issue as my Sonos Speakers, Connects and Amps are also no longer showing as clients in Roon / Settings/ Audio, when previously they were, even though I never used them as output zones

Tell us about your home network

· Verizon Fios
Ubiquiti UDM Pro
Ubiquiti USW Pro

Network has always been configured this way
Rebooted the network to debug.

Hi @mail.mark.bartlett,

The most recent Roon release (today’s release) contained a fix for an issue matching some of the symptoms you’ve described.

Can you confirm that you’re still encountering this on Roon 2.61?

If so, please re-toggle Roon’s local network permissions in MacOS Privacy & Security settings. Sometimes, a MacOS update will restrict Roon’s network access until you re-toggle.

We’ll watch closely for your response and follow up with next steps. Thank you!

Heya Connor. Thanks so much for the quick reply! I am updated to the latest 2.61 build 1639. I have quit and restarted Roon and toggled the Privacy / Local Network toggle on and off a few times and it has not resolved the issue :frowning:

I also see that my backup to my NAS also failed and even though the volume is mounted in Mc OS when I “force backup” it still errors out “Backup directory not available.”

This does seem to indicate that Roon is having trouble locating devices on the network in Mac OS Tahoe.

Please reboot the Mac. Turn off firewall. Make sure Ethernet is being used, WiFi is off. Restart Roon.

1 Like

Hey @mail.mark.bartlett,

Thanks for the update! Were you able to give @wklie’s suggestions a try?

We’ll be monitoring for your reply, thank you! :folded_hands:

Heya Peter and Benjamin-

Thanks so much for the support! Roon just pushed update 2.62 (Build 1641) and that resolved the issue :slight_smile:

Performing the Mac restart, Roon restart and System Settings confirmation with Roon version 2.61 (Build 1639) prior to the update had not resolved the issue. Post update (Roon version 2.62 Build 1641) everything is now working as expected.

Thanks to the support team and teh dev team for getting these updates out to support this incredible community.

Warm regards,

-m

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.