Hey @Bennard_van_Diermen,
Thanks for reproducing the issue and sharing the track details — that was very helpful. We’ve now reviewed the full diagnostic logs from your ROCK, and we have a clear picture of what’s happening.
What the logs show
The Roon Server is not crashing, and there is no fault on the server side. What we see repeatedly in the logs is this:
[raat_ll/client] [HiBy R6PROMAX @ 192.168.1.199] no data received for >10000ms. Killing connection.
The ROCK’s RAAT client stops receiving any data from the HiBy for more than 10 seconds, hits its built-in timeout, closes the TCP connection, and immediately reconnects. This cycle repeats continuously — we can count dozens of sessions in the log, ranging from 16 seconds to about 13 minutes each, with no stable pattern.
Importantly, this also happens before any playback starts — we can see it firing within 2 minutes of the device connecting, while it is completely idle. This rules out DSD64, the specific track, or any format-related cause. The “Genesis - Takin’ it all too hard” DSD64 drop on June 2 was the same mechanism, not something specific to that format or file.
Your FiiO M11 Plus is on the same WiFi mesh and does not show this behaviour at all, which confirms the issue is specific to the HiBy R6 Pro Max — either its WiFi implementation or its RAAT client build (version 1.1.43).
What you can try on your end
These steps may reduce the frequency of drops while a permanent fix is being investigated:
- Disable WiFi power saving on the HiBy. On Android, go to Settings → Battery → Battery Optimization and exclude the Roon app and any network/WiFi system services. Also check for a “Keep Wi-Fi on during sleep” or “Always On” option under Developer Options or Wi-Fi Advanced settings.
- Disable Adaptive Wi-Fi / Smart network switching if present in the device settings.
- Lock the device to a single WiFi band (5 GHz or 2.4 GHz only) in the ASUS XT8 mesh settings for that device, to prevent roaming between nodes triggering brief disconnects.
- Assign a static IP to the R6 Pro Max on your router to eliminate any DHCP renewal interference.
Our recommendation
Based on what we see in the logs, the root cause lies in how the HiBy R6 Pro Max handles the RAAT keepalive connection — specifically, it periodically stops sending data long enough to trigger the server-side timeout. This is a device-level behaviour that we are not able to resolve from the Roon side.
We recommend contacting HiBy support directly and sharing the following information:
- The RAAT client on the R6 Pro Max (firmware 1.50_20251208-2312, RAAT 1.1.43) intermittently stops sending keepalive data to the Roon RAAT server for periods exceeding 10 seconds, causing the server to close the connection.
- The issue occurs both during playback (PCM and DSD64) and while the device is idle and connected.
- The FiiO M11 Plus on the same network and firmware generation does not exhibit this behaviour, suggesting it is specific to the R6 Pro Max RAAT implementation or its WiFi power management integration.
HiBy would need to investigate whether their RAAT client is being suspended during screen-off, audio decoding, or any battery/thermal management events, and ensure keepalive packets are sent regardless of device state.
We’ll keep this ticket open. If the workarounds above make any difference — or if HiBy provides a firmware update — please let us know and we’ll follow up from our side.