· None of the above quite fits
· None of these quite match
· Cannot find Production Roon Bridge (v2.6) from EA Roon Server (v2.59 b1625) after the latest RoonBridge update.
· See Diagram
Comments on Above Diagram;
A RED Arrow indicates v2.6 RoonBridge ( One is Arch Linux bese and the other one is RoPieee).
A GREED Arrow indicates EA Roon Server , Arch Linux base.
PS: I posted a similar topic on EA category.
Additional Input.
On Setting/Audio page on EA Roon Server,;
Red Arrow - RoonBridge 2.6 - not working (forever enabling …..)
Green Arrow - RoonBride 1.8 - working
@support - for info, this is being reported by other users (including me). RoonBridge 2.6 is not working with the EA build of Roon Server.
Hello @Osamu_SHIOTANI
Thank you for reaching Roon support. Since the issue is affecting the EA builds, we are moving the thread to the Early Access thread for further review by the QA team.
Sure, Please.
Hi @Osamu_SHIOTANI,
We have identified a compatibility issue between the current Early Access Roon Server (Build 1625) and the newly released Production Roon Bridge (v2.60). This version mismatch is preventing the EA Server from properly initializing the Production Bridge endpoints, which is why they are stuck in the “Enabling…” state.
The good news is that we have already developed a fix for this in the upcoming Early Access build. Once that update is released, your EA Server will be able to communicate correctly with the v2.60 Bridges again.
Please keep an eye out for the next EA release notes!
Good to hear this!!
Good to hear that there is a rapid fix for this. Is there any chance that its release could be prioritised, perhaps as a hotfix? For those of us affected it is very frustrating, as the endpoints are effectively bricked and there’s no way around it short of migrating everything to production.
As an EA user i expect to experience issues that GA users don’t, but i also expect that changes will be pushed through EA BEFORE they go to GA…
Given how long it is taking to publish a new EA release, and the fact that this “security fix” was not published to EA before it went to GA (per your process as far as we understand), it seems safe to assume that this fix skipped EA by design… Perhaps due to some known incompatibility issue between the production fix and the current EA code.
SInce EA users have effectively been “bricked” for 4 days or so, is there an ETA you can share? would it be possible for you to just push the GA version of roon server to the EA branch so EA users can at least use the product again while you work through merging the code?
Hi @dhusky and @Shawn_Kernes,
I completely understand the frustration here—having endpoints not working is obviously not the experience we want for anyone, even in Early Access.
Regarding the release timeline: The team is currently targeting a release for this Friday which includes the fix.
Please note: This is a target, not a guarantee. It is subject to the build passing all necessary QA checks.
If you need your endpoints working immediately and cannot wait for the potential Friday release, the most reliable workaround right now is to migrate your Core back to the Production build, which is fully compatible with the current Bridge version.
Thanks @vadim - I appreciate this additional clarity and acknowledgement of the difficulties, despite the frustration.
Thanks for the update
Correct me if I’m wrong, but regarding the Roon Server, production Release is in 2.6 and Early Bird release is in 2.59…
Should’nt it be the other way around?
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
