Roon IR Remote bridge using FLIRC

Hi everybody,

The Project at

I’ve started a project in Github that provides the code for a Roon IR bridge that turns received IR events from a FLIRC USB device into commands that are sent to the Roon Core using Roon API The solution can for instance be deployed to a RaspberryPI running Roon Bridge. Using a configuration file one will be able to map key codes to Roon transport commands (play, pause, stop, fwd, prev).
The solution can be easily deployed using Ansible to any node running a Linux system providing a systemd interface and supports Python3. The project isn’t in its final state yet but survives restarts and several days uptime without any notice of instability.

Use Case

What I’m using it for? For me the use case was to integrate a Raspberry PI wearing a DAC hat from Hifiberry into my Harmony setup. Volume buttons are ignored by the IR bridge and received by the amplifier while the transport commands from the harmony remote are translated into Roon transport commands right away.

Extended Use Case

Using the same solution we could map different IR-based remote controls mapped using a programmable FLIRC and python code that maps those commands to different Roon zones.


I need some early adopters in order to test such a solution. We could even make it run on a Raspberry PI zero with display and knobs and IR receiver so that we end up with a cheap remote control for each zone we’re sitting in.
I have always thought about that because of the fact that taking the mobile out of the pocket and waiting for the Roon App to wake up while looking for the core takes ages. A cheap remote solution could be available instantly instead when someone would like to just skip the track.

Link to Github Project


Please share a link to your repo

I’ve updated the page above. Thanks for your interest. Please respond if something isn’t crystal clear or behave differently from what you expect.

I’m confused. Is this different from the RoPieee remote control extension?

My exact thoughts. Ropieee allready works perfectly with flirc, how is this any different?

I’m not using Roopie and like to be independent from any distro for the PI or any other device running Roon Bridge. So this solution can be deployed to any device running Linux. So I was interesting to have something more independent solution. And that gives me the chance to implement some desired features like Audio response based on text-to-speech for those systems where no display is attached. So once I mark a file as “favorite” I will get a response through the same ALSA channel based on Amazon Polly speech engine. See it both as an experiment that is not bound to any distribution.

1 Like