How to run Roon 1.8 Legacy on Nucleus?

[Stuart_Dudman]

I was busy yesterday so missed the “Big Leap Backwards” information. Thus my iOS devices upgraded overnight. But Roon on my Nucleus is still 1.8. I’ve installed the Legacy 1.8 remote on one iPad but it still doesn’t connect. See photo

Looking at this forum, it seems like 2.0 isn’t ready to be released. And I don’t need to play Roon elsewhere.

Add im

ages

What is my next step to return to 1.8? Thanks 

[DanielAvasilichioaei]

Roon 1.8 Legacy - How to stick with Roon 1.8

Roon 2.0 is here, and with it comes some exciting new updates to the Roon platform - including Roon ARC, our mobile app for remote listening - free and exclusive for Roon users. However, we know not everyone will want to - or will have the capacity to - upgrade to Roon 2.0 straight away. We know some users will want or need to ‘hang back’ from 2.0, at least for a little while. So alongside Roon 2.0, we’re also giving users the option of sticking with Roon 1.8 - should they choose to. In this p…

[Formula]

Basically your core is on a stable production release. You need to change/downgrade to 1.8 legacy.

Roon 1.8 <-> 2.0 Migration FAQ

[Stuart_Dudman]

I don’t think this is what I’m after. Core is 1.8. Remote is 1.8. But they don’t see each other.
I presume I’m missing some kind of subtlety.
Do I need to reboot something?

[Formula]

I believe your Nucleus needs to be 1.8 LEGACY now going by what the guide says. From your screenshot it’s 1.8 stable. If you want to stay on 1.8 they all need to be on the legacy version and, not on the 1.8 stable release version.

[Stuart_Dudman]

Surely not. I never asked for this update. I just want to be where I was last night.
Can I not load Roon Remote 1.8 (not legacy) and all will be well?
There must be a fiddle.
I’m dealing with a bereavement and just don’t have time to play around for hours.
But music would be very welcome right now. Somehow someone in Roon has made it impossible for me to play music.

[Stuart_Dudman]

Could I politely suggest you roll everybody back to 1.8
Then send out a message about 2.0 with a week’s notice so that we can all switch off updates, upgrade OS etc.
This has seemingly done without any thought or planning.

[Formula]

It seems that Apple and their auto app update has caused you this problem. Not Roon. Simply disabling auto app updates would be wise for all software/app to avoid situations like these.

I’m sorry you’ve got this going on now with everything that is happening. But, Roon did communicate and there are posts and guides in the FAQ.

Others have had the same issue and they have fixed it by downloading the legacy version.
See here:

Going back to 1.8 without success

Against my better instincts I updated my remote (iOS) to roon 2.0 this evening, only to discover that my core, an onlder macmini, does not support roon 2.0. I then installed the roon 1.8 legacy remote (build 1126) but the legacy remote now cannot connect to my core because it says they are running different versions. Core is on 1.8 (build 1105) while tablet/remote is build 1126. Frustrating, roon has been working great for me for years but with this new version I may end up looking for a diff…

Take some time out and come back to this when you’re ready. And, remember to the the guide!!

[Thomas_Forster (Tom)]

Please try rebooting your NUC. It worked for me and others.

[Stuart_Dudman]

Now the nucleus sorts of flickers on the remote.
I give up. I’ll upgrade to 2.0
How do I upgrade the Nucleus given that I can’t access it from my remote?

[Stuart_Dudman]

I’ve gone to web access, but that doesn’t give me the option to upgrade to 2.0.

[PRE (Peter)]

I was talking to others in posts about the 1.8 issue on Macs 10.14 or earlier. I downloaded the Roon Core 1.8 Legacy build 1126 app. I first installed the Legacy 1.8 iOS app on my iPhone and iPad. Then I closed out of Roon on my iMac core. Installed Legacy 1.8. Only took about 2 minutes to fully open. Worked OK and my remotes with Legacy 1.8 app connected. Seems like all OK. But Wow, Roon could have done a much better job communicating on this situation. Hope this helps.