Waiting for your Roon server. Roon is trying to connect...Taking ages!

Thank you. I will perform 2 successive reboots this evening when I get home. Then, as requested, will inform back here with the exact date and time when I notice the issue occurring. I appreciate your efforts.

I have just rebooted the Nucleus. Twice. Here in Australia, it is Thursday, 31 October, 7:53 PM AEDST. Currently, in Los Angeles, it’s 1:54 AM on 31 October. I will message you again with the date/time when the issue recurs. Typically, this is shortly after 24 hours from a reboot of the Nucleus.

FWIW, after every reboot, I can leave the house or select ‘disconnect’ via any remote on any device, close the app, and on relaunch the Nucleus shows as ‘Ready’ to connect with a green light. I can duplicate this repeatedly with the same ‘Ready’ status of the Nucleus every time. However, about 24 hours later, every time I leave the house or manually disconnect, the Nuclues no longer indicates it’s ‘Ready’ and instead shows ‘Initializing’ for an extensive period before eventually showing ‘Ready’. That is where the issue is. Upon a reboot, the Nucleus is perfect…and then, 24 hours later, it starts having this issue and thus, the title of this support thread.

Okay Noris, unexpectedly, the issue has returned exactly 2 hours and 34 minutes after the second reboot. The date and time here in Melbourne, Australia is:

Thursday, 31 October 10:28 PM AEST
[Thursday, 31 October 4:28 AM US PDT]

Noris, I haven’t restarted the Nucleus as usual, and the issue is worse than ever.

Currently, Tuesday, 5th November @ 12:26 AM PST

Adjusting, it is 7:27 PM on Tuesday, 5 November here in Australia.

Hi @Tom_Zappala,

Thank you for your patience. Here’s where we stand:

The verbose logging we’ve enabled hasn’t exposed any evidence of the Nucleus’ network interface or backend processes failing or enduring stress during the timestamp you’ve indicated.

However, the network availability of devices on the local network is fluctuating. We see controllers and endpoints dropping, but the Nucleus retains its own connection to the internet and upstream servers. RoonServer reports that the controller devices (Mac, Windows, and iPhone) no longer have a network path to the Nucleus. Since the Nucleus’ network interface remains online, we have to assume this is a local network issue.

It’s worth noting that the network path itself does recover - the Nucleus eventually finds these controllers and endpoints again. However, they don’t retain a connection long enough to indicate they’ve reconnected.

Rebooting the Nucleus triggers certificate renewal within the router, as well as network-wide device discovery as we’ve mentioned above. Since rebooting reliably restores your connection to controllers, we need to investigate how the router/network are handling these announcements.

How, specifically, is your network configured relative to the Nucleus? Please describe the network pathway, including any switches, access points, or mesh nodes, between your Nucleus and your main router. Please also describe how you have configured your WiFi hardware to accommodate the other controllers and endpoints.

Diagnostics indicate that Roon is struggling with bandwidth allocation when it downloads and distributes high-resolution files to grouped Zones. Until we have direct evidence of hardware failure or performance decline on the Nucleus itself, then interference with WiFi or network traffic handling are the most likely culprits for this cyclical disconnection problem.

Thank you for your patience and we’ll promptly provide an update once we see your response.