· I had to migrate my Roon Server to a new laptop as with each new update my old server (MacBook Pro, i7) became less reliable. After the migration, I lost the ability to attach to my main streamer (Nativ Vita) which you had allowed to attach to my old server by special exception. (Nativ is no longer in business, although its "uncertified" version of Roon RAAT has given me no problems over the past several years and was working as of yesterday.) Is there something you can do on your end to allow the new server to connect to the new streamer as you did with the old streamer?
Since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.
Please try the following steps:
Open macOS System Settings → Privacy & Security → Local Network
Make sure Roon and Roon Server are both enabled
Even if they are already enabled, please toggle them off and back on
Fully quit Roon Server from the macOS menu bar / task bar
Reboot your Mac
After reboot, launch Roon again and check if the devices is avaliable again.
Once these permissions are refreshed and the system restarted, your audio devices should reappear.
Please let us know if the issue persists after these steps, and we’ll continue from there.
Performed the tasks as indicated. Nativ Vita “is available” insofar as it shows on the menu under the “Roon Ready” tab with it’s network ip address indicated. but when I try to enable i get
“There is a problem with this device.” “Unfortunately, the manufacturer has not yet completed certification for this device.”
We know this, because the manufacrturer went out of business before certification was completed with Roon. However, on my old server, you were able to bypass this error and allow me to enable. the Vita’s RAAT implementation worked flawlessly on my old server after you allowed the device to be enabled.
That did not work on my new server. Still shows same error message for the Nativ device. However, WAS able to upgrade my old server with the latest software, and that allowed me to reconnect it after decommissioning the new server. The restored old server can still connect to the Nativ. Problem solved for now. But it is only a matter of time before the old server hardware is no longer supported and I’ll have to upgrade. When I do, maybe i can restore the backup of the old server to the new and keep my Nativ connectivity that way?
Permission to use uncertified devices has now been applied to your account. That was done on our side, and it is tied to your Roon account rather than to any one machine or database, so it follows you to whichever server you sign in to.
Two things about picking it up, because this is where it went wrong last time.
Quitting Roon Server properly matters, and it is not the same as rebooting. Please quit it from the Roon Server icon in the macOS menu bar and choose Quit, rather than only closing the Roon window or restarting the Mac. Then start it again. Please do that twice, waiting for it to come fully up in between. The permission is picked up when Roon Server signs in, and a clean quit and relaunch is what forces that to happen.
Then please send us a screenshot. Go to Settings, then Audio, find the Nativ Vita under Roon Ready, and press Enable. Whatever appears, whether it works or you get the certification message again, please screenshot the whole screen and post it here. That tells us immediately whether the permission is being seen.
