Lutron HomeWorks · design and programming

Lutron HomeWorks, written for the residence.

Lutron HomeWorks is the platform we reach for when a residence’s lighting and shading have to be designed at the architectural level — not configured from a Lutron Designer template. Keypads composed for the room they live in. Astronomical timeclocks tuned to the actual fenestration. Scene language that reads as one vocabulary across every elevation of the house.

We design and programme HomeWorks natively, on Lutron’s own toolchain, by the senior engineer attached to the residence. The hardware is procured through a Lutron dealer of record on the project; the design and the programme are ours, and stay ours for the life of the system.

What HomeWorks actually carries.

HomeWorks is Lutron’s wired flagship platform — the system the architects and design teams we work with reach for when the residence’s lighting and shading have to be part of the architecture rather than dropped into it after.

i.

Lighting design.

Dimmers, drivers, low-voltage relays. Fixture-by-fixture circuit design from the architect’s reflected ceiling plans. Astronomical scenes for sunrise / sunset / civil twilight, tuned to the residence’s actual fenestration rather than a generic latitude default.

ii.

Shading choreography.

Sivoia roller shades, drapery tracks, Palladiom hardware. Shade positions layered against solar gain on each elevation; scene language that knows when to bias toward view and when toward thermal load. Rolled with the architectural palette and the room’s daylight study.

iii.

Keypad vocabulary.

Keypads composed for the wall they live on — the typography, the engraving language, the button order. Behaviours written so the principal never has to learn which button does what; the wall reads as the room does. Custom engraving paired with the project’s typeface where the project warrants it.

How HomeWorks programming differs from a Designer-template install.

Lutron HomeWorks ships with Designer, the manufacturer’s configuration software, and most regional dealers stop there: a template-based scene layout that gets the lights on and the shades moving. That is enough for a competent installation. It is not what a serious design team is looking for.

Native HomeWorks programming — the kind this practice does — works below the Designer layer. Scene scripts written by hand. Conditional logic against time, occupancy, solar load, and household pattern. Keypad behaviours that change based on context (a long-press in the morning does one thing, a long-press in the evening does another). Tie-ins to Crestron at the scene engine, not at a translation layer. The system the household actually lives with is the layer above Designer, not Designer itself.

Most failures we see in inherited HomeWorks systems are at this layer: a Designer-template install that gets to about 70% of the household’s actual needs and stalls. The fix is to rewrite the scene engine natively against the way the residence is used. The hardware in the wall almost never changes; the programme above it does.

Common questions about HomeWorks.

The questions that come up most often when households and design teams first encounter native HomeWorks programming.

When is HomeWorks the right platform?

When the residence is being built or renovated to a standard where lighting and shading are part of the architectural design (rather than added after), the property carries serious electrical scale, or the system needs to integrate cleanly with Crestron. Below that threshold, Lutron RadioRA is usually the better answer.

Can HomeWorks pair with Crestron?

Yes — this is the normal pairing in the residences we work on. Crestron carries AV, climate, security, network, and the AI layer; HomeWorks carries lighting and shading. The two are joined at the scene engine, with a single vocabulary the household touches on the wall panel and the app.

How long does a HomeWorks programme take to write?

From schematic design through commissioning, the lighting and shading programme tracks the building’s timeline. The active programming phase is typically 8–16 weeks for a residence of moderate scope, with refinement visits over the following season as the household’s rhythm settles.

Will the household have to learn anything?

Ideally, no. The wall panels and keypads are composed so a household member — or a guest — can use them on instinct. We commission with the household present, refining keypad order and scene names against how the residence is actually used.

What happens at handover?

A senior engineer is on site through commissioning and stays for the first season of operation. The system is fully documented — scene tables, keypad maps, override paths — and handed to the household and to the on-site facilities manager (where one exists).

Can you take over an existing HomeWorks system?

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.

Begin a conversation.

A short, written brief is enough to begin. We respond personally, within two business days.

Request a consultation Lutron programming · Custom Crestron programming · Crestron Home