· Other
· None of the above
· Other
two devices are conflicting; only 1 will play at one time; the units have, in Roon Bridge, the exact same ‘machine_id’
tp-link deco mesh router;
Motorola - MB8600 32x8 DOCSIS 3.1 Cable Modem; gigabyte switch
see this thread for more details:
Hello @doug_wolf
Can you try clearing your endpoint cache? You can do so using the following steps:
Note: Deleting these files will
If this doesn’t help, please restore the backup you made before trying these steps.
OK, i created the backup
finding the roon/roonserver folder and editing it will be a trick; i have roon running on a linux mint machine and my linux skills are very limited; am reading up on how to edit in linux…it looks like i have to use the “cd” and “rm” commands
i was able to use the file manager in mint to go to the folder; it was var/roon/roonserver/database/registry/core; i was able to delete everything in “core”
i restarted roonserver (and confirmed that it is running); when i went to my roon interface on my pc i have the “waiting for your roon server” message; it has been in that status for a couple of hours
i went back to my linux server and there is an open terminal box (from when i restarted roon and checked its status); if i try to close it it says there is a process running and if i close it the process will stop
in file manager i navigated to the “core” folder and it has 8 files in it now; so it is repopulating? how long will this take?
and now there are 9 files, so i guess that is progress 
been over 5 hours and still “waiting for your roon server”…is this normal?
Hello @doug_wolf,
Thank you for the update.
It appears that your Roon Remote is still trying to connect to the old Core, which no longer exists. Please try the following steps:
This should allow your Remote to connect to the newly created Core.
ok, did that; was able to set it up mostly OK
however, looks like the conflicting devices problem has not gone away; when i went to enable devices, roon re-named the living room device “home office” after i had named it “living room” (these are the 2 that have been in conflict before); and when i try to create a group, either living room or home office will show up as options for a group, but not both
i do have roon playing (though not living room), so that is good
Hello @doug_wolf
Thank you for the update.
Could you please confirm the name of the zone you are trying to create with the problematic devices? Is it:
AV room + bedroom + home office + pantry
Additionally, would you be able to share a short video recording showing what happens when you attempt to create the zone group, including the timestamp of the issue?
Thank you!
it would be this plus living room
how do i do this?
it is really simple: when i try to create a group, living room does not show up as an option, even though it shows up in settings/audio
Hello @doug_wolf
| Device Name | Machine ID | Device ID | OS Version | Type | Local Endpoint | RAAT Version | Protocol Version | Notes / Vendor |
|---|---|---|---|---|---|---|---|---|
| HPHOMEOFFICE | fb00120d-e0ce-ea35-631c-79cdeb0a9ddd | raatserver/265da801-832c-48d4-a2d9-78cab5bcd31e | Windows 11 | RAAT | tcp://192.168.68.50:9200 | 1.1.39 | 1 | - |
| bedroom-ropieee | f10df51c-ab90-75b4-4e25-bc0fc1cfb274 | raatserver/0351e879-3b9b-4881-86b5-b8057d917751 | Linux 6.12.42-SPCKFSH-v7+ | RAAT | tcp://192.168.68.65:9200 | 1.1.38 | 1 | - |
| pantry-ropieee | 40ee9695-ddb3-7b1d-40ee-0bc656463b63 | raatserver/c6ee71ce-a6aa-4833-9c25-08e1ff0fc5a1 | Linux 6.12.42-SPCKFSH-v7+ | RAAT | tcp://192.168.68.61:9200 | 1.1.38 | 1 | - |
| living-room-ropieee | 45cee116-2ad9-f7c6-ab6f-4305192d1aad | raatserver/9b1ea5a2-641f-43ff-bdb7-ce3e829033bf | Linux 6.12.42-SPCKFSH-v7+ | RAAT | tcp://192.168.68.56:9200 | 1.1.38 | 1 | - |
| home-office-ropieee | 45cee116-2ad9-f7c6-ab6f-4305192d1aad | raatserver/9d8d5dae-62cf-4049-8827-d6e61fb7808c | Linux 6.6.28-SPCKFSH-v7+ | RAAT | tcp://192.168.68.60:9200 | 1.1.38 | 1 | - |
From what we see in the diagnostic data that all of the devices are recieve all the unique id and device names. Currently from the logs it’s hard to understand what exactly is going on so I have requested the video recording of the process.
You can just record the Settings → Audio tab and what happens while you are trying to create a group and this should be enough to trace it across the logs.
| living-room-ropieee | 45cee116-2ad9-f7c6-ab6f-4305192d1aad | raatserver/9b1ea5a2-641f-43ff-bdb7-ce3e829033bf | Linux 6.12.42-SPCKFSH-v7+ | RAAT | tcp://192.168.68.56:9200 | 1.1.38 | 1 | - |
|---|---|---|---|---|---|---|---|---|
| home-office-ropieee | 45cee116-2ad9-f7c6-ab6f-4305192d1aad | raatserver/9d8d5dae-62cf-4049-8827-d6e61fb7808c | Linux 6.6.28-SPCKFSH-v7+ | RAAT | tcp://192.168.68.60:9200 | 1.1.38 | 1 | - |
take another look: home office and living room have the same machine ID
this is the exact problem we started with (and identified by harry ten berge)
Hello @doug_wolf
Sorry my bad, will discuss this with the R&D team to understand from where we are recieving this ID and will get back here with the updates.
OK, many thanks
Hello @doug_wolf
Could you kindly provide us with the MAC addresses of the Raspberry Pi devices?
You should be able to find them in your router’s DHCP or Clients tab.
sorry, had to go out of town for an emergency
will do shortly…