Did you use a static ip address for your Roon Server with your old router? If so, does the new router employ the same subnet on the Lan side?
If the answer to the first is ‘yes’ and the answer to the second is ‘no’, then your Roon Server will need to be changed to use DHCP to obtain an ip address or the static ip address will need to be changes to an address within the subnet manages by the new router (and the gateway ip address will have to be changed to the Lan side address of the new router).
Usually, on a home network, the netmask is set to 255.255.255.0 meaning that the first three of the four numbers of all ip addresses on your network should be the same. If your old router was, for example, set to 192.168.0.1/255.255.255.0 and the new router is set to 192.168.50.1/255.255.255.0 then any device still on static ip addresses starting with 192.168.0. Will be unreachable.
Thanks Wade, I have it up and running now, had to input the IP a few times as it didn’t do anything, now seems stable. What is interesting is I have 4 zones with Zuma speakers, these are no longer an option on Audio, plus my Lyngdorf in my office, which dropped off when I had router issues, is now showing and working as expected.
Thanks for writing in! Sorry to hear you’re still having issues with audio devices on your Mac running Roon Server.
Can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.
Sorry to hear you’re having issues with your Nucleus! We’re not seeing any Nucleus tied to your account, could you please use the directions found here and send over a set of Nucleus Roon Server logs to our File Uploader?
We’ll need more information regarding your Zuma zones. How are they connected to your network, as well as your Nucleus? Can you confirm each zone is receiving an IP via your router settings devices list?
It may be good to confirm all your Roon devices are on the same local subnet as well - which you can see from the same router settings.
If you haven’t yet, I’d also reboot your router and endpoints as well.