Lutron Homeworks QS is the industry standard for luxury residential lighting control in high-end private homes, boutique hotels, and premium apartments. Where KNX handles building automation — HVAC, blinds, access control, energy monitoring — Lutron excels at smooth sine-wave dimming of incandescent, halogen, and LED loads with its proprietary phase-adaptive dimming technology. Integrating both systems creates a unified control layer: KNX presence sensors trigger Lutron lighting scenes; Lutron keypad presses change KNX blind positions; a single KNX "Good Night" scene command sets Lutron to 0%, closes KNX blinds, and sets HVAC to sleep mode.

Lutron Homeworks QS system architecture

Homeworks QS runs on the HQP7 (or legacy HQP6) processor — a DIN-rail-mounted Linux computer managing up to 200 dimmers/switches (over 100 circuits per processor with multi-processor expansion). Dimmers (HQD-6D, HQD-12D) are wall-box or DIN-rail mounted Lutron PHASED dimmers with CLEAR CONNECT wireless or HWQS system bus wired communication. HWQS system bus: proprietary Lutron 4-wire RS-485-based bus running at 9600 baud — different from KNX TP. Keypads (HWKP, HQRD) send scene recall commands to the HQP7 processor over HWQS bus. HQP7 exposes an IP interface (Ethernet RJ45, static IP recommended) for: Lutron mobile apps (iOS/Android), integration modules, remote monitoring via Lutron Connect Bridge.

Lutron KNX integration module

Lutron provides a software-based KNX integration (available as add-on licence for HQP7, configured via HW-ACCESS-LINK or similar Lutron integration software). Architecture: HQP7 acts as KNXnet/IP device (tunnelling or routing client) on the same LAN as the KNX IP Router. ETS6 side: no Lutron ETS plug-in required — the HQP7 appears as a virtual KNX device, each Lutron zone/keypad button mapped to a KNX group address. Configuration in Lutron HW-ACCESS-LINK: for each Lutron zone (dimmer circuit): assign a KNX GA for ON/OFF command (DPT 1.001) and a KNX GA for dimmer level (DPT 5.001, 0-100%). For each Lutron keypad button: assign a KNX GA output (DPT 18.001 scene recall, or DPT 1.001 binary) triggered when button pressed. Feedback: HQP7 publishes current dimmer level back to a KNX status GA — enables KNX visualisation (Gira X1, Home Assistant) to display actual Lutron lighting levels.

ETS6 group address structure for Lutron integration

Recommended 3-level address structure for combined Lutron/KNX project: Main group 2 = Lutron Lighting. Sub-group 2/0 = Living room: 2/0/0 = LR dimmer ON/OFF (1-bit), 2/0/1 = LR dimmer level (1-byte), 2/0/2 = LR scene recall (1-byte, DPT 18.001), 2/0/3 = LR dimmer level status feedback (1-byte, read-only). Sub-group 2/1 = Master bedroom: same structure. ETS6 logic: KNX MD-05 motion detector (Schneider Electric Argus 200) presence output (GA 0/1/0) → ETS6 AND function: presence AND time 08:00-22:00 → trigger Lutron scene "Occupied" via GA 2/0/2 DPT 18.001 scene 1. Absence → trigger Lutron scene "Off" via GA 2/0/2 DPT 18.001 scene 0 (with 10min absence delay timer in ETS6 logic block).

Lutron keypad to KNX action mapping

Homeworks QS keypads have button-level KNX output mapping: when a keypad button is pressed, HQP7 generates a KNX telegram on the assigned GA. Example: Living Room keypad button "Dinner" → HQP7 recalls Lutron scene "Dinner" (dining pendant 80%, kitchen 60%, island 40%) AND simultaneously sends KNX telegram to GA 4/0/0 DPT 18.001 scene 5 → KNX ABB jalousie actuator sets blinds to 60% position. Button "Cinema" → recalls Lutron scene "Cinema" (all off except cabinet backlights 10%) AND sends KNX GA 4/0/1 DPT 18.001 scene 8 → blinds fully closed, HVAC setpoint to 21°C via KNX climate actuator GA 3/0/0. This avoids the need for a separate KNX scene controller — Lutron keypads directly orchestrate the full room experience across both systems.

Practical integration challenges

1. IP network stability: Lutron HQP7 connects to KNX via LAN — use a managed switch with VLAN and QoS to prioritise KNX multicast (224.0.23.12) and Lutron traffic. Assign static IP to HQP7 and KNX IP Router. DHCP lease changes cause integration failure requiring reconfiguration. 2. Scene synchronisation: when KNX sends a scene recall to Lutron (via DPT 18.001), Lutron ramps to scene levels over its configured fade time (default 1s, configurable 0.5-600s). KNX actuators respond immediately (< 100ms). If blinds close and Lutron dims simultaneously, visual sequencing may not be perfectly synchronised — program KNX delay timer (2s) before blind command to allow Lutron fade to complete first. 3. Power cycle order: on building startup, energise Lutron HQP7 before KNX IP Router — HQP7 boot takes 45-90s; if KNX broadcasts group addresses before HQP7 is ready, initial state telegrams are missed. Program KNX time delay on initialisation (ETS6 logic: power-on delay 120s before sending startup scene commands).

Testing and documentation

Lutron-KNX integration acceptance testing protocol: 1. From each KNX presence sensor, verify corresponding Lutron scene fires within 2 seconds of occupancy detection. 2. From each Lutron keypad button, verify corresponding KNX group address telegram is received (ETS6 Group Monitor). 3. Test "All Off" master command: KNX group address write → Lutron all zones to 0% AND KNX actuators off, blinds to position 0%. 4. Test dim feedback: verify Lutron zone level change reflects on KNX status GA within 1 second. Documentation: provide Lutron HQP7 project file (.hwp) backup and KNX-to-Lutron GA mapping table to building owner and FM team. Without both files, re-commissioning after HQP7 replacement requires rebuilding both Lutron and KNX configurations from scratch.