Asus wireless router (RT-AX86U)
Netgear Gear 12 port Gb switch
Mac(s) and Roon connected to Gb ethernet ports
No VPN
Connected Audio Devices
USB from Nucleus Plus into Meridian DAC
Number of Tracks in Library
700,000 tracks
Description of Issue
Was prompted that an update of all my devices was available, clicked on it and from then on have been getting it’s taking longer to connect to your core. Have re-booted by entire system plus the iMac a couple of times to no avail. would appreciate if someone could check my logs cc @noris@AMP@vova
It sometimes happens after an update. Is there a screen asking to you connect to a different core? Say yes, it will then tell you that you won’t be able to use the music on the previous core, but that doesn’t matter. Normally it then finds the usual core on the network and you can then reconnect to it.
After saying yes it will proceed to look for cores on the network. It will usually find the one that you always use (probably the only one you have) and show a Connect button next to it. Click Connect and you should be good
Good luck. I also have this occasionally after an update for no particular reason, it always helps to let it search for the core again and it only takes a few seconds to find it either. If it takes long / doesn’t help, then something else seems to have gone wrong
Did this reboot include your network (modem\router\switches, etc)?
Can you look at your router and see if the nucleus is listed as connected and online?
Or ping the IP of the nucleus if you know it?
If it’s never a few seconds for you and even hours (!), then there is always something very wrong. My remotes normally find the core immediately. If they don’t run yet, they start up with the splash Roon logo, and once the app launch is finished, the jellyfish appears for less than a second, then the UI loads and everything is functional. Same on all remotes, Macbook, iPad, Android phone (all on wifi, ROCK is wired). It’s a few seconds all in all from a fresh launch to everything being ready, never more.
What I meant is that in some cases (rather rarely) after an update it happens that the remote searches longer for the core and does not find it. Not sure how long that takes, 10 or 20 seconds maybe? Then it shows a screen that it couldn’t find the core and asks if I want to search for and connect to a different core. I answer yes. Then it shows a message that if I do that I won’t be able to play the music from my previously connected core, and asks if I really want that. I answer yes again. Then it starts the search again and after a few seconds at most it lists the cores that it found on the network - which is always the only core I have, my usual one. Next to it is a button Connect. I click that, there’s a second of jellyfish, and then all is normal.
No idea why it does that occasionally after an update, but it is never an actual problem, it just seems to need a little reassurance and it’s all done in seconds.
Seems to be a problem with the update package, again. I tried to “update all” and now my NUC is rebooting over and over.
Last time this happened it was down for about a week, and then came back to life. Frustrating for such expensive software, but I think eventually an updated package is pushed, without whatever is causing the error.
and it’s all done in seconds.