Haunted Roon (core downgraded itself to 1.8 overnight)

[Jon_Leonard]

Roon Core Machine

NUC8i5BEH (Core i5)

Networking Gear & Setup Details

Ethernet (EdgeOS router)

Connected Audio Devices

NAD C338, HiFiBerry. WiFi (Netgear WAC540 access point)

Number of Tracks in Library

12,000

Description of Issue

I upgraded to 2.0 shortly after it came out. I had one legacy client that couldn’t run 2.0, so I followed the instructions for 1.8 compatibility (create Roon directory, copy roon_18 into it, rename to roon). That and my other five 2.0 clients (1 Mac, 3 Android, 1 Windows) all worked fine. Until today. Today I wake up and the core had downgraded itself to 1.8 and none of my 2.0 clients could connect. Since nothing can connetc, I can’t access Settings. They correctly identified the core as 1.8, latest versino, and said “update required”. I thought that maybe the legacy client was confusing things so I uninstalled it and restarted the server. No luck. There is no option to upgrade anywhere.

Is there any fix? Or do I just have to do a clean reinstall from a USB device?

[Nepherte (Bart Verhoeven)]

You need to decide first whether you want 2.0 or 1.8 legacy. All your devices need to be on the same version.

If you have a single device that is incompatible and for which you want to use 1.8 legacy, then all devices need to go to 1.8 legacy.

[Jim_F]

You followed the instructions to downgrade your Roon core from Roon 2.0 to Roon 1.8 Legacy. Now, you need to downgrade all of your Roon clients to Roon 1.8 Legacy. Check the Google Play store for Roon Remote 1.8 (Legacy) for all your Android devices. Then, you can deal with downgrading your Mac and Windows PC.

Of course, you could put your Roon core back on Roon 2.0 and just not use the one device that is not capable of running Roon 2.0. Do you really need 5 or 6 Roon clients?

You also can’t use the new Roon ARC mobile app with Roon 1.8 Legacy. Roon ARC requires your Roon core to be on Roon 2.0.

[Jon_Leonard]

I want 2.0. I installed it when it came out. The downgrade happened by itself from one day to the next.

[Jon_Leonard]

Well, no. I followed the instructions for 1.8 compatibility for 2.0. All of my clients except one are 2.0 and had been working fine. 2.0 had been running fine until last week when my core downgraded itself.

[Jim_F]

There is no 1.8 compatibility for 2.0. You have to run Roon 2.0 or Roon 1.8 Legacy. The instructions you followed and posted above are for installing Roon 1.8 Legacy. So, you can stay there or install Roon 2.0. It’s your decision. However, all clients and core need to be on the same version.

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…

Roon 1.8 <-> 2.0 Migration FAQ

[Jon_Leonard]

that’s very interesting since the old 1.8 client and my 2.0 clients worked until last week. i’ll just delete the old 1.8 client and reinstall 2.0.

[Jim_F]

You also need to upgrade your Roon core back to Roon 2.0.

[Jon_Leonard]

yup. got that.

[Jon_Leonard]

ah. just to state what everybody else knew, what i thought were compatibility instructions were downgrade instructions. (duh). happily running on 2.0 now. thanks!

[Jim_F]

So now, you can try to figure out Roon ARC.