Broadlink RM Blaster 1.11.0

This Homebridge plugin has been 100% vibe coded with Claude.

Blast RF and IR signals from Broadlink RM devices using Homebridge. Sends hex codes to a known device IP; this plugin does not autodiscover devices. Codes can be learned interactively via the included broadlink-rm-learner command (see Learning hex codes).

Requirements

• A Broadlink RM device, unlocked using the official Broadlink app
• A fixed IP for the RM device, since the plugin does no autodiscovery

Installation

npm install homebridge-broadlink-rm-blaster
hb-service add homebridge-broadlink-rm-blaster

Features

• Multiple RM devices configure several Broadlink RMs and assign each accessory to whichever one
• Interactive code learning learn codes straight from your remote and add them to your config
• Simple on/off accessories power on/off
• Advanced accessories one press sends multiple signals in sequence, with a configurable timeout between them
• Dimmer lights one signal per discrete brightness level
• Fans speed control, optional swing, extra on/off features (e.g. cooling), and an optional resync switch
• TVs power on/off plus a usable remote in the iOS Remote app
• Temperature/humidity sensor optionally expose sensor data
• ntfy.sh notifications push notification when a RM fails to connect
• MQTT optionally publish sensor data to a broker, and drive fans from MQTT messages
• Fully configurable via the Homebridge Config UI X plugin settings form

Configuration

This plugin can be fully configured from the Homebridge Config UI X plugin settings form.

Learning hex codes

To learn codes straight from a remote and add the resulting accessory to your config, run this in the Homebridge shell:

broadlink-rm-learner

Run broadlink-rm-learner --help for usage details. Advanced Accessories (multiple signals per press) and Fans (speed levels, modes, swing) can be learned too, alongside Simple On/Off Accessories, TVs, and Dimmer Lights. There's also a "just show hex code" option that captures a single signal and prints it for copy/pasting, without saving anything.

Backs up config.json to config.json.backup once per session before writing anything.

MQTT

Enable MQTT in the plugin settings to publish temperature and humidity readings, and to control accessories over MQTT.

Tick "Control via MQTT" on an accessory and give it a topic. It then reads commands from the MQTT base topic followed by that topic and /set, and publishes its own on/off state to the same topic without /set:

| | Topic | | --- | --- | | Commands in | broadlinkrm/bedroom-fan/set | | State out | broadlinkrm/bedroom-fan |

An accessory publishes its state whenever anything about it changes, however that was triggered. State messages use the same keys as the commands below, so whatever an accessory says about itself can be sent straight back to it as a command. A fan reports its speed and swing, a dimmer its level, and everything else just its on/off state. It is retained unless you untick "Retain state messages" on that accessory, so a subscriber connecting later immediately gets the last known state. Commands are JSON, and anything left out is not changed.

Every publish - state messages and sensor readings alike - also carries a last_seen field, similar to zigbee2mqtt. Set the format ("last_seen Format" in the MQTT settings) to ISO 8601 UTC (default), ISO 8601 local time, epoch milliseconds, or disable it entirely. Each RM device can override the format for its own sensor readings.

Simple on/off accessories, advanced accessories and TVs

{ "state": "ON" }

| Key | Values | | --- | --- | | state | ON or OFF |

Dimmer lights

{ "state": "ON", "level": 50 }

| Key | Values | | --- | --- | | state | ON or OFF | | level | 0 to 100 |

Fans

{ "state": "ON", "speed": 100, "swing": "ON" }

| Key | Values | | --- | --- | | state | ON or OFF | | speed | 0 to 100 | | swing | ON or OFF |

{"speed": 50} on its own only changes the speed. "state": "OFF" turns the fan off and ignores the rest of the message. Retained messages are applied when the plugin connects.

A fan only reports speed if it has more than one, and swing if it has a swing signal configured, so a plain on/off fan publishes a plain on/off state. A dimmer keeps its level while off, the same way the Home app does, so an off state still says which level it will come back to.

Debugging

To send a single hex code straight to your RM, bypassing Homebridge/HomeKit entirely run this in the Homebridge shell:

broadlink-rm-blaster <ip> <hexCode>

Run broadlink-rm-blaster --help for usage details.

Credits

Inspired by homebridge-broadlink-rm, built on kiwicam-broadlinkjs-rm for the underlying device communication.

Links

LICENSE · CHANGELOG