Audio devices not showing after Roon Server setup on MacMini (ref#DXNLI1)

What is the issue with your audio zone(s)?

· All audio zones missing

Restart Roon Server

· No, the issue is still the same even after a restart

Restart Network

· No, the issue is still the same even after a restart

What is the operating system of the affected device?

· Linux (other)

Describe the issue

I have Roon Server on a Tahoe M4 MacMini. New install. On setup it located my Marantz 70s, Blue Node Vault and Sonos devices. After completing setup they don’t show in my audio devices. Tried rebooting the server and devices. Only things I did was ad sport forwarding and one music folder. This MacMini is also a plex server.

Describe your network setup

Ubiquiti Cloud Fiber Gateway and a few switches. All devices are wired.

Good day @John_Crick !

We’re sorry to see you’ve bumped into such a problem.

What you are observing can happen because of security policies in macOS 26.

In order to resolve this part please go to the System Settings → Privacy & Security → Local network and make sure to grant permissions for Roon and Roon server. If they are already granted please retoggle them.

Let us know please whether it helps.

Have a nice day!

Regards.

Toggling and restarting roon didn’t help. My room app is still scanning my library fwiw.

Hi @John_Crick,

Are you using any managed switches in this setup? Where are the audio devices positioned relative to RoonServer in your network topology?

Does this only affect networked endpoints, or are you also having issues seeing Mac-controlled Zones like System Output?

Roon’s network discovery relies on multicast - please ensure that multicast forwarding is toggled on for any managed network components you have in this setup (access points, mesh nodes, managed switches).

The Mac Mini RoonServer instance, while recently online, has so far not responded to our automatic diagnostic logging requests. Do you have any third-party network security software that might be restricting traffic to/from Roon?

We’ll watch for your response. Thank you!

I have four managed switches in my network. Here’s a photo of my network topography.

I am not sure I understand your third question. I enabled multicast forwarding and now my devices were seen and able to be configured. It's odd you can't connect to my server. I enabled ARC and received a confirmation. I am guessing something is blocked by my network. Is there something I need to enable to allow you to check remotely?

Hey @John_Crick,

Thanks for the follow-up! It looks like we’re able to enable diagnostics on your instance of Roon Server without issues now.

Are you still having issues at this point? Or, are things performing as expected?

Thank you!

That’s awesome. I am running in to an issue where my server is struggling to play on multiple devices at once. What is the best way to isolate this my content, my server or something else? I attempted to begin playing on both my BlueOS devices. My vault has been playing now for 4 days. When I attempt to play on my node, or Google Speaker, I get nothing, it won’t start playing. Any ideas?

Hello @John_Crick,

Thank you for the update.

We’d like to take a closer look at the logs to better understand what’s happening. To do that, could you please reproduce the issue once more and provide us with:

  • The exact local time when the issue occurs
  • The name of the track you were playing (or trying to play) at that moment

Once we have that information, we’ll enable diagnostics on your account and review the logs around that timestamp for any relevant clues.

Thank you for your help!

Hi @John_Crick,

Roon playback can be sensitive in larger networks with a lot of managed stages. Here’s what we see happening during dropouts with the BlueSound Node2i:

  1. Roon and the Node2i have already passed a device discovery phase and recognized one another as available for connection. This means there isn’t an overt problem with multicast throughput, at least initially.

  2. You click play on the Zone. RAAT’s transport layer attempts to initialize a TCP session with the Node2i to send the audio stream.

  3. RAATServer expects to receive a response to the initialization request within a few seconds, but doesn’t hear anything back from the Node2i.

  4. Playback sits at 0:00 until the handshake fails and Roon tears down the Zone.

Certain managed/enterprise switch features (IGMP snooping, multicast filtering, QoS, or port isolation) can attempt to optimize traffic in a way Roon does not expect. Even if devices show up correctly after enabling multicast forwarding, quirks with multicast hanlding and packet scheduling might be causing these timeouts.

The simplest step would be to toggle on/off some of the settings mentioned above (QoS settings, port isolation, multicast-related settings, etc.) The most thorough test is to connect the Node2i directly to the same access point or router serving RoonServer, with no managed hardware in between.

If you have the router functions enabled in the Ubiquiti gateway, please also double-check these settings there.

We’ll watch for your response and proceed from there. Thank you!

This thread will auto-close shortly without any new responses. Please see the post above and let us know the results of the tests provided and we’ll continue the conversation from there. Thank you!

This topic was automatically closed after 16 hours. New replies are no longer allowed.