Recently transitioned to Nucleus One, works amazing until it doesn’t. Gets into fits of the “Waiting” “Uh-oh” cycle, then goes without issue for hours. No apparent correlation to reboots, network restarts, reinstalls, etc.
Happens with all remotes, even those not running AVG (eg, iPad).
Just stopped on me at 1817, playing Vaughan Williams London Symphony 4th movement.
I happened to have a reinstall of Arc on the iPad syncing at the same time. It is currently trying to connect and the server wasn’t ready for several tries and then becomes available again. Syncing for the first time again.
Certain multicast settings that are essential to Roon’s device discovery of both controllers and endpoints might not function unless you have enabled IGMP Proxying in the Orbi settings.
See here:
Specifically, uncheck the “Disable” next to IGMP Proxying in the Advanced tab of your Orbi settings.
Are your remotes connecting to the same node to which you’ve hardwired the Nucleus One, or to another mesh node in another room?
It happens whether I’m connected to the main or a satellite, and it happens with any and all remotes when it starts being fidgety again, which it has after almost a week of stable performance.
Yes, both are the way they are supposed to be. Still happening. To recap, never was a problem with my NUC as the core, only an issue since I brought the Nucleus One online. Enjoying some CDs tonight as my Nucleus is basically a decoration as I watch Roon tell me “Uh oh” over and over again.
If you navigate to the Web Admin page for this Nucleus in a browser on your network, do you see any errors presented? Please share a screenshot of the web administration settings.
Roon diagnostics show the RoonServer instance in this Nucleus restarting cyclically on a near-24 loop. Are you running a scheduled reboot via cronjob, an automated power bank, or similar?
Let’s first troubleshoot the connection between a single Roon controller and the Nucleus.
You’ve mentioned AVG. Is this installed on a desktop? If so, verify Roon.exe and RAATServer.exe are added as exceptions. Verify these processes are exceptions in the Windows Defender firewall, if relevant to this controller.