Lutron Caséta with Control4: Drivers, Limits and Fixes

Lutron Caséta works with Control4, and the integration is solid once it's set up. Three things decide whether it goes well: which Caséta hub you have, which Control4 driver is doing the talking, and whether the house has outgrown Caséta's limits. Here is each, from Lutron's spec sheets and the documentation inside Control4's own drivers.

You need the PRO hub

Caséta comes with two hubs (Lutron now calls them the Smart Hub; they were the Smart Bridge). The model numbers tell them apart:

L-BDGPRO2-WH: the PRO hub. Lutron's spec sheet gives integration with A/V and control systems to this one only, and Control4 is on Lutron's list of its partners.
L-BDG2-WH: the standard hub. We found no Control4 driver that supports it, and Control4's current driver only discovers the PRO.

If the hub in your rack is the standard one, swapping it for a PRO means pairing the Caséta devices to the new hub again. Worth knowing before the house grows.

Two Control4 drivers, and the one to use

Control4 has written two generations of Caséta driver. Both are in Control4's driver database.

Current: "Lutron LEAP RA2 and Caseta Processor"

Talks to the hub over Lutron's LEAP protocol, encrypted, on ports 8081 and 8083. No telnet.
Paired by running the driver's Start Pairing action and pressing the small black button on the back of the hub.
Needs Control4 OS 3.1.0 or later; more than one Lutron hub in the same project needs OS 3.2 or later.
On OS 4 (X4), it should be on version 12 or later: version 12 fixed the driver's certificates not being kept on OS 4.
It covers Caséta and RA2 Select. It does not cover RadioRA 2, which has its own driver.

Legacy: "Lutron Caseta SmartBridge Pro" and its device drivers

The older set (from 2014–2016) talks telnet, so the PRO hub's telnet support has to be switched on in the Lutron app, and each device is bound by its Lutron integration ID. Plenty of systems still run it. If yours does and it works, there's no emergency, but a system moving to X4 is the natural moment to move to the LEAP driver.

What Control4 can see and do

From the LEAP driver's own documentation:

Lights: dimmers and switches come in as Control4 lights, and the driver mirrors the Lutron rooms into the Control4 project.
Picos become Control4 keypads. Every button press is an event you can program: a Pico by the couch can run a Control4 movie scene, not just its own lights.
Lutron scenes come in as buttons Control4 can press.
Shades: roller shades, and roller shades with tilt. The PRO hub adds Sivoia QS, Triathlon and some Sivoia QS Wireless shades to the Serena shades both hubs run.
Occupancy sensors: reported by group, and Control4 can act on them.
Fan controls: not among the driver's zone types. If a Caséta fan control matters to you, confirm it on your system before counting on it.

The limits

75 devices per hub, the hub counting as one (Lutron's spec; the "50 devices" you'll still read on forums is out of date). Dimmers, switches, plug-ins, Picos and shades all count.
Everything within 30 feet of the hub. Caséta has no repeaters.
One hub is one system. A second hub gives you another 75 devices, and Control4 can run both, but on the Lutron side a Pico paired to one hub can't control lights on the other. Control4 can bridge that gap in its programming; the Lutron app can't.

Things that trip people up

Added a Caséta device and Control4 doesn't show it? Control4 learns about new Lutron devices when its Add Zones, Add Keypads, Add Scenes and Add Occupancy actions are run again. The driver keeps track so nothing is added twice. Set the device up in the Lutron app first.
One Pico shows up twice. A Pico that controls two things, say lights and a shade, comes into Control4 as two Pico drivers. Control4's documentation puts it down to the LEAP API. Program the one you need; it's expected.
The hub was replaced. A new hub means a new pairing, and the driver documentation says a new driver instance. On OS 3.2.0 and 3.2.1 there's a specific order (disconnect before identifying the new one); get it wrong and the driver needs Control4 support to recover.
It all stopped after a router change. The hub needs its network: Lutron's network requirements ask for Bonjour/mDNS and multicast enabled, and QoS and IGMP snooping off. A new router with different defaults is a common cause. Keeping the hub on a reserved address is good practice too. We covered the router case in smart home stopped working after a new router?

When Caséta is the wrong system

Caséta is excellent at what it is: a well-made system a homeowner can set up. In a Control4 house, the reasons people move up to RadioRA 3 are the limits above. RadioRA 3 takes up to 100 devices per processor and 200 per system, has repeaters for range, and offers engraved keypads (Sunnata and seeTouch) instead of Picos alone. Control4 has a separate LEAP driver for it. The trade-off is that RadioRA 3 is programmed with Lutron's dealer software, not the app. We compare the two in RA3 vs Caséta.

If you'd rather it were done for you

Adding the driver, bringing the devices in and tying Picos to Control4 scenes is remote work. Nobody needs to come to the house unless the hub itself has to be swapped. Our prices are per item, not per hour: remote Control4 programming, with prices. Not sure what your Control4 controller can run? The free checker answers in seconds.