· My problem is that roon looses connection to my Bluesound node randomly. It will be working fine then at the end of a track is chokes.
Tell us about your home network
· My problem is that Roon looses connection to my BlueSound Node. It will be playing fine for hours, then at the end of a track, it simply stops. Roon tells me to connect to an audio device, or it tells me the track will take a while to play, but it never does. But my BlueSound node is not listed. Other Non Roon Resdy devices are shown, like my TV, or a Dennon amp, and other devices that are of no interested to use. However, BluOS works just fine after Roon craps out.. There is no consistent way to get reconnected. Sometimes rebooting my computer that has Roon Server on it does the trick, but not always. Other times I have to restart (unplug) the Blue Sound Node. This happened on an almost daily basis, rebooting the computer or the BlueSound Node or both.
Tom’s Acer OS Software Spec
Edition Windows 11 Home (latest version) Version 25H2 Installed on 2/1/2025 OS build 26200.8457 Experience Windows Feature Experience Pack 1000.26100.304.0
I am using an ACER Swift SFG14-73T laptop for a computer Memory: 16 GB Bios Version: V1.19 Processor: Intel Core Ultra 7 155H Hard Drive: 954 GB SSD
Could you please try to reproduce this one more time and confirm the exact timestamp when it happens? That will let us pinpoint it in the diagnostics report from your machine.
Thanks. We are looking forward to hearing back from you.
last night Roon again gave me the message the “it will take a while to play the file” message at 8:02 pm. see the attached screen capture. when it stops working I’ll again get the time it occurs and send that info.
Thank you for your post. The failures we see in logs all occur when the Bluesound Node 2 is grouped in a Zone with another endpoint. Here’s an example:
05/26 18:18:11 Warn: [Living Room+Deck] [zoneplayer/raat] Failed to prepare Bluesound NODE 2 in 15000ms. Giving up
Is this laptop on WiFi? First, try hardwiring it during testing to rule out bandwidth congestion. What about the Bluesound Node 2? You mentioned that you need to unplug it to rediscover the device. Do you mean power cycle, or disconnect/reconnect the ethernet?
Do you have any issues if you play to these Zones individually?
It’s worth checking that RAATServer.exe is safelisted in the Microsoft Defender firewall on your laptop, but since this issue is intermittent.
Another possibility is that the laptop sleep settings are interfering with background network activity and preventing consistent access to TCP port 42351, which Roon/Bluesound are using for control here.
Just checking in on this. Were you able to try the tests Connor mentioned, like connecting the laptop by Ethernet, whether the Bluesound Node 2 only fails when it is grouped with another Zone, and confirming whether the Node needs a full power cycle or just an Ethernet reconnect to come back? Let us know what you are seeing, thanks!
I had to buy a Ethernet to USB interface to connect to my computer, what I have found is that if my Node 2 was paired with my other Blusound device, Roon would loose the connection. If the two Bluesound devices were no longer paired, they were instantly available to Roon. If I played two different streams to the Bluesound devices both streams worked for a while but one would get dropped. And finally when playing just the node 2, the stream continued and did not drop the connection for many hours, over 24, before being dropped which simply required me to press play in Roon and it streamed again.
So my question now is:
Roon used to stream just fine to my paired BlueSound devices. now it does not run consistently after a Roon update a few months ago. I should say I had the same problem at our winter home after a Roon Update. On that system I was only have one Node 2i. When I connected that roon server via Ethernet, it was more stable. I use the same computer with Roon Server at both homes.
Is this a problem that other users have had?
Is running Roon Server on an NAS the most stable way to run the server?
Thank you for the thorough testing — this is very helpful. Based on what you found, the issue is clearly related to grouped Bluesound zones. Bluesound’s native BluOS grouping and Roon’s RAAT protocol both try to control the same devices simultaneously when grouped, which can cause conflicts and dropped connections. Playing to each Bluesound device as a separate Roon zone — and grouping them within Roon if you need synchronized playback — is the recommended approach.
Regarding running Roon Server on a NAS: it can be more stable than a laptop, particularly because a NAS runs 24/7 without sleep or power management interruptions. However, the NAS must meet the current system requirements — please see our Docker installation guides for NASes if you go that route.
