DO NOT UPDATE Roon Bridge to v1.8 after updating the R30 to its current 5.0 or 5.0.1 firmware!
This breaks the connection to the R30, Roon Rock cannot establish a streaming connection via LAN to the R30!
I got offered a “1.8” version, not the new 2.0 version, but after updating to that, Roon Bridge fails to even run. So: no way to select the R30 as a renderer.
Stay on the previous, still working Roon Bridge version.
Since this post was separated by an admin (sorry for mixing up two topics!) I wanted to share an update: with the help of other users, I found a solution to at least get the Gustard R30 being recognized again by Roon.
Have the R30 running, set it to its „Streaming" input.
Enter r30.local in your browser, that opens R30s configuration screen. Choose the second tab on the bottom, then “Roon Bridge” on the top and hit the reset button.
This will force an interaction with Roon to reinstall a working, compatible Roon Bridge.
I would like to add a interesting observation, though. Interestingly enough, that very reset brought back a working Roon Bridge v1.8 ! That seemed strange, in a way, since the update from 1.7 to 1.8 initially had broken the connection to the R30.
Then, I got offered an update for that very Roon Bridge 1.8 version. No indication, to which version, though. Once I allowed the update, the connection to R30 was broken, again. So I did the “reset Roon Bridge” procedure, again, and ended up with a working 1.8 Roon Bridge version. I disabled automatic updates for Roon Bridge in Roon, to be shure not to loose that working version.
Today, I received an answer from Gustard support, that I would like to share here. As I had assumed, the new .NET10 dependecies play a role.
I had made the Gustard support team aware of this, once the Roon team had announced the new dependencies and requirements some time ago. They have not yet integrated the new dependencies in their firmware.
Here is the full answer to my service request, once my Gustard R30 DAC refrained to work with the Roon Bridge update.
Thank you for the update and for providing the additional context.
The issue occurs because updating Roon Bridge directly through the Roon application replaces the built-in software with Roon’s generic upstream 2.x package. That package requires newer system runtime dependencies (including .NET and specific glibc/OpenSSL libraries) that are not present in the current embedded Linux environment of CelMusperOS 5.0.1. As a result, even though your Roon ROCK server is already running version 2.71 (build 1683), the updated bridge binary cannot initialize on the R30 and immediately enters the “stopped” state.
To ensure stable operation, we recommend the following:
Maintain Roon Bridge Version 1.8:
Continue using the factory-verified Roon Bridge 1.8 restored via the reset function on the r30.local page. This version is fully optimized for CelMusperOS and communicates seamlessly with Roon Server / ROCK 2.71, delivering bit-perfect streaming and full audio performance without any compromise in sound quality or playback capability.
Avoid Updating Roon Bridge via Roon:
Please ignore the update prompt for the R30 within Roon and do not update Roon Bridge from the Roon interface.
Future Firmware Updates:
Because the network streamer runs on a dedicated embedded system, any updates to the internal streaming components—including bridge runtime environments—are adapted, tested, and integrated directly into CelMusperOS by our engineering team. These updates will be delivered through official CelMusperOS OTA releases.