· I see the Server but the Connect button is grayed out
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *WiFi*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *MacOS*
Select any of the following components that are present in your local network setup
· *Mesh networks*
You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.
· None of the above
Describe the issue
When Arcam Radia SA-45 is switched on....it appears in the audio settings as Roon Ready device but then disappears. When Arcam SA-45 is switched off it appears briefly in Roon audio settings as Roon Ready device.
Describe your network setup
router Zyxel EX3301-T0...Roon server on Macbook Pro M5 Max connected to router via WIFI and Arcam Radia SA-45 connected to router by ethernet 'wired' connection.
I have gone to system settings and privacy and security and local network and toggled the Roon app in local network and rebooted Macbook Pro. Still no Arcam SA-45 in roon ready devices in audio settings of Roon.
I have also tried installing early access 2.71 build of Roon…but Arcam Radia SA-45 still does not appear in Roon as a Roon Ready device in the audio settings of Roon
This points to the Mac beta environment interfering with Roon Ready discovery for the Arcam.
As @mjw mentioned, Roon does not support beta releases of macOS, and this kind of device visibility issue is consistent with that. Since this started after installing the macOS 27 Public Beta, the best next step is to move Roon Server back to a supported version of macOS if possible.
Just checking in on this. Have you had a chance to revert to the general release of macOS, and did it help with the Arcam issue?
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Hi I can’t revert to MacOS 27 general release as it has not been released yet. It won’t be released until the autumn… Soon as it is released I will revert to it.
Same issue for me with any networked devices since the first developer beta of macOS 27. I cant see any networked endpoints. Also the Roon server does not register in the local network settings so can’t be toggled. I always do a clean install of the beta’s so maybe the reason for this difference with your issue. The endpoints I cant detect are from Devialet, KEF, Naim and Chord Electronics. Hope Roon takes a look at the beta or at least a release candidate prior to general release rather than waiting until the general release then spending 3 months to fix as has been the case on recent releases. Fortunately my other player of choice has no issue with the Golden Gate betas so far…
You could revert to Tahoe but it will involve a wipe and re-install.
@Mitesh_Doshi, I want to clear up one point that I think is causing some confusion. You don’t need to wait for the macOS 27 general release to get back to a supported environment, the current shipping release of macOS is already the supported one. The recommendation is to move off the beta and back onto that shipping release, not to wait until autumn.
On getting there: as @mjw noted, this usually means unenrolling from the Apple Beta Software Program and restoring your pre-beta backup via Time Machine. If you don’t have a Time Machine backup from before the upgrade, the alternative, as @David_Moore2 described, is a clean install of the shipping release, which does involve wiping and reinstalling. It’s worth backing up your data first either way.
@David_Moore2, thank you for the added data point. Seeing the same discovery failure across Devialet, KEF, Naim, and Chord endpoints, plus Roon Server not appearing in the Local Network settings, lines up with this being a networking/local-network change in the macOS 27 beta rather than anything specific to the Arcam. As has been the case with past macOS betas, Apple often adjusts this behavior late in the cycle and these incompatibilities are frequently resolved by the general release, so we tend to evaluate the betas later in the process rather than chase changes that Apple may revert.
Happy to keep this thread open while you work through the revert, just let us know how discovery behaves once you’re back on the shipping release.
Just checking in on this. Have you had a chance to move off the macOS 27 beta and back to the current shipping release, as we discussed, and either restore from your pre-beta Time Machine backup or do a clean install after backing up your data? Once you are back on the shipping macOS, let us know whether discovery starts working again across your endpoints, including whether Roon Server shows up in Local Network settings.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
