Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· None of these quite match
Tell us what's going on
· How add audio devices
Tell us about your home network
· HUMAX BGW320-500
· None of the above quite fits
· None of these quite match
· How add audio devices
· HUMAX BGW320-500
Hello @kramkajs
Roon automatically discovers supported audio outputs that are available on your system or network. If no devices appear under Settings → Audio, it usually means Roon is unable to detect or communicate with them.
Please make sure that:
For step-by-step guidance, please review our Audio Setup Basics article here:
https://help.roonlabs.com/portal/en/kb/articles/audio-setup-basics
If the issue persists, let us know what audio device you’re trying to use and how it’s connected.
I originally installed Roon on my Mac Mini. Roon automatically found my two HiFi Rose RS250s and I could play music from Roon through them. However, the Roon server slowed down my Mac Mini so I purchased a Roon Nucleus One and connected it to my home router. Roon recognized the Nucleus One but but when I chose the Nucleus One as my server it (Nucleus One) doesn’t find my HiFi Rose streamers. How do I get the Nucleus One to recognize the streamers? In Settings|Audio, I tried clicking on the icon to scan for devices but nothing happens.
Hello @kramkajs,
Thank you for the additional details — this helps clarify what’s happening.
From the IP addresses you shared, your Nucleus One is on a different subnet than your Mac and HiFi Rose streamers:
192.168.1.241192.168.86.34192.168.86.xxxRoon discovers network audio devices (RAAT, AirPlay, etc.) using local network discovery, which does not work across different subnets. Because of this, when the Nucleus One is selected as the Roon Server, it cannot see the HiFi Rose streamers that are on another subnet.
To resolve this, please make sure that all of the following are on the same local subnet:
Common ways to achieve this:
192.168.1.x vs 192.168.86.x)Once the Nucleus One and the Rose streamers are on the same subnet, the devices should automatically appear under Settings → Audio without needing to manually scan.
If you’re unsure how your router is segmenting the network, feel free to share more details about your network setup and we’ll be happy to guide you further.
Hi @kramkajs
Diagnostics indicate that the MacOS RoonServer is still online and connected to the Rose.
Did you migrate your RoonServer to the Nucleus One following this guide?
At a minimum, please ensure that RoonServer is fully offline on the MacOS server instance before testing the connection between the Nucleus One and the Rose endpoint.
Additionally, you’ll need to ensure that your Roon ecosystem shares a single subnetwork/VLAN:
Please let us know if you have any questions from here. Thank you!
Hi Connor,
I think that RoonServer may still be running on my Mac Mini. I’ve quit and restarted the Roon software on my Mac but I think it may still be running in the background. Today, when I restarted my Mac and launched Roon, Roon indicated that I had two servers running but only one license.
I just rebooted my Mac Mini and launched Roon. Roon presents me with a screen that says I’m already signed in to a Roon server and prompts me to “unauthorize” my Nucleus One. Does that mean that an instance of Roon server is running on my Mac Mini? How can I tell?
Hi @kramkajs,
You are 100% correct here - Roon Server is still active on your Mac. You can tell by seeing the Roon jellyfish in the upper right-hand on your Mac taskbar.
If you quit Roon Server on your Mac, and re-open the Roon app, does it present you an option to connect to the Nucleus?
Note that unauthorizing and reauthorizing devices isn’t a big deal, and doesn’t hurt anything!
Thank you! ![]()
I have succeeded in removing Roon Server from my Mac Mini. The Nucleus One is the only server that shows on the Roon app. However, the app still finds only the RS250. It does not see the RS250A.
Here is my network setup:
AT&T Fiber Humax BGW320-500 Modem
Google Nest Mesh Router:
Google Nest Mesh Access Point 1
Google Nest Mesh Access Point 2
Nucleus One (connected by Ethernet to the AT&T Humax router
Rose RS250 connected by WiFi
Rose RS250A connected by WiFi
The Humax router, the Nucleus One, and the RS250 all share the XXX.XXX.1.XXX IP address range while the Google Nest mesh components and the RS250A share a different range: xxx.xxx.86.xxx.
The RS250 is located close to the Humax router and may be connecting to the Humax network while the RS250 is located two stories away and is connecting to the Google mesh network.
I don’t know how to get the 250A on the xxx.xxx.1.xxx network.
Thanks for your help.
Hi @kramkajs,
In order for Roon to communicate with all devices, they need to be on the same local subnet.
To do this, you’ll likely need to bridge your nest network to your primary router and get everything running on the same local subnet. Here is more information around this:
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.