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.
Thank you for your patience while we investigated this! We have identified the culprit: you are encountering a known issue with the Qobuz Content Delivery Network (CDN).
Under the hood, your Nucleus is getting stuck in a loop. It is repeatedly sending requests to the streaming-qobuz-std.akamaized.net network but failing to receive the actual audio data in return. This is exactly what causes your playback to stall.
This specific routing issue is under active investigation by our engineering team. I have attached your diagnostic data to our internal report, which helps our developers map out the scope of the problem and work toward a fix. We will keep you posted right here as soon as an update or workaround becomes available.
We’re sorry to hear you’re not satisfied with our Technical Support response times, certainly feel free to share your feedback over in our Feedback category on the community.
In the meantime, I wanted to also share the tracking thread for the known issue you’re experiencing:
We wanted to revisit this case. If your main symptom is device disconnections, this network may be handling multicast traffic in a way Roon doesn’t expect.
The team can more than likely recommend a few settings adjustments in your router’s multicast settings that can improve or remedy these device disappearance events.
Can you please share where you’ve connected the Nucleus One to your network? Is it hardwired to the main router, or to the access point?