Roon unable to detect updated BluOS device (ref#P27KFT)

[Christopher_Newell]

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 cannot find my BluOS (which is fully updated) and works via BluOS app. Thanks for your help.

Tell us about your home network

· ArcherAX21

[noris]

Hello @Christopher_Newell ,

Thanks for reaching out. Can you please let us know the model of the affected BluOS device? Is the Roon Server and the BluOS device on the same network/subnet? It doesn’t show at all in Roon Settings → Audio?

[Christopher_Newell]

A posted suggestion to go to my iMacs System and allow Roon to connect to local network fixed the problem, why that was not allowed, when it was before, is a mystery, and I hope I don’t have to do this every day as the post mentioned.

[Suedkiez (Just a fellow user like you)]

Please see here:

Roon Server Can’t Find Audio Zones / macOS Sequoia Network Connectivity Issue Workaround

Hi everyone, We wanted to provide an update on the Local Network permissions issue described in this thread. Over the past year, our team has spent considerable time investigating whether Roon could detect or automatically recover from the state where macOS revokes or invalidates Local Network access. Unfortunately, after extensive testing and review, we’ve confirmed that this permission state cannot currently be reset or repaired by Roon itself. The Local Network permission system in newer v…

[vadim]

Hello @Christopher_Newell,

I’m glad to hear that toggling the Local Network permission got your BluOS device back on the map!

To clear up the mystery and ease your concerns: no, you shouldn’t have to do this every day. This is a known behavior in recent versions of macOS. It isn’t a bug in the Roon software, but rather a quirk of how Apple manages its security framework (called TCC).

Essentially, when macOS or the Roon app receives an update, the operating system sometimes “invalidates” the existing permission. It’s like the Mac forgets it already gave Roon a key to the front door and needs you to turn the lock manually one more time to prove it’s still okay.

You should only see this occur after a macOS system update or a Roon app update. It certainly shouldn’t be a daily requirement.

As we’ve investigated this thoroughly, we’ve found that Apple does not provide a way for third-party apps to fix or reset this permission themselves. It is entirely under the control of the operating system. If you find it frustrating (and we certainly do too!), the best course of action is to submit feedback directly to Apple support, as they are the only ones who can change how macOS handles these network handshakes.

Since your BluOS device is back and working, I will go ahead and close this thread. If it acts up again outside of an update window, please let us know!

Happy listening!