· None of the above quite fits
· App interface looks or behaves oddly
· Audio devices from Multiple Macs merge into one list and behave oddly
· unifi udm pro
Strange Mac client behaviour - #5 by mjw more in thread here
Hey @Gav_Reid,
Thanks for writing in and for sharing your report!
We were able to review a fresh Roon Server diagnostic report, and saw that both your Macs share the same RAAT client ID.
Let’s see if refreshing your RAATServer database may help you here.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Let me know if this helps, thank you! 
Hi Benjamin , this was tried when a chap on the forum recommended a clear and reinstall
Library/roon & /Library/Raatserver and the binary were removed from both macs (trash emptied )
And the client downloaded and reinstalled manually ( was brew installed before)
The screen shot was from after that procedure was completed
Hello @Gav_Reid,
Thank you for the update and for confirming that you already performed a complete wipe of those folders. That is helpful to know and rules out a simple cached file issue.
If both Macs are still generating the exact same RAAT client ID even after a completely fresh, manual installation, it usually points to a deeper system-level similarity. Roon generates its unique RAAT ID by looking at the underlying hardware and OS network identifiers.
When two physically separate devices end up holding onto identical IDs despite fresh software installs, it is almost always due to how the operating system environments were originally set up.
To help us figure out how to break this link, could you let us know how these two Macs were initially configured—specifically, did you use Apple’s Migration Assistant, restore one Mac from the other’s Time Machine backup, or clone the hard drive from one machine to the other?
Sure, I can help with that. One Mac is a corporate device that has been built from with a Jamf ?profile. The other machine was built entirely from scratch by hand
Originally software would have been installed with the tool Brew, but to diagnose this issue I installed Roon manually after the cleanup steps were performed
There is occasionally a third Mac that appears and that also probably has the same RAAT client ID.
This machine was recently reinstalled using the recovery process.
Out of curiosity, where does the RAAT ID get built on the client ? Or is this something that the server vends to it?
I ask as my server is possibly a little unconventional. It’s running a Linux installation with the binaries downloaded from your website.
I was going to try rock, but I don’t have the machine at the moment.
trying to rule out my server , built a new server based on your ROCK image.
performed the uninstall , delete RAATServer & Roon directories from Library reinstall dance
on corp machine started up the app , logged into the new server went to the setting audio panel
on home machine started up the app and left it (not even clicking on the get started button)
corp machine displays the additional audio devices from the home Mac
RAATServer_logs show the same machine_id !
So the behavior is the same with my server or rock. It behaves the same.
what’s next?
Can you give me technical detail on how the machine ID is actually calculated?
Hello @Gav_Reid
Please use the below steps to reset your Roon Machine ID and separate the remote from the server:
thanks , that’s fixed it.
Both remotes report differing machine_id’s in the RATTServer logs now
as my server is linux based I added some notes that are relevant
systemctl stop roonserver
systemctl status roonserver
○ roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; preset: disabled)
Active: inactive (dead) since Tue 2026-05-26 16:43:55 UTC; 14s ago
Duration: 5d 2h 47min 14.700s
Invocation: 6cec300016854193a0535bd14fade0a1
Process: 410 ExecStart=/opt/RoonServer/start.sh (code=killed, signal=TERM)
Main PID: 410 (code=killed, signal=TERM)
Mem peak: 7.2G (swap: 2G)
CPU: 9h 1min 39.763s
May 25 13:16:48 lost start.sh[464]: [AAC/oop] GOT 44100/24/2 8821 samples mf=0x7f22e803feb0 underlying_objecttype=-1 underlying_sfidx=-1
May 25 13:16:48 lost start.sh[464]: [AAC/oop] GOT 44100/24/2 8848 samples mf=0x7f22f40face0 underlying_objecttype=-1 underlying_sfidx=-1
May 25 13:17:06 lost start.sh[464]: [AAC/oop] GOT 44100/24/2 6465 samples mf=0x7f230c12c840 underlying_objecttype=-1 underlying_sfidx=-1
May 25 13:17:06 lost start.sh[464]: [AAC/oop] GOT 44100/24/2 8695 samples mf=0x7f22e00b5bf0 underlying_objecttype=-1 underlying_sfidx=-1
May 25 13:20:28 lost start.sh[464]: [AAC/oop] GOT 44100/24/2 8038 samples mf=0x7f230407edf0 underlying_objecttype=-1 underlying_sfidx=-1
May 25 13:21:52 lost start.sh[464]: libpng warning: iCCP: known incorrect sRGB profile
May 26 16:43:55 lost systemd[1]: Stopping RoonServer...
May 26 16:43:55 lost systemd[1]: roonserver.service: Deactivated successfully.
May 26 16:43:55 lost systemd[1]: Stopped RoonServer.
May 26 16:43:55 lost systemd[1]: roonserver.service: Consumed 9h 1min 39.763s CPU time over 5d 2h 47min 15.073s wall clock time, 7.2G memory peak, 2G memory swap peak.
cd /var/roon
ls
RAATServer RoonGoer RoonServer
rm -rf RAATServer
rm .rmembid
systemctl start roonserver
systemctl status roonserver
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; preset: disabled)
Active: active (running) since Tue 2026-05-26 16:51:07 UTC; 22s ago
Invocation: 4909b3e0c4c1465fbee39a7ee740a706
Main PID: 80687 (start.sh)
Tasks: 190 (limit: 1041)
Memory: 328.3M (peak: 328.3M)
CPU: 22.673s
CGroup: /system.slice/roonserver.service
├─80687 /bin/bash /opt/RoonServer/start.sh
├─80695 /opt/RoonServer/RoonDotnet/RoonServer RoonServer.dll
├─80718 /opt/RoonServer/RoonDotnet/RoonAppliance RoonAppliance.dll -watchdogport=34245
├─80719 /opt/RoonServer/Server/processreaper 80718
└─80763 /opt/RoonServer/RoonDotnet/RAATServer RAATServer.dll
May 26 16:51:07 lost start.sh[80695]: 00:00:00.001 Info: get lock file path: /tmp/.rnsgem0-
May 26 16:51:07 lost start.sh[80695]: 00:00:00.027 Info: GetLockFile, fd: 74
May 26 16:51:07 lost start.sh[80695]: 00:00:00.027 Info: GetLockFile, res: 0
May 26 16:51:07 lost start.sh[80695]: 00:00:00.028 Trace: Nope, we are the only one running
May 26 16:51:07 lost start.sh[80695]: Initializing
May 26 16:51:07 lost start.sh[80695]: Started
May 26 16:51:10 lost start.sh[80718]: [Sentry] Initialized for RoonServer (appliance), release: roonserver@206601658+production
May 26 16:51:10 lost start.sh[80718]: aac_fixed decoder found, checking libavcodec version...
May 26 16:51:10 lost start.sh[80718]: has mp3float: 1, aac_fixed: 1
May 26 16:51:12 lost start.sh[80695]: Running
Hello @Gav_Reid
Can you try clearing your endpoint cache? You can do so using the following steps:
endpoint_ files in this directory.Note: Deleting these files will
If this doesn’t help, please restore the backup you made before trying these steps.
Hello @Gav_Reid ,
Just checking in on this, and we wanted to see whether you had a chance to create a fresh backup, stop Roon Server, and clear out the endpoint_ files in the /Roon/Database/Registry/Core/ folder. If you tried that already, did restarting Roon afterward change anything with your audio devices? Let us know what you found, thanks.