I see a couple of oddities happening but the biggest one is that Roon sees two cores. Something called BMGY is running Roon 2.0 and both Nucleus and BMGY are reporting back to Roon’s servers.
I have sent additional commands to your Nucleus and assuming the other instance of RoonOS (BMGY) is deauthorized, Nucleus should correct itself. Please try and access the WebUI for BMGY. Its IP address ends in .5.
I can tell you with certainty that the 192.168.0.5 was online just under an hour ago and reporting to Roon’s servers. This bears 100% relevance to the issue you’re experiencing. However, now it is offline and this should allow an installation to happen properly. Try restarting your core from the WebUI first but if that doesn’t work, a normal update from Roon>Settings>about should do the trick.
Are you by chance using a VPN or behind a firewall? It appears our remote commands did not go through as expected. I can normally run diagnostics on a Nucleus but am meeting roadblocks and limitations I wouldn’t normally see in trying to do so.
Your Nucleus is currently offline and not reporting to Roon. We have yet to receive a response from it yesterday or today. In the last 24 hours we have sent four requests to the unit for diagnostics and only once did it respond. In that case, the moment it did respond it went offline again. Something is keeping it from reaching our update servers because normally we can force an update remotely. In addition to that, the manual attempts of your own have failed.
I will review this with my team today but I suspect a networking issue is the root cause. Perhaps we can come up with a workaround. My only remaining step is to have you wipe the Nucleus but this requires a remote flash of it once you are done and I am concerned that given what we’ve experienced thus far, we’ll meet the same roadblocks.
I’ll let you know what we find in our discussions of your case.