· I have a Roon Nucleus One at work to replace my Mac Mini M2. It often freezes and states, waiting for Roon core. There are also instances where the remote screen will not load at all. I have tried rebooting my core, reinstalling the software, trying different Ethernet cables, clearing cache. This was not an issue with my Mac and is never an issue with my home Roon Nucleus One.
Thank you for your report and we’re sorry to hear you’re having issues.
We’ve taken a look at Roon logs from the affected Nucleus One and see evidence of things:
First, certain Qobuz tracks are failing to play because of a problem with the implementation of the upstream content delivery network serving Roon via the Qobuz API. Roon and Qobuz are working together to fix this urgently. We have just released a patch that will cause affected Qobuz tracks to fail, rather than suspend at 0:00 endlessly, and we see evidence of tracks failing for this reason on your FiiO endpoint.
In other cases, we see Roon endpoints and Roon remotes disconnecting because a sudden network change terminates the TCP session. The network serving this Nucleus One isn’t behaving in a manner Roon expects. You mentioned the unit is at your workplace; is this an enterprise network, or a large mesh network with multiple WiFi access points?
Fortunately, we don’t see evidence of crashing or memory problems that might mean the database itself has a problem.
Where specifically is the Nucleus One connected via Ethernet?
This thread is now closing due to inactivity. You can reactivate it anytime to continue troubleshooting by submitting a new support request here, referencing this thread URL.
