Broadlink IR/RF remotes integration (RM3 Mini, RM Pro, RM4 Mini/Pro)

Custom Apps and Drivers
50

I pushed this feature live in v0.9.4. I wanted to post here with some introductory instructions. This documentation will eventually live in the readme.


I use it to configure multiple devices in my setup with a single command call, which makes writing automations simpler.

I also prefer that the sequence itself is edited as a string, which I find faster to iterate on compared to building that same logic in either of the rule or flow execution engines that I use.


All of the previous features still work. You can sendSavedCode and push with a single code name.

The sequence feature is also accessed using push. The string contents define the sequence like this (you must use the whole line, including the sequence: part:

sequence: term=value; term=value; ... ; term=value

  • term can be any of code, delay or repeatN, in any mixture and order.
  • value is:
    • the saved IR or RF code name (for code)
    • number of milliseconds up to 5000 (for delay)
    • a saved IR code name (for repeatN, where you also replace N with the number of repeats of that IR code).
  • You can have as many entries as you want in a given sequence.
    • Use this carefully because once you start executing the sequence it will keep going until it completes.
  • When one sequence is executing the driver won't let you start another one, but there is no limitation on sending a single code while a sequence is executing.
    • This can lead to unexpected behavior, and I would recommend trying to make sure that you don't run any other commands while a sequence is executing.