I am working with BluSound to try to get my Node 2i visible by Roon again. It has not worked in 2 weeks and my Roon subscription is wxpensive and worthless without this working. I followed BluOS suppport instructions to turn everything off my network and deliver all new IP addresses all around and the Roon still does not see the BluSound even though I can see it on rhe network with all BluOS devices and all Airplay devices,
Please help!!
Describe your network setup
Router is from Verizon, network switch from Netgear, a lot of ethernet connections. There is a Apple Extreme extender on network too. Bluesound is on ethernet as is Mac where Roon is resident.
What are the ip addresses of the Roon Server and the BluSound Node? Are they in the same subnet (first three number of the four number ip address the same)?
In your screen shot, there is something strange visible. Under ‘Connected to Roon Server’, you have the device named ‘Kitchen iMac’ which appears to be the machine running the Roon Server. Then in ‘Other network devices’ is show Droinda’s iMac via airplay - but the ip address shown is 127.0.0.1. This ip address is the localhost address meaning ‘this machine’ so this is only correct if the Roon client is running on ‘Dorinda’s iMac’ in which case I would expect this to show under a ‘This Mac’ (in Windows the machine running the client shows under ‘This PC’) and even then, I would expect it to show the real ip address of the machine on you network.
If the client is not being run on Dorinda’s iMac, then there is something wrong.
Was considering going to entirely wifi just to see if that fixes it. Also both the Mac and the Blusound are on a switch not on the router, it is very hard for me to trace all my ethernet cables to get these 2 both on the router which Bluesound said could help. But the wifi thing is fairly easy to test
The switch should not make any difference unless it is faulty.
The ip address and subnet masks all seem to be correctly configured.
I would not move the Roon Server to WiFi for anything other than the briefest of tests. Having the Roon Server attached by WiFi is known to be problematic.
Does your router have any settings for filtering multicast packets and igmp packets in particular? If so the filtering should be enabled (to allow such packets to propagate around the network).
Your original post suggests that everything was working until about two weeks ago. Did anything happen about two weeks ago that may have caused this. One culprit that has caused a lot of traffic on this forum is the upgrade of iMacs to Mac OS 15.1 (Sequoia). Did that happen about two weeks ago?
If your iMac(s) have recently been upgraded to MacOS 15.1, try the solution posted at:
YES! That was it! Roon support page is messed up and I was having trouble submitting a ticket and stupidly should have just posted here myself. Thank you!! Yes it was 15.1 Roon Server was turned off in those settings. I turned both on and off and back on and rebooted to get it to work.
Sequoia has tighter (and more obfuscated) network security settings than preceding MacOS versions. The team has open tickets to address numerous issues that can arise with RAATServer and RoonServer installed on those machines.
Most issues can be resolved with the aforementioned MacOS System Settings workaround - toggling on local network access in Privacy & Settings for RoonServer. If I’m reading your post correctly, this workaround has resolved the issue in your case for now.
A common symptom with Sequoia is the sudden disappearance of all audio devices/Zones in the Settings → Audio page on MacOS Roon remotes/controllers. This symptom is also most likely a result of MacOS network security. The team is investigating actively. If devices don’t reappear after a few seconds, restarting Roon or the affected machine will resolve the issue.
