Skip to content

Lutron RadioRA 2 / HomeWorks

Controls Lutron lighting on RadioRA 2, RA3, and HomeWorks QSX systems, addressing lights by their integration id. It reports every level change back.

Network, over the Lutron Integration Protocol on Telnet port 23, with a login and password. Lights are addressed by integration id, taken from the system’s Designer file. The system reports every level change as it happens.

  • Host — the main repeater or processor’s address.
  • Username / password — the integration login (default lutron).
  • Port — default 23.
  • Integration id — the light’s id from the Designer file (managed).
  • Fade seconds — the fade time for level changes.
CommandWhat it does
power_on / power_offTurn a light on or off
set_brightnessSet the level (0–100)
brightness_up / brightness_downStep the level up or down
refreshRe-read current state
rawSend a raw integration command (e.g. OUTPUT,7,1,100)

Because the system pushes updates, level changes made elsewhere are reported back as state.

A processor that will not take the integration login still accepts the connection and then ignores everything sent down it — it does not disconnect, and it sends no error. Nothing about the wire says the lights were not reached.

Where the processor asks for a login a second time, the hub reads that and says so: the device stays connected, its card shows Something’s wrong with the reason, and every command fails with it rather than reporting success. Check the Username and Password here against the integration login set on the processor.

Where a processor answers a bad login some other way, the hub has nothing to read and commands behave as they always have. There is no positive “the login was accepted” signal this driver relies on, because the ready prompt is not spelled the same on every processor family — so a session is treated as fine unless the processor has said otherwise.