Roon Bridge on DietPI: impossible to update from build 164 to 167 [Resolved by Dan_Knight (DietPi Creator)]

Just to be clear, we’re not currently aware of any general issues with updating Roon Bridge, and the most recent release was Core only (no mobile updates, no updates for Roon Bridge), so there was no update last week.

My understanding is that there was an issue with updating on DietPi, and Dan is on it. In the world of software, it’s doesn’t get a lot better than “the bug is fixed in our current beta and will go live with the next release”, so I think you just need to be patient on this one.

Also note that there have been very few changes in Roon Bridge over the last few months, if any.

1 Like

The issue is with DietPI, not Roon. Allo products running DietPi are impacted.
This is not really a problem as Roon Bridge works well even without the latest update.
Also Dan sais DietPi will be fixed in the next days.
So let’s all wait, then update our devices through All Web Interface or dietpi-update, and all will be good!
Thanks again @Dan_Knight

1 Like

Hi All,

To clear this up the issue is with DietPi, not Roon.

In our attempt to improve security on users systems, we rolled out the RoonBridge service with its own user “roon”, which had access to audio and DietPi groups for userdata only.
This works fine as an endpoint, however, the remote update will fail, due to insufficient permissions available to update the RoonBridge binary.

I apologise for this.

This is fixed in v6.18 by allowing root access to the RoonBridge service, required for updates.
The release has been delayed longer than expected, due to RL priorities and extended beta testing.

v6.18 will be released this weekend.

In regards to Allo images, the issues with O!MPD are also resolved in v6.18:


If you are having an issue, outside of O!MPD with the Allo GUI images, please email me directly daniel.knight@dietpi.com and I will investigate.

3 Likes

Thank you Mike! A clear, concise response that gets to the point. I will (continue) to wait for the bug fix. Patience? Hmm. Not my forte. :slight_smile: My best to you.

I am just happy to have an OS that suits my Roon needs, available free. I have been threatening to send a donation to DietPI, I will really do it this time.

1 Like

Hi all,

DietPi v6.18 is now live. You can update the system with:

dietpi-update

Release info:

1 Like

Update worked great. Now running 6.18.14. Thanks Dan.

Worked for me too! Thanks
Gerald

I’ve waited quite a while before asking again. Is there no fix in sight for the failed Roon Bridge update? This is getting quite frustrating.I was under the impression (you, Roon) were working on a solution?

Update your diet pi this was fixed a couple of weeks back and was a diet pi issue not roon’s

We’ve covered this. They can’t be manually updated unless I travel to Phoenix and Houston. This is getting ridiculous… no one knows what’s going on? I thought Roon had “there ‘stuff’ together”?

It’s a problem with Dietpi. There is a Dietpi-section in this forum. Ask there.

It appears I won’t be recommending Roon ever again. This is ridiculous. “Go look in another forum”? That will solve the issue in locations I can’t get to?

There is a Dietpi section on this forum. Ask your question there.

Hi @Neil_Small — Thank you for the follow up here regarding “RoonBridge” running on your Diet Pi and the issue you are currently experiencing.

I wanted to touch base because I see that you had been engaged not only by the Roon support team here but also Dan Knight as well, who offered a way to update the Pi as requested. I can see that others have taken the update and they seem satisfied with the results. Have you given Dan’s instructions a go yet?

Also, just to echo what Mike had mentioned in his response to you in that thread. The last release was a core update only so any Roon bridge devices should not have been affected by the update in any way.

Thanks!
-Eric

I see now! This must be a rogue chatbot that has latched on to the forum, as a real user would have read the responses and fixed their problem by now.

1 Like

Is Build 164 not working for you? What feature in 167 are you seeking? Getting the update will change nothing except you won’t see that message "Checking for an update? And for the hundredth time THIS IS NOT AN ISSUE WITH ROON. The device you have chosen to use utilizes DietPi. The issue is with DietPi so if you are never going to recommend something again it should be devices running DietPi.

It appears my only solution is to order 5 new SD cards (I’ve done 5 installs out side of mine), and build new images for each person I configured DietPi and Roon Bridge. This isn’t what I had in mind when I convinced friends (and friends of friends) to use Roon. Fingers crossed they will be able to swap the SD card with no damage. These people don’t have a clue how the Pi works - they trusted me to do this. Aye carumba.

What’s the problem you’re trying to solve?

If it’s simply replicating one install 5x then use fsarchiver to back up the install and write it out to each SD card. Simple.

Pi solutions are really aimed at the hobbyist and distributing them to non-technical people is a bit off centre.
If you want to keep using Pi based end points then RoPieee might be a better solution for the use you are describing as it self updates.

1 Like