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
· Qobuz playback hangs for 30s / RAAT disconnects after hours of inactivity (Synology NAS Core)
Tell us about your home network
· Router: ASUS RT-AX1800S
Topology & Connections:
- The Synology NAS DS918+ on DSM(Roon Core) is wired directly to the ASUS router via a single Ethernet cable.
- Link Aggregation (Bonding) on the NAS is DISABLED.
- The Audio Endpoint (Cambridge Audio CXN V2) is on the same local network.
- Static IPs are manually assigned to both the NAS and the CXN V2 via the router's DHCP.
Key Network Settings:
- IPv6 is completely DISABLED on both the router and the NAS.
- IGMP Snooping and Multicast Routing are ENABLED on the router (for both LAN and Wireless) to ensure stable RAAT communication.
Extras:
- No VPNs are active.
- No managed switches or Wi-Fi range extenders are used in the audio chain.
Description of Issue
When the Roon system is idle for several hours (e.g., overnight or while I'm at work), attempting to play any Qobuz track results in a massive delay or failure.
Add images
Specifically:
- After hours of inactivity, pressing play on a Qobuz track causes Roon to hang.
- Sometimes it shows "Nothing to play due to unavailability".
- Other times, it shows "Starting playback on your device, this may take some moment" followed by silence, and the log shows RAAT dropouts or Endpoint disconnected.
- After waiting for about 30 seconds to a minute, or if I reboot the Roon Server package, playback returns to normal and I can skip tracks instantly.
Troubleshooting Steps I've Already Taken (Issue persists):
- Completely disabled IPv6 across the entire network.
- Ensured IGMP Snooping is active for RAAT communication.
- Increased Synology's
fs.inotify.max_user_watchesto 524288 via SSH. - Disabled all third-party extensions (including Last.fm scrobbler).
- Reset Cambridge Audio CXN V2 (unplugged power cord) and re-enabled it in Roon.
- Naked Core Test: I completely uninstalled Roon Server, renamed the old shared folder, installed a fresh instance, and logged into Qobuz without restoring my backup and without adding local files. The idle timeout issue STILL happened.
Could the support team please enable diagnostics on my account or review my logs? It feels like the TCP connection to Qobuz API or RAAT server goes into a dead session after idling, and Roon is waiting for a 30-second timeout before recovering. Any help would be greatly appreciated!
