I’ve just accidentally deleted my last post 
. Is there anyway to get it back?
Dunno. You were right anyway. Alternatively, if they don’t want to work on the weekend (understandable), don’t break things on Friday or at least mitigate it with a banner if it’s not a terminal issue (like now). It’s not so difficult.
7 Likes
My Roon ROCK can’t enable Chord DAC on updated RoPieee. That’s never been a problem before. Persists after power cycling both ROCK & RoPieee. Disable/enable device fails to fix it
2 Likes
And they put up the banner eventually and are about to fix the issue, it’s already much better now. Kudos for the rather quick fix, and much could have been avoided by an earlier banner 
Apologies if I’ve missed something obvious, but where’s the fix?
The fix is that Home is loading again (and quickly), at least for me and as reported by others. As this thread here had drifted away to complaints about the cloud issue and its handling generally, I thought I should acknowledge that this part is fixed.
The actual topic of this thread, the EA compatibility with the Bridge 2.60 update, might not be fixed AFAICT (but I don’t have any bridges)
Ah, that’s what I was focused on. My bridge is inaccessible after accidentally choosing today to update Ropieee and inadvertently getting the broken update. Really not impressed by the seeming absence of testing on this release.
Indeed. Seems they may have rushed to get this security fix out and forgot about bridge users in EA. (The other stuff with the Home page et al., and the ARC test error, was unrelated to the update according to Vova, just a cloud issue coincidence apparently)
1 Like
@spockfish - I don’t suppose there’s a simple way around this in RoPieee, i.e. a way to downgrade the Bridge back to 1.8 until this mess is sorted by the Roon team? Am presuming not but thought I may as well ask! Thanks 
2 Likes
I’ve got the same issue, running two RPis, one with Ropieee and the other Gentoo Player, and it has happened on both devices, constantly “enabling”. Hoping Roon can fix this pretty quicky!
I don’t think so… a long shot might be that they did not update the downloadable bridge (yet), so that you might receive an old version upon reinstall of RoPieee.
That can be tested rather quickly by choosing ‘Reinstall Roonbridge’ in the advanced menu, but again I think that’s a long shot.
Hi Harry I tried that on DietPi X86 and the new 2.6 version was downloaded. Though interestingly when I did it on the Audalytic RD70 version 1.8 was downloaded
I just tried reinstalling it on Ropieee and 2.6 came down again. That suggests Audalytic downloaded the version and is pointing to a downloaded version.
Thanks Harry - yeah, I gave that a go but sadly no joy. Worth asking
Guess I’ll just have to be patient….but it’s very frustrating to find a perfectly functioning endpoint is completely disabled due to a botched release. I realise EA comes with risks, but I expect at least some testing to be done beforehand.
1 Like
Yeah - but the starting point is to have all your devices on EA or all on Production. Having a mixture is just asking for trouble.
And I realise that the Roon Bridges on Production just upgraded themselves automatically, so this issue popped out of the woodwork.
Still - those of us on EA should expect to take a hit for the team occasionally.
And, this update was apparently made “for security reasons”, so I don’t blame Roon Labs for pushing it out quickly. I expect that they will follow up with something for us on the guinea pigs’ EA builds very soon.
1 Like
How do you put a bridge on EA? I wasn’t aware there was any agency in this?
You can’t - and that’s why this issue has arisen, as I said.
I misunderstood you - I thought you were suggesting I was running a mix of EA / Production wilfully. AFAICT, anyone on EA using bridges will be stuffed by this release if the bridge updates or the user accidentally clicks to update it.
From my perspective this is a straightforward botched release, but I can see there may be a variety of views on this.
1 Like
Even if under time pressure because of the potential security issue, they should have updated EA to work with the updated bridge version, or at least warn EA users. I think that’s clear and it’s difficult to have a different view
2 Likes
Any word on this yet? Or is the roon team taking today off for the holiday in the US?