Audio zone disappearing intermittently on BlueOS streamer (ref#H8LB17)

Support
1

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

· My audio zone (blueOS) streamer keeps disappearing. I've had this happen in the past after an upgrade and I was able to fix with reboots. Not working this time. If I step away it sometimes appears on it's own, but it doesn't last. Will disappear in the middle of a track. Core is IMac. Hardwired to ethernet.

Tell us about your home network

· Core is IMac. Hardwired to ethernet. Streamer BlueOS

2

Hey @Kent_Ottwell,

Thanks for writing in and for sharing your report! We were able to review a fresh Roon Server diagnostic report, and see that the most recent logs show a repeating failure pattern:

Roon discovers the NODE 2i, tries to open a RAAT TCP connection, and gets No route to host every single time, dozens of attempts across several hours.

“No route to host” is not a timeout, it’s an immediate, hard rejection from the network stack. This means the NODE 2i’s IP is reachable, but something is actively blocking TCP connections to that port. The three most likely culprits:

  • The NODE 2i's BluOS firmware changed the RAAT listening port, and that new port is being blocked by a firewall rule, either on your macOS Application Firewall or by something in the Verizon CR1000A router's internal switching rules.
  • The MAC address / IP lease shifted and the router now applies different ACLs to that device. (The IP itself stayed at .155 throughout the logs, so this is less likely but worth noting.)
  • The NODE 2i is in a bad state, advertising a RAAT port that its own internal process isn't actually listening on yet.

With that, earlier in the logs there are clear dropout storms with long rtt sync warnings showing RTT spiking from ~1.5ms to 300ms+, followed by repeated “status”:“Dropout” messages and the session being killed with “Too many dropouts (>3s dropped out in the last 30s).”

Here are some immediate next troubleshooting steps to try:

Step 1: Assign the NODE 2i a DHCP reservation (static IP) In your Verizon CR1000A router, find the NODE 2i by MAC address (90:56:82:40:8f:6c) and pin it to a fixed IP. This eliminates any possibility of the IP changing and ensures router rules are consistent.

Step 2: Check for a BluOS firmware update The NODE 2i in the logs is running a BluOS kernel from July 2025. Go to the BluOS app → Player Settings → Check for Updates. A firmware bug causing the RAAT listener to crash and restart periodically is consistent with everything seen here.

Step 3: Disable the NODE 2i’s auto-standby / power-saving mode In the BluOS app → Player Settings → Auto-Standby, set it to Off or the longest available interval. The logs show the NODE reporting “source”:“standby” when Roon reconnects. If it’s going to sleep and waking up with a stale RAAT port binding, that would explain the pattern exactly.

Step 4: Check macOS firewall Go to System Settings → Network → Firewall. If it’s on, make sure RoonServer is in the allowed apps list and not set to block incoming connections. macOS Sequoia tightened some network rules.

Step 5: For the dropout issue specifically, the dropout pattern (RTT spiking 100x) points to something on the network path between the iMac and the NODE becoming congested intermittently. Since both are ethernet, check: the switch/patch panel between them (if any), whether the NODE is actually ethernet or has fallen back to WiFi in its settings, and whether the Verizon CR1000A has any QoS or traffic shaping enabled that might be throttling the RAAT stream.

We’ll be monitoring for your reply, thank you Kent! :folded_hands:

3

Hi Benjamin -

Thanks for the prompt response.

The audio zones were back this morning. As soon as they drop out again, I’ll try your suggestions.

I’ll let you know…Best, Kent

4

Update:

Step 2 - I checked for updates in BluOS. No updates available.

Step 4 - Firewall is turned off.

Step 3 - I do not see an “Auto-Standby” setting in BluOS app settings

Steps 1 and 5 - These are technically challenging for me. I’ll need more assistance. I’ve attached screenshots of router settings.

Screenshot 2026-05-30 at 9.15.43 AM
Screenshot 2026-05-30 at 9.15.43 AM1756×1212 154 KB

Screenshot 2026-05-30 at 9.13.03 AM
Screenshot 2026-05-30 at 9.13.03 AM1676×1836 230 KB

Screenshot 2026-05-30 at 9.12.35 AM
Screenshot 2026-05-30 at 9.12.35 AM1942×1482 188 KB

5

Hey @Kent_Ottwell,

Before sharing a more specific step-by-step below, I also wanted to check to see if you may have multiple active subnets in your network. If so, this could definitely be causing you issues.

Here is more info on subnets in your network:

Reviewing all the IPs of your devices would be a good way to check this. Make sure every device on your network has the same 7 numbers, for example:

192.168.1.yyy

Here’s a breakdown for step 1:

Step 1: Log into your CR1000A Router

  1. Open a browser and go to http://192.168.1.1
  2. Enter your admin credentials (default username is usually admin; password is on the sticker on the router)
Step 2: Navigate to the Connected Devices
  1. From the home dashboard, click "My Network" in the top navigation (sometimes labeled "Network")
  2. Select "Network Connections" or "Connected Devices"
Step 3: Find the NODE 2i by MAC Address
  1. Look through the list of connected devices for MAC address 90:56:82:40:8f:6c
  2. It may show up as "NODE 2i", "Unknown", or a generic device name, the MAC address is your identifier
  3. Click on that device to open its details
Step 4: Set the DHCP Reservation
  1. Inside the device details, look for an option like "Reserve IP", "Static IP", or "IP Address Reservation"
  2. Toggle or enable that option
  3. The router will typically pre-fill the device's current IP address — you can keep that or choose a specific one (e.g., 192.168.1.50)
  4. Confirm the MAC address shown matches 90:56:82:40:8f:6c
  5. Click "Apply" or "Save"
Step 5: Confirm the Reservation
  1. The device should now appear with a lock icon or "Reserved" label in the device list
  2. Note down the IP address you assigned, you'll need it for all future router rules
Additonal notes:
  • If the NODE 2i is currently offline, the CR1000A may still let you add a reservation manually by entering the MAC address directly under a "Add Device" or "Add Reservation" option
  • You may need to reboot the NODE 2i (not the router) after saving so it requests a fresh DHCP lease and picks up the reserved IP
  • To verify it worked, check the device list again after the NODE 2i reconnects, the assigned IP should match your reservation
For Step 5:

Check 1: Verify the NODE 2i is Actually on Ethernet (Not WiFi Fallback)

  • Open a browser and go to the NODE 2i's reserved IP (e.g., http://192.168.1.50)
  • Log into the NODE's web interface
  • Navigate to "Settings" → "Network" or "Connectivity"
  • Confirm the active connection shows "Ethernet" — not WiFi
  • If WiFi is shown as active or as a fallback, disable WiFi entirely in the NODE settings to force it to stay on ethernet
Check 2: Inspect Any Switch or Patch Panel in the Path
  • Physically trace the ethernet cable from your iMac and from the NODE 2i, do they plug directly into the CR1000A, or do they go through a switch or patch panel first?
  • If there's a switch in the path:
    • Check its indicator lights, a healthy gigabit link shows a solid green/amber light; flashing amber or no light on a port indicates a problem
    • Try bypassing the switch entirely by running a direct cable from the NODE 2i straight to the CR1000A, even temporarily, to rule out the switch as the culprit
    • If you have another port on the switch, try moving the NODE's cable to a different port, switch ports can fail intermittently
Check all ethernet cables in the path:
  • Reseat both ends of each cable (unplug and firmly re-plug)
  • Swap out any cable that's coiled tightly, sharply bent, or looks damaged, even a partially broken cable can cause intermittent RTT spikes
Check 3: Disable QoS / Traffic Shaping on the CR1000A
  • Log back into your router at http://192.168.1.1
  • Look for "Advanced" settings in the top nav or sidebar
  • Navigate to "QoS", "Traffic Shaping", or "Bandwidth Management"
  • If QoS is enabled, either:
    • Disable it entirely to test if that's the cause, or
    • Add a rule to set the NODE 2i's reserved IP as highest priority / unthrottled
  • Click Save/Apply and monitor for dropouts

Let me know if this helps, and if you have any additional questions along the way! :folded_hands:

6

Hi Benjamin -

I connected my streamer via ethernet yesterday, and so far so good.

I’ll let you know if that changes.

Thank you,

Kent