Introducing RoPieee - A RoonBridge-to-go image for the Raspberry Pi



Hi @spockfish,

I was just thinking, what if Ropieee could also serve as a central place to manage Roon extensions?

At the moment extension installation requires quite a bit of tinkering, making it not suitable for every Roon user. If the web interface of your Ropieee system provides an easy way to install extensions it can be of great value to fill the gap till Roon has an easy way to do it.

Roon extensions require node.js, it should be possible to run this on a RPi. ARM binaries are available here.

What do you think? A good opportunity for a community project?

1 Like

Hi Jan,

The web interface of RoPieee is already node.js, so from a tech perspective that should work.
I’m not sure that I understand you correctly though. I have to admit I did not look that much in the extensions. So… why does these extensions require tinkering?

And yeah, I’ve created RoPieee to make it a community effort. I’ve been preparing stuff on github, so that’s gonna happen soon.

Hi Harry,

Good to hear that node.js is already included and that RoPieee will be on GitHub soon!

Roon extensions currently ‘live’ on GitHub as well. So users have to:

  • Download or clone a repository
  • Install node.js
  • Install Git
  • Run the extension in a certain command window, depending on the used OS
  • Find a way to automatically start it at power-up
  • Repeat the install process in case of updates

So that made me think that if we can build a system for this and include it in RoPieee then extension installation would be much more easy.

In case you’re interested, you can find the discussion about my Alarm Clock extension here.

1 Like

Although the sun is shining over here, I’ve created another update with some small changes:

  • native DSD support for the Amanero Combo384 USB interface
  • show the kernel version in the web interface

For the tech kids: the kernel has been updated to 4.9.25.

As usual these changes are being pulled in automatically somewhere the coming 24 hours. The image on the website has been updated and reflects these changes as well. And on top of that I’ve shaved a few bytes off.

Your feedback is welcome. Enjoy the weekend!



Have been reading through the thread you pointed out. Clear indeed now. Running a Roon Extension is not that trivial.

Adding this to RoPieee is rather simple I guess. What would be nice if we can come up with a kind of convention on how to provide them (on github). RoPieee would then have a ‘register’ of ‘certified’ Roon extensions. With a simple click on the RoPieee interface you can install it then.

Just thinking out loud, with a glass of good Macallan. So maybe this doesn’t make that much sense :wink:

Anyhow, let me know what you think!

Regards Harry

Whilst enyoying my glass of Westmalle triple, i wondered if building extensions into RoPieee does make sense.
Extension should run on the server/core, not on the endpoint, right?

Extensions can basically run anywhere – not necessarily on the core machine.

Crossed my mind as well. But the RoPieee is meant for people that want a simple Raspberry Pi based endpoint, without the need to being a system administrator.

If you looking from it as “the RoPieee is a Roon capable appliance” then the idea of providing plugins in a very easy way could be interesting.

I would guess that once out of beta, there will be an easy way to install extensions from within Roon. Just guessing though.

1 Like

I’m not sure. That would require that Roon provides a runtime (Node.js for example) or something.

Just what I was thinking. Should we create a separate thread for this? I don’t want to pollute your release thread.

The server would be the best option but since there is no community project for this I think that RoPieee is the best alternative at the moment. And as Rene said extensions can run on both, you just have to make sure that your endpoint is active.

Tha depends on the extension. If you’d like to use an extension that requires access to a certain hardware (that could be a connected USB PowerMate or a serial connection to a Hifi component), it won’t work to have that extension running on the core. The only solution to this would be, if every Roon (Server/Bridge/remoteI) instance has it’s own nodejs runtime…

You are right. I was too much focused on my own use case :slight_smile:

Guys, can we start a new thread for the extension discussion? Want to keep this focussed on RoPieee :wink:

I’m working on it…

@spockfish thank you for Ropieee! Running now on my three RAAT endpoints, fantastic!.. Quick and painless to get up and running, set and forget.

Thanks again.

1 Like

I’m wondering in there any possibility to add an AirPlay module to ropieee - sometimes my family members don’t want to use roon and want to just airplay to my IQAudIO DigiAMP+ setup - now I run Volume with Roon installed too which is fine but I rather have something simpler.

I also use dietpi with shairplay but it doesn’t seem to work well as airplay identified setup :frowning:

is there a way to tell from the CLI what version of ropieee is currently installed or perhaps this can be shown in the web interface?

Hi Harry, is integration with Jivelite possible?

I’m looking for a Pi distribution that supports album art on the 7" Pi Touchscreen (like PiCorePlayer does) that also supports DSD512 via the Pi USB port (like DietPi with RoonBridge does)