Roon 2.0 Build 1303 (uploaded to Core and remote today) corrected all my issues regarding no access to Nucleus core from iPad or Mac Mini using Roon remote. The previous version, Roon 2.0 Build 1299, brought my system down as Core could not be found. All is well.
@Dennis_Roderick
How were you able to update when you couldn’t connect the Core to the network with build 1299?
@benjamin
I decided to reboot my Nucleus+ one last time last night before I send it in for repair or e-waste, but this time it showed up on the network. It immediately notified another new update. I updated it to 2.0 build 1303, it came back but loading very slowly with missing album artwork. I let it ran overnight and it’s still stuck on synch with the spinning circle (it’s another Roon issue for a different thread). I rebooted Roon Server using the web interface. It came back with the message that says new software update requires updating the database, may take a while. It’s running OK after it came back. It appears the software update was incomplete the first time until I rebooted Roon Server the 2nd time.
Another interesting observation is that the Nucleus+ Roon acted like it’s a brand new Core, a lot of previous settings were reseted, all the Audio Zones had to be enabled again after the last update.
I believe there are basic flaws in the Nucleus+ design. This is my 2nd Nucleus+, last one bricked after a Roon update. Half the time it requires multiple reboots before the unit shows up on the network after an update or power off. This time if took over 2 days before it reconnected, pure exercise in frustration. I dread hitting the update button or powering off the unit every time. My unit is mounted in an AV rack, not easily accessible to reboot with the power button in the back or run a HDMI cable to a TV. Roon needs to figure out the root causes and come up with a permanent fix. It’s failing the most basic function which is to be able to connect to the network and boot up properly. Also, don’t release updates without testing it thoroughly, especially on your own hardwares. None of my friends running Roon Core on the Mac have this problem. Hindsight I should’ve use a Mac Mini, it would be cheaper and much more reliable than the Nucleus+.
@DN28 I opened Roon remote on iPad today and saw the Nucleus core (my last situation, but could not connect to core) but there was a note added that a software upgrade was required. I clicked to accept update and both the core and remotes accepted Build 1303. All good after that.
@Dennis_Roderick It looks like you had a slightly different issue, your Core was connected to the network, but the Roon App can’t find the Core. My problem was the Nucleus+ Core was unable to reconnect to the network at all after the update. It’s “bricked” until it’s reconnected.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.