Is the affected network Zone connected with Ethernet or WiFi?
· WiFi
Does the issue affect all file formats?
· The issue affects *multiple/all* file formats.
Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has *no problem*, it's only my other Zone.
How is the affected Zone connected to your RoonServer machine?
· Network - WiFi
Which network audio protocol is the Zone using with Roon?
· RoonReady
Does the device show up at all in Roon Settings -> Audio?
· Yes, it shows up there, but it isn't Enabled
Does the "Enable" button unlock the Zone?
· I pressed Enable, but the Zone remains disabled
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
If the device has multiple output options, do the other options work as expected?
· Multiple output types are affected
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?
· Few weeks but very bad today
What are the make and model of the affected audio device(s) and the connection type?
· Bluecore Node2i
Describe the issue
Bluecore Node2i suddenly not working well after Roon software update. Works ok with BluOS and Spotify. Can work for a few hours or few days after switching off and on Roon Titan. No sound output
Thanks for the detailed answers on the initial questions. Before we go further, we need a clearer picture of exactly what’s happening and how to reproduce it, since a few parts of your description are ambiguous to us right now.
Could you please walk us through the exact sequence of events, step by step? Specifically:
When you say you switch your Nucleus Titan off and on to get sound working again, do you mean you fully power cycle the Titan itself (unplug or use the physical power button), or does the Bluesound Node 2i go into its own standby/idle state on its own, separate from anything you’re doing to the Titan?
Please also let us know: right before the Node 2i loses sound, is it actively playing music and it just stops, or is it more that you go to start playback and nothing comes out? And when you say it can work for “a few hours or a few days” before failing again, does anything specific happen right before it fails (a schedule, an idle period, a network hiccup), or does it seem to happen at random?
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here. However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information. First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
The more precisely you can describe the exact steps that lead to the Node 2i losing output, and the exact steps that bring it back, the faster we’ll be able to pin down what’s happening on our end.
When I switch the Nucleus Titan off and on, I mean that I fully power cycle the Titan itself at the physical power outlet.
Right before the Bluesound Node 2i loses sound, it is actively playing music and just stops suddenly. It will not play again after that.
To get the sound working again, the exact steps vary:
Sometimes just power cycling the Titan at the outlet works fine.
Sometimes I also have to power cycle the Node 2i itself.
Sometimes I additionally have to disable and re-enable the Node 2i within the Roon app.
When the failure occurs, the Node 2i may change spontaneously to fixed volume, whereas it is usually set to device volume. Screenshots of the two with volume set to 9 and suddenly goes to fixed volume attached for you.
Please go ahead and enable the diagnostics on my account. It is not working now.
Thanks for the logs and the volume screenshots, they told us exactly what’s happening.
The logs show that every one of these dropouts is happening on the network link to your Node 2i specifically. During playback, we’re logging hundreds of “buffer overrun” and audio “dropout” events for the Node, and none at all for your other Roon endpoints on the same Nucleus. What that means is the Titan is sending audio fine, but it isn’t reaching the Node reliably, so once too much audio has dropped, Roon stops the stream. That’s the sudden stop you’re hearing.
The switch to “fixed volume” is part of the same event, not a separate problem. Your Node is correctly reporting its volume control every time it connects; when the connection gets shaky, Roon temporarily falls back to fixed volume because it can’t reach the device to control it. So that flip to fixed volume is actually an early warning that the link is dropping.
The fix is to stabilize the Node’s connection:
Connect the Node 2i to your router by Ethernet if at all possible. This is by far the most reliable fix and, based on the logs, I’d expect it to resolve this completely.
If it has to stay on Wi‑Fi: give the Node a strong 5 GHz signal, set a DHCP reservation so its IP never changes, and on the Asus router try disabling Smart Connect / band‑steering and Airtime Fairness, which are known to disrupt Roon (RAAT) streaming.
Until the link is solid, avoid grouping the Node with your other zones, grouped playback needs tight timing and fails much faster on a marginal Wi‑Fi link, and your logs show the Node is grouped most of the time.
Try the Ethernet connection first if you can, and let us know whether the dropouts stop. Thank you!
Wanted to follow up on this and see if you’ve had a chance to try the network changes we suggested for the Node 2i. If you can, please connect it by Ethernet first, or, if it has to stay on Wi-Fi, give it a strong 5 GHz signal, set a DHCP reservation, and disable Smart Connect or band-steering plus Airtime Fairness on the Asus router. It would also help to keep the Node out of grouped playback until the link is stable, since the logs showed the dropouts were happening on that endpoint specifically. Let us know what you’re seeing after those changes, and we can take it from there.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Thanks for your suggestions. Can’t connect via ethernet cable due to physical constraints. Need to contact my internet guy to reconfigure network as suggested so unable to test as per your email.
I’ve connected my Bluecore Node to a new router via Ethernet cable as suggested. Had a similar drop again just now. Music played for slightly more than a hour before stopping. Similar to previous problem via Wifi. Volume also reset to fixed volume. Had to power off and on the Roon Titan to get the Node working again with volume now back to device volume. Node was ok until recently. Can please help.
Thank you for going to the trouble of moving the Node onto Ethernet. That result is important, and it changes our reading of this.
If it still stops on a wired connection, then the network link is not the explanation we thought it was, and we need to look elsewhere. Worth noting too that what brings it back is power cycling the Titan, not the Node, which points more at the server side than at the Node.
To go further we need one thing from you, and it has to be precise. Please tell us:
the date and the exact local time the music stopped, to the minute
your time zone or city
what was playing at that moment, and whether it was from Qobuz, Tidal or your own files
Diagnostics record everything your server does, so with an exact time we can go straight to that moment and see what happened in the seconds around it. Without it we are reading days of logs and guessing which stop was the one you mean.
If you can give us the time from the stop you had just now, that works. Otherwise, the next time it happens, please note the clock time before you power cycle anything and post it here.
