Migrated to Unifi network at home. None of the Airplay devices (Sonos, Sennheiser Ambeo and one Airplay2 receiver) are no longer seen as a Zone in Roon. All the devices are on the same network and in the same VLAN. Any idea what might be going on?
Describe your network setup
Unifi E7 access point, Unifi Flex 2.5G and XG switches.
Thanks for reaching out. I am looking over your account diagnostics and I noticed that you have two Roon Servers, a NAS and a Windows machine.
Can you please confirm if the issue is the same when using either one of them? To note, you can switch between Roon Servers as often as you’d like, but you can only have one active at a time.
Additionally, looking over your NAS diagnostics, we can see that it has quite a few subnets associated with it. Your Windows PC seemed to be on a 192.168.50.XYZ subnet, but your NAS appears to be on 10.0.XYZ, 10.3.XYZ, 10.5.XYZ, and a 10.7.XYZ subnets.
I have never had a machine called LOCOLOS. I did rename RoonServer to RoonServer_old, but couldn’t connect to it. After that I renamed it back to RoonServer and I had to select new Roon which was my old Roon on NAS. However, I don’t see anything else but local PC:
But I figured it out. I have several networks created. Default one for all Unifi devices, Home, Kids and IoT.
Devices that are directly connected to switch land in Default network. I had mDNS disabled for it. Once I enabled it, voila:
The second RoonServer instance is hosted on a Windows 11 machine locally named “LOCOLOS” per our diagnostic servers.
Ensure multicast forwarding and IGMP snooping are enabled in the Unifi settings. Restart RoonServer to initiate a device discovery cycle - this should also update our diagnostic servers.
If the Airplay Zones are then visible to the RAATServer instance in the NAS, their IP addresses should populate with the latest logset.
If you want to clear the second RoonServer deeply from the Windows machine: