· Can't find previously working devices on network in Roon but they are there and working using a network analytical tool. Roon server is a 4 year old Mac mini. Had a storm and power outage yesterday, but all is back and working except for this. Roon does recognize and works with the one device that is ethernet connected to the Roon Server but all the others are on a TP-link mesh network and do not appear at all in Roon config audio list. Help!
Tell us about your home network
· TP-Link mesh with 4 satellite units, all check out as working
It sounds like Roon Server is still seeing the wired path, but the mesh-connected zones stopped advertising themselves after the outage.
Since the TP-Link mesh and the Mac mini both survived a power event, the first things we’d check are discovery and network isolation between the server and those endpoints:
Restart the Mac mini and the TP-Link mesh system, including the main router and all satellites.
On the Mac mini, confirm Roon Server is allowed through macOS firewall and any security software that may have re-enabled itself after the outage.
Check whether the missing zones are still getting the same IP addresses and are on the same subnet as the Mac mini.
It would also help to know how the Mac mini is connected right now, wired or WiFi, and whether the mesh is using any wired backhaul or is fully wireless.
If you can share that, we can narrow down whether this is a discovery issue, a subnet issue, or something specific to the mesh after the outage.
It sounds like the WiFi isn’t forwarding multicast device announcements properly if you’re not seeing anything populate in the Settings → Audio page and your WiFi remotes can’t properly connect.
In the Deco app, ensure that the mesh nodes are set to Access Point. If you see any multicast forwarding settings, ensure those are enabled.
I have seen this problem before on my system following a power or internet disruption, devices that have been enabled and working fine just go missing on the Roon ->Audio screen and the list of endpoints. But usually a reboot of the server or restart of the house modem/router along with restarting the endpoint devices resolves the problem. Sometimes just waiting has seemed to do it too. I have never been able to pin down on exact action that solves the problem but some combination of the above would get things going in an hour or so. Now it has been close to 24 hours and nothing I have tried has worked. Perhaps this info will help you in some way.
I’ve considered damage to the mesh system and satellites but the TP-link DECO app says the mesh is optimized and healthy. Out phones and computers are not having trouble using the network from anywhere in the house.
The thread’s gone quiet. I’ve still got the connection problem. Any ideas? One additional peiece of info. I turned on an old Mac that I had configured with old Roon software so it could serve as an endpoint. It did show up on the Roon Audio page. But my other devices don’t.
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.
Thank you Ben. You are the man of the weekend, because this was the fix! I also discovered that I had another copy of the Roon app that I had renamed back when the upgrade past 2.0 was going to obsolete the hardware I was running on at the time and forgotten to delete it later. So somehow in the Local Network window of my computer I have two copies of Roon whose switches turn off and on in unison. I can’t figure out how to delete one, but maybe it makes no difference because everything seems to be working. Do you know how to delete one?
Glad to hear that worked! Since everything is working now, you can leave both of those Roon instances in the security panel. There is no need to delete the extra copy if the system is behaving normally, though if you do find a way you can delete both instances and readd just one.
Since this is resolved, we’ll go ahead and mark the thread for closure. Enjoy your music!
