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.
Greetings. Here are some intriguing details for you to ponder. Over the weekend, I disconnected all endpoints from Roon. I then disconnected everything from my wireless router so that only the Nucleus was connected via ethernet. I then rebooted the Nucleus and within a few hours, the exact same problem occurred.
I have now powered down and disconnected the Nucleus entirely and am running a Roon core via my PC. As of this post, Roon is running exceedingly snappier than the Nuclues ever could. I will report back in a few days with further findings. As of this moment though, I feel that even if my Nuclues wasnât acting up, Iâd prefer running my core on my PC as the experience is ridiculously superior in every way. Every action is near instantaneous whereas the Nucleus felt like running a PC from the 90s on Windows XPâŚdespite the fact it does look âcoolâ. Canât help but feel like I wasted money on it.
Hey @Tom_Zappala,
Thanks for the response, we would love to continue to help pinpoint the issue specifically, but weâll need the information asked by Connor in his prior response:
As of now, all we have is:
As a side note as well, can you confirm that the router has the latest firmware version? Hereâs more info on this:
Another troubleshooting step to try if you havenât yet (and my apologies if this has already been glazed over - this thread is now becoming quite long in terms of responses) is to access the webUI of your Nucleus and perform a RoonOS reinstall.
Weâll be on standby for your reply, thank you!
My PC-based Roon Server continues to operate flawlessly, providing a far superior and operationally flawless experience. The difference is fundamentally improved in every facetâwithout changing anything within my router, network, or devices. The Nucleus is getting scrapped for parts and going in the bin. As a result, this is my final post to this thread as it is no longer necessary.
However, the assistance received here was disappointing and tediously slow. Ultimately, the best support came from using my critical thinking and problem-solving skills. Additionally, multiple posts from the community volunteer were particularly pedestrian, unhelpful and antagonistic. These added nothing and instead were an unwelcome source of unrequested annoyance.
Hereâs the thing. The most simple and common-sense advice should have been to do exactly what I eventually did: try an alternative Roon server and see if the issue is present. Ironically, before purchasing the Nucleus, I used my PC as a core without issueâjust as I am now. As a result, I profoundly regret purchasing a Nucleus. I stupidly fell for the marketing and aesthetics. Admittedly, thatâs on me.
Thankfully, Roon itself is a brilliant achievement in software engineering. I am thrilled to be a lifetime member and will continue to enjoy it for many more decades. All the best.
Hi @Tom_Zappala,
Thank you for sharing your feedbackâweâre sorry to hear that your experience with support hasnât met your expectations. If youâd like to continue troubleshooting, weâre here to assist you and address any concerns. We also encourage you to share your thoughts in our Feature Suggestions category, where they can help us improve. Please let us know how youâd like to proceed!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.