Starting 6th March, after a Roon update happened, I am no longer able to connect to my Roon core (hosted on the Rockna Wavedream NET server) by using my Android smartphone Roon remote or my Apple iPad Roon remote anymore. The only way I am able to connect is from a PC (Windows X64), but even then, even if I can access my local files and stream the Qobuz playlists that I saved, I cannot see any new releases or search for any album/artist/track in Qobuz from Roon. Also, I cannot access any of the favorite radio stations that I have saved (or from the radio stations' list), and I do get a message to check my internet connection (but again, I can play tracks from the the Qobuz playlists I have saved favorites)
Please note that I am not using any firewalls on either my Android smartphone or iPad, neither on my PC and have restarted several times my router, switch and Roon core in this order). I was able to connect 1 out of 2 times from my Android smartphone only once to the Roon core...after that, if Roon app went on sleep, it lost the connection. I have left the beta for the Roon remote on my phone, but not sure if that was supposed to make any difference. My Roon core runs the 2.0 (build 1378) earlyaccess version, while my Android phone runs the 2.0 version (build 1378 production). My core is getting an error message that it cannot check for newer versions, while it's streaming from Qobuz playlists...
Please make sure that your server and remotes use the same release channel (all on production or all on early-access). To resolve connection issues potentially introduced with the latest releases see also:
You should probably inform the manufacturer (Rockna) about the issue so they can update the firmware of their product. More information can be found in the thread below:
Thanks for the warm welcome and very useful info provided below, @BlackJack, appreciate it!
Funny, I though both server and remote should update more or less the same time, but apparently the server update never happened and was left behind, using the 1379 versions vs the 1382 of the remote. Will read through the topics below and contact Rockna, eventually. Thanks!
Well, joining the Beta was my decision, indeed - but never expected remote and core not to update the same time, so not sure how I could have caused this mismatch when updates should happen simultaneously??
Even the numbering convention is super confusing. How can a 1379 earlyaccess be a Beta, while 1382 to be a production? Wasn’t it supposed to be the other way round, newer versions to be the Beta? Or maybe this is due to my core not updating…
Nevertheless: I have rejoined Beta in Google PlayStore, but I still can only get the 1382, despite the Roon Remote (Beta) being flagged as Beta in PlayStore…while my Roon core stays stuck with 1379 -earlyaccess.
My question is: how can I upgrade the Core to 1382 stable now, or how can I downgrade my Roon emote to 1379 - earlyaccess to make it work with my Core?
The problem is now fixed by manually upgrading the Rockna NET FW to the latest 15th Feb version, thanks!
It had nothing to do with the different versions of software for the Core and Remote apparently, but with Roon’s update that messed up everything…
Luckily, Rockna was ahead of the curve and released a new FW before these updates/changes, it’s just that I had to manually update my core
