NODE 2i endpoint discovery issue requiring power cycle (ref#KA53B1)

Support
1

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *All of my Zones* are affected.

Is your RoonServer machine running MacOS 15 Sequoia or above?

· I still can't see my endpoints as available Zones.

Is the affected network Zone connected with Ethernet or WiFi?

· Ethernet

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· 2025-07-23 around 7:30 pm

What are the make and model of the affected audio device(s) and the connection type?

· Blusound NODE, using Roon Ready and ethernet. Air Play works fine.

Describe the issue

Roon cannot find my NODE 2i, but can find it when I reboot the NODE. Then it works as an endpoint until the NODE goes to sleep. I have to power cycle the NODE to get it to be able to be found by Roon. Blusound support told me "I would advise you to contact ROON support directly as the discovery issue may be with ROON itself."

Describe your network setup

My network setup looks like this: UDM Pro - Unifi USW-16-PoE Switch - Unifi U7 Pro Wall Access Point - Node For my Roon server it looks like this: UDM Pro - Unifi USW-16-PoE Switch - Unifi U7 Pro In-Wall Access Point - Unifi USW Flex 2.5G Switch - Roon Server

2

Hey @42_Below,

Thanks for writing in and for sharing your report! It sounds like a network discovery issue that’s affecting RAAT protocol specifically, rather than a problem with the Node 2i itself. Since AirPlay continues to work, that confirms the hardware and the general network path are functional.

Here are a few next steps for you to try:

  1. Disable IGMP Snooping (or adjust timeout)
    In your Unifi Controller:
  • Go to Settings > Networks > LAN > IGMP Snooping
  • Try disabling it, or set a short Membership Interval timeout if your system allows.
  • Save and apply.
  1. Enable Multicast Enhancement / MDNS Repeater On Unifi APs, check:
  • Settings > WiFi > Advanced > Multicast Enhancement (Bonjour Gateway) → Try enabling.
  • Make sure your Roon Server and Node are on the same VLAN and that MDNS/Bonjour forwarding is allowed.
  1. Reserve IPs for the Node and Roon Core Assign static IPs or DHCP reservations in your UDM Pro to avoid IP churn after sleep/wake cycles.
  2. Update Bluesound NODE sleep settings In the BluOS app:
  • Check if there is a way to disable automatic sleep or increase the timeout.
  • Some users have resolved this by keeping the Node "always on."
  1. Try a direct Ethernet connection (as a test) Temporarily bypass the Flex switch and connect your Node and Roon Server directly to the USW-16-PoE switch, just to rule out switch-level multicast filtering.

We’ll be on standby for your reply and results! :+1:

3

Hi @42_Below,

This thread will auto-close shortly without a response, so we wanted to ensure you’d found the above posts helpful.

Roon relies on multicast for device announcements - WiFi and managed network software can affect the timing of multicast traffic, depending on topology and settings.

If Roon isn’t seeing the Bluesound Node when it wakes from standby mode, then either 1) the Node is not sending new mDNS announcements for some reason or 2) those announcements are being held up/blocked before reaching Roon.

Unifi networks, specifically, can affect the timing of multicast traffic. The most crucial steps are steps 1 and 2 listed above, since these ensure that Unifi nodes are forwarding traffic properly across the network.

Take note that you can prompt a device discovery cycle within Roon by hitting the refresh button of the Settings → Audio page. This might discover the Node without you having to power cycle the endpoint.

Thanks!