← Back to Community

Lutron with Control4: Which Systems Work and What You Need

By Ixome · Control4 & Lutron service•6 min read•Published •Updated

Free: what can your Control4 controller still do? →

Control4 doesn't talk to Lutron dimmers one by one. It talks to the Lutron system — the hub, repeater or processor that runs the lights — through a driver in the Control4 project. So the first question is always which Lutron system is in the house, because each one connects a little differently and has its own limits.

A long, warmly lit living room with window walls and a person walking through, trees outside
Illustration

Everything below comes from Lutron's own spec sheets and integration protocol, and from the documentation inside Control4's current drivers.

The short version

Lutron systemWhat Control4 connects toControl4 driverNeedsLutron's own limit
CasétaSmart Hub PRO (L-BDGPRO2-WH) — not the standard hubLutron LEAP RA2 and Caseta ProcessorControl4 OS 3.1.0 or later75 devices, the hub included
RA2 SelectMain repeater (RR-SEL-REP2-BL)The same LEAP driverOS 3.1.0 or later100 devices, repeaters included
RadioRA 2Main repeater (RR-MAIN-REP-WH), network or RS-232Lutron RadioRA2 RepeaterRepeater firmware 9.3 or later100 devices per main repeater
RadioRA 3Processor (RR-PROC3)Lutron LEAP Radio RA3OS 3.1.0 or later100 Type X devices per processor, up to 4 processors
HomeWorks QSProcessor (HQP6-2), networkLutron HomeWorksQS ProcessorOS 2.9 or later99 devices per link, up to 16 processors
HomeWorks QSXProcessor (HQP7-1 or HQP7-2)Lutron Homeworks QSX LEAP ProcessorOS 3.1.0 or laterUp to 16 processors and gateways, 10,000 zones

The newer drivers (Caséta, RA2 Select, RadioRA 3, HomeWorks QSX) use Lutron's LEAP interface. The older ones (RadioRA 2, HomeWorks QS) use Lutron's integration protocol over a network login. All of them are written by Control4.

Caséta and RA2 Select

Caséta only works with Control4 through the PRO hub. Lutron marks A/V integration as a PRO feature; the standard hub doesn't have it. The devices are set up first in the Lutron app, then paired: you start pairing in the Control4 driver and press the button on the back of the hub. Control4 then imports the rooms, dimmers, switches, shades, keypads and Picos, and the hub's scenes.

One thing that surprises people: a Pico that controls two things shows up in Control4 twice. That's how the driver reads it, not a fault. The details, and the fixes for the usual Caséta problems, are in Lutron Caséta with Control4.

RA2 Select uses the same LEAP driver. There is also an older RA2 Select driver that works over telnet; if a house still uses it, telnet has to be switched on in the Lutron app, because it's off by default.

RadioRA 2

Control4 connects to the main repeater over the network or a serial cable. The repeater needs firmware 9.3 or later. The login matters: the default one only lets Control4 send commands, so for two-way control — keypad presses and light levels coming back into Control4 — a telnet login has to be created in the Lutron software. From Lutron software version 13, there is no default login at all; it has to be created.

A RadioRA 2 system can have one main repeater (100 devices) or two with Lutron's larger software package. Control4's driver supports one per project.

RadioRA 3

RadioRA 3 connects through its processor, over LEAP. Pairing uses the button on the processor. Control4 imports the areas, zones, keypads (including Picos, Sunnata and Vierti) and occupancy groups.

Two things worth knowing. After a power cut, it can take up to four minutes before the processor and Control4 are talking again, so a system that "doesn't work" right after the power comes back may just need a few minutes. And updating the Control4 driver requires restarting the Control4 controller.

HomeWorks QS and QSX

HomeWorks QS connects over the network with a login set up in the HomeWorks software. The current Control4 driver replaced an older one from a different developer, and the two must never be in the same project. One processor driver per project.

HomeWorks QSX connects over LEAP, and its driver documentation is candid about the limits:

  • It doesn't support Control4's virtual-button drivers.
  • After any transfer from the Lutron software, the button events Control4 listens for have to be subscribed again. If Control4 programming tied to a Lutron keypad stops working after a lighting change, this is the first thing to check.
  • Occupancy is reported per area, not per sensor.

What Control4 can do with Lutron keypads

On the LEAP systems, Control4 sees each button press, release, hold and multi-tap, and can turn button LEDs on and off. It can't make an LED flash, Picos report only press and release, and there's no ramping from a held button. One rule catches a lot of people: a Lutron button only sends its press to Control4 if that button has something programmed on the Lutron side. A blank button is invisible to Control4.

RadioRA 2 keypads, on the older protocol, do support LED flashing.

Why put Lutron behind Control4 at all

Because each is best at a different job. Control4 is the brain of the house: TV, music, cameras and the app. Lutron is built for one thing: making light behave.

The lights keep working when Control4 doesn't. The Lutron hub or processor runs the lighting on its own. If the Control4 controller fails, is mid-upgrade, or loses the network, every keypad on the wall still works. Lighting is infrastructure; it shouldn't depend on the entertainment system.

Dimming at the low end. LED fixtures behave differently near the bottom of the range — some flicker, some drop out. Lutron lets each dimmer's minimum level be set to match its fixture, so a light fades smoothly to off. It has to be set by eye, in the room, at night, and it's the step most often skipped.

Fade times. One second feels like a switch. Three to five feels like a room changing. A goodnight scene wants longer, so nobody is left in the dark halfway up the stairs.

When Control4's own lighting is enough

Control4 makes its own dimmers, switches and keypads, which talk to the controller wirelessly. For a small number of lights, adding a second system and its hub is hard to justify, and Control4's own lighting does the job. Wiring can decide it too: in a retrofit, what fits in the walls sometimes matters more than what's theoretically better.

And if a house only needs good dimming, shades and a schedule, it may not need Control4 at all. Caséta on its own does a lot, and the owner can set it up in the Lutron app.

Questions to ask before you add either side

  1. "Can you program both?" Lutron's professional systems are programmed in Lutron's own software; Control4 in Composer Pro, which needs a dealer account. Different tools, different logins — a company with one may not have the other.
  2. "Will the lights work with the Control4 controller off?" The answer should be yes.
  3. "When will the low-end trim be set?" At night, after the fixtures are in. If it isn't on the schedule, it won't happen.
  4. "Can I have copies of both project files?" Ask at install time, when it costs nothing.
  5. "Does the Lutron processor have a fixed network address?" A new router moving the Lutron hub to a new address is the most common way a combined house stops working. See Control4 and Lutron have stopped talking to each other.

If you already have both

Most of what makes a combined house good or frustrating is programming, not equipment: which scenes exist, how fast they fade, which system owns which button, whether the trim was ever set. All of that can be changed without buying anything, and most of it can be done remotely. The trim is the exception — that's a visit, best done for the whole house at once.

Not sure which Lutron keypads you have? Lutron keypads: every family and which system it needs tells them apart.

What can your Control4 controller still do?

Three questions: which OS it can reach, whether it will register, and whether it can be done remotely. Free, no signup.