I was on 2.0. It was working fine. Roon requested an update. After that I’m back on 1.8 version !
I have created the Data\branches folder with the roon file in it. Content of roon file is production as expected.
Did reinstall all
==> Still on 1.8
I can provide screenshots if needed.
Roon is totally unusable for now.
Please help quickly.
Now using Roon Legacy Remote. When doing about, it does NOT propose to migrate to 2.0.
Seriously such a bug ???
It’s a shame, it’s a lack of testing, a lack of respects of the customers.
Again a such bug and I will resign and go back to Daphile !!!
Very angry customer here.
I hope it will be fixed before Wedsneday !!! (We are Sunday currently)
However, I can connect for WIndows using Roon App even in Wifi.
Seems Roon Remote is also broken
I have used Roon remote on 3 differents machines (2 Chromebook, Galaxy S20+ smartphone) and same problem. It used to work before.
Note: Indexing is still in progress… That may explain why Roon Remote can’t connect but in that case it is a huge bug !
However, I can connect from WIndows using Roon App even in Wifi.
Seems Roon Remote is also broken
I have used Roon remote on 3 differents machines (2 Chromebook, Galaxy S20+ smartphone) and same problem. It used to work before without issue.
Note: Indexing is still in progress… That may explain why Roon Remote can’t connect but in that case it is a huge bug !
Please don’t open multiple support threads on the same topic. I’ve moved your new request into this existing support thread to keep every thing in the same place.
@xxx, sorry for not being accurate. What I tried to say is that it’s not every RoonOS install affected. We are investigating this and have not been able to reproduce it locally.
Sorry to jump in again. Are the logs from the machines any help at all? I’ve seen one user post a log which complained about the branches folder and connection to the room server URL. However the pair has since been moved or deleted, so I am unable to link it directly to you.
I had this problem (ROCK downgraded itself to 1.8)
I fixed it by installing the legacy 1.8 remote, connecting to the core, then going to the settings/about screen - thats what prompted it to update again to 2.0.