Lutron HomeWorks is the lighting and shading backbone of most of the residences we work on. We programme it natively, on Lutron’s own toolchain — no middleware abstraction, no template configuration, no third-party wrapper. The same senior engineer who writes the Crestron system writes the HomeWorks programme, and ties the two together at the scene engine.
For households deciding between a custom HomeWorks programme and a standard Lutron RadioRA / Caséta install, the threshold is usually scale and ambition. RadioRA is excellent for retrofits and houses under about 5,000 sq ft. HomeWorks is the platform when the lighting and shading vocabulary has to match the architecture, the property carries serious electrical scale, or the system has to integrate cleanly with Crestron.
Lutron HomeWorks is a deep platform — processor, dimmers, keypads, sensors, shades, the Designer software, and a scripting layer most installers never touch. Programming it natively means working at every layer, not just the keypad-button mapping that most regional dealers stop at.
One named programmer attached to the residence for the life of the system. The same person writes the lighting scenes, the keypad behaviours, the shading choreography, and the integration logic with Crestron — and returns to refine each as the household’s rhythm changes.
Lighting scenes drawn from the architect’s daylight study, not from a Lutron Designer default template. Astronomical timeclocks tuned to the actual fenestration. Shading layered with solar load. Scene language that survives a principal being away for three months.
Crestron and Lutron exist as two systems on the residence, programmed natively on each platform, and joined at the scene engine rather than at a translation layer. The principal touches one tile; both systems respond as a single intent.
In the residences we work on, Lutron carries the lighting and shading layers and Crestron carries everything else — AV, climate, security, network, AI. The two are designed to behave as one system, but each is programmed by a senior engineer who knows the native toolchain rather than a generalist who treats both as the same platform.
Most failures we see in inherited residences are at the seam between the two platforms. Generic middleware abstracts both systems into a lowest-common-denominator scene language, and the household pays for it every time a scene almost works. The fix is always the same: rewrite each side natively, then re-tie the scene engine at the right layer of abstraction.
The questions that come up most often when households and design teams first encounter native HomeWorks programming.
Caséta is Lutron’s consumer line — excellent for retrofits and homes under about 3,000 sq ft. RadioRA covers most of the residential luxury market in the 3,000–15,000 sq ft range. HomeWorks is the wired platform for the residences where lighting and shading need to be designed as part of the architecture rather than dropped in. More on HomeWorks →
We are an integration practice that programmes Lutron HomeWorks natively. The hardware is typically procured through a Lutron dealer of record on the project; we’re responsible for the programme — the scene language, the keypad behaviours, the integration with Crestron — that lives on top of it.
Yes. Most of the residences we work on carry both. Custom Crestron programming covers the rest of the system; Lutron carries lighting and shading. The two are tied at the scene engine and programmed by the same senior engineer.
Frequently. We audit the existing programme, write a remediation plan, and either work alongside the original installer or take over the engagement entirely. The first survey is usually free; the remediation plan is a paid deliverable that we hand to the household to use however they choose.
North America (California, Texas, Florida, Aspen, the Pacific Northwest), Latin America (Mexico City), Europe (Greece — where Lutron HomeWorks is often the shading backbone), and the Pacific (New Zealand). The senior engineer attached to the residence travels.
Native Lutron HomeWorks support is on the near-term roadmap — the platform reads HomeWorks telemetry the same way it reads Crestron Home today. More on Intuitiv AI →
A short, written brief is enough to begin. We respond personally, within two business days.
Request a consultation → Lutron HomeWorks · Custom Crestron programming · Crestron Home