IR Bridge 1.0.0 for RoonPilot 2.0.2. The official firmware and Bridge Web Installer are available. Existing paired Bridges can be updated from RoonPilot; installation is always manual.

Optional hardware extension

Let the knob control the hardware.

RoonPilot IR Bridge adds learned infrared volume, mute and power control to any selected Roon zone—without modifying RoonPilot or installing another service.

Watch the installation video
  • Per-zone Roon or IR routing
  • Up to four saved Bridges, including parallel group routes
  • Encrypted BLE with Wi-Fi fallback
  • Learned profiles and signed A/B updates
Encrypted BLE
Learned IR
Wi-Fi fallback

01

One turn. The right control path.

Each zone decides independently whether Roon or the Bridge receives its commands.

RoonPilot

The rotary ring, touch controls and zone settings remain the single user interface.

IR Bridge

Receives the action for its assigned zone or group member, schedules the learned frames and drives the transmitter.

Audio hardware

Your DAC, amplifier or active speaker sees the same command as from its original remote.

RME ADI-2 DACVOL
−31.0 dB
AUTO REF LEVEL ACTIVE

A practical example

Keep RME Auto Ref Level where it belongs: inside the DAC.

For an RME ADI-2 DAC connected to a WiiM zone, RoonPilot can send the original RME infrared volume commands instead of changing Roon’s digital volume. The DAC therefore performs the level change itself and retains its Auto Ref Level behaviour.

  • Two learned 0.5 dB increments can form one precise 1.0 dB encoder step
  • Optional mute and separate short/long press power actions
  • No guessed absolute value is shown for an IR-only volume path
  • Native Roon control remains available for every other zone

02

Modern transport. Familiar infrared.

The Bridge stays simple at the equipment rack while RoonPilot manages setup, profiles, routing and updates.

Pair once

Every Factory installation creates a unique RPB-… identity. Select it deliberately in RoonPilot to confirm the first encrypted pairing.

Learn the original remote

RoonPilot guides the recording of volume, mute and separate power actions. Known protocols are analysed; unknown signals retain their raw timing.

Reach another room

BLE is preferred nearby. If enabled and BLE becomes unavailable, authenticated local Wi-Fi takes over automatically and returns control to BLE when it recovers.

Completely optional means completely off.

When Bridge & Bluetooth is disabled in RoonPilot, Bluetooth, scanning, Bridge update checks and all Bridge background work remain off after restart.

03

RoonPilot is the entire control centre.

The Bridge needs no separate app, web interface, cloud account or background service. From the first pairing to a signed firmware update, every normal task is managed from RoonPilot.

Close-range trust. Whole-home reach.

Pair securely over Bluetooth. Add Wi-Fi only when the room demands it.

Initial setup always begins nearby over Bluetooth LE. RoonPilot scans for the factory-generated RPB-… identity, asks you to select the intended unit and establishes an encrypted, bonded connection. That deliberate first contact is the trust anchor for everything that follows.

Allow Wi-Fi fallback is an explicit, optional second step. While the trusted BLE link is active, RoonPilot sends the current 2.4 GHz network details and a newly generated 256-bit application key to the Bridge. BLE stays preferred. Confirmed BLE trouble can move control to authenticated local Wi-Fi; RoonPilot returns to BLE only after reliability checks, not after one good signal reading.

One RoonPilot can remember up to four Bridges. In normal Automatic zone control, the selected zone determines the required IR routes. For a Roon group, RoonPilot monitors and operates every Bridge assigned to its physical members. Manage may temporarily administer another Bridge over BLE while active zone or group routes continue over verified Wi-Fi. There is at most one BLE link but multiple independently authenticated Wi-Fi paths.

For multiple Bridges, a single IR receiver on one learning Bridge is enough. It captures profiles for every zone; RoonPilot stores them permanently and later deploys them even to target Bridges without receivers.

The Bridge page follows RoonPilot's global English/German setting. Roon metadata, physical RPB-… identities and names entered by the user remain unchanged.

Nothing is exposed to the internet: transport choice, connection health, signal strength and recovery remain visible and testable from the same RoonPilot page.

RoonPilot Bridge status showing enabled Bluetooth, optional Wi-Fi fallback, encrypted bonding and live transport information
One status surface shows the master switch, preferred BLE path, optional Wi-Fi fallback, identity, firmware, signal and security state.
The selected Roon zone determines the target Bridge and IR profile
The route stays exact. Manage does not change it; the current radio path may be BLE or authenticated Wi-Fi.
Two saved Bridges and only one heard in the last BLE scan
Saved is not the same as found. “1 found” describes only the last BLE scan. The other paired Bridge may still work over Wi-Fi; scan again after it returns to BLE range. Open full-size diagram.
01

Find and pair

Scan nearby Bridges, compare the unique identity and complete encrypted bonding without opening the enclosure.

02

Learn and verify

Create named equipment profiles, record every command twice, inspect recognised protocol data and test the real hardware immediately.

03

Route per zone

Mix native Roon volume, external IR volume and deliberately disabled control across different zones, each with its own encoder step and optional Power/Mute buttons.

04

Protect the work

Save settings, routes and each named IR profile once, with separate Bridge assignments. Restore a profile to a paired replacement Bridge or share it across several Bridges.

RoonPilot Bluetooth pairing screen with a dummy Bridge identity
Deliberate BLE pairing. The factory identity is visible before an encrypted bond is accepted.
RoonPilot profile library with a fictional named IR profile and learning Bridge selector
Profiles on RoonPilot. A Bridge with a receiver is needed only for learning; the saved profile may later control other Bridges.
RoonPilot per-zone volume routing screen with dummy Roon zones
Independent routing for every zone. Roon, external IR or disabled volume can coexist in one RoonPilot installation.
RoonPilot System page for creating one controller and Bridge backup
One backup for the complete setup. Controller settings, zone routes, the permanent named IR profile library and separate assignments are saved in a single JSON file. Offline Bridges trigger an explicit warning.
RoonPilot signed online update management for the IR Bridge
Bridge updates without another USB session. RoonPilot finds, verifies, transfers and confirms signed releases; installation remains manual.
Four steps from a RoonPilot library profile to automatic deployment on a target Bridge
Learning and target Bridges are independent. One profile may later be assigned to several Bridges. Open full-size diagram.
A Roon group using native numeric volume, native dB volume and an infrared Bridge at the same time
Roon groups keep every physical route. One turn may combine native values and several Bridges. Outage and recovery are tracked per required Bridge; healthy members continue. Open full-size diagram.
All required Bridges

Automatic control follows every IR member of the selected Roon group, not only its lead output.

Parallel local paths

A nearby Bridge can use BLE while other group members use authenticated Wi-Fi.

No silent rerouting

An offline Bridge marks its own route unavailable and never borrows another member's profile.

Quiet recovery

Failures and reconnections are reported per Bridge without flooding the display or event log.

Responsive RoonPilot Bridge management page on a phone-sized screen

The same local interface, anywhere at home

Configure at the rack or from a phone.

The responsive Bridge page is served by RoonPilot itself. It lets you inspect the active transport and manage the complete extension from a desktop, tablet or phone connected to the local network. The Bridge remains an appliance beside the audio hardware—RoonPilot remains the product you operate.

See every management step in the guide

No cloud. No daemon. No extra computer.

Commands remain on the local network. The Bridge is a small hardware companion, not another service to maintain.

04

Compact hardware, clearly defined.

The target build uses a small ESP32-S3 board, an infrared receiver for learning and a dedicated transmitter for reliable range.

Controller
Waveshare ESP32-S3-Zero · USB powered · no battery
IR receiver
AZ-Delivery KY-022-compatible receiver module · signal on GPIO5
IR transmitter
Adafruit High Power Infrared LED Emitter · product 5639 · signal on GPIO4
Status light
Onboard RGB LED · complete signal table
Firmware
ESP-IDF 6.0.3 · signed A/B OTA · persistent identity and profiles
Compact white printed enclosure for the RoonPilot IR Bridge beside a one-euro coin
The one-euro coin is shown only as a size reference; keep both infrared apertures unobstructed.

The supported transmitter is the Adafruit High Power Infrared LED Emitter 5639. Verify reach, emitter direction and enclosure temperature in the physical installation; reflective rooms and hidden placement can change infrared reliability.

Adafruit IR transmitter Official Waveshare board documentation AZ-Delivery IR receiver Controller board listing

05

Every IR Bridge light signal at a glance.

The small RGB LED is on the ESP32-S3-Zero. It remains off during normal operation; RoonPilot's Bridge page provides the ongoing connection status.

LED patternMeaning and required action
OffNormal operation. A dark LED does not mean the Bridge is powered off or disconnected.
Slowly pulsing blueA pairing window is open; the Bridge can be found and deliberately paired in RoonPilot.
Two short blue flashesThe encrypted pairing completed successfully.
Repeated short blue pulses for about 1.5 secondsIdentify Bridge was requested in RoonPilot.
Pulsing orangeThe learning Bridge is waiting for or recording an IR signal. Normal IR transmission is blocked while learning.
Two short green flashesTwo matching IR captures were stored. After pulsing violet, green means the firmware was accepted and restart follows.
Two short red flashesIR learning failed or timed out. After pulsing violet, red means firmware transfer or verification failed.
Pulsing violetFirmware is being transferred or verified. Never remove power.

07

From bare board to a routed zone.

Initial USB installation is separate; everyday configuration then happens entirely through RoonPilot.

  1. 1

    Wire and inspect

    Connect the receiver, sender and a shared ground using the verified pin map.

  2. 2

    Install Factory

    Use desktop Chrome or Edge. Factory installation erases Bridge identity, pairing and profiles.

  3. 3

    Pair by BLE

    Enable Bridge & Bluetooth, start pairing and confirm the displayed RPB identity.

  4. 4

    Learn a profile

    Use any receiver-equipped learning Bridge; the eventual target Bridge does not need a receiver.

  5. 5

    Route the zone

    Select IR in Zone Management and choose its independent encoder step count.

  6. 6

    Back up and update

    Create one combined setup backup, then install future signed updates directly from RoonPilot.

08

Updates managed by RoonPilot.

Installed and available versions appear on the Bridge page and, when enabled, as a dismissible notice on the device.

DiscoveryAutomatic
InstallationAlways manual
VerificationRSA-3072 + SHA-256
RecoveryA/B rollback

Two independent checks

Verified before and after transfer.

Understand Bridge updates

No unattended installation: RoonPilot may check for a new Bridge version and show a notice, but download and installation start only after explicit confirmation.

  1. 1
    RoonPilot validates

    HTTPS manifest, project, board, protocol, controller version, file size, embedded version and SHA-256 are checked first.

  2. 2
    Bridge validates again

    The Bridge verifies block order, size, SHA-256 and the RSA signature before selecting the inactive OTA partition.

  3. 3
    Version confirms success

    After restart, RoonPilot waits until the Bridge reconnects and reports the exact requested version.