Integrates Lutron HomeWorks QS systems with Control4 directly through the HomeWorks QS processor, with no extra interface. The driver reads the processor's project and creates the ZOOM Universal drivers for every light, shade and keypad on its own, already with the names and rooms from the Lutron project.
Lights (dimmers, panels, GRAFIK Eye, DALI, EcoSystem, 0-10 V and on/off outputs) with level, ramp and real-time feedback.
Shades and shade groups (Sivoia QS) with open, close, stop and position.
Keypads (seeTouch, Palladiom, Architrave, Signature, Hybrid, Tabletop, Pico and contact closure interfaces): every button can trigger Control4 programming, using the names engraved on the buttons.
Keypad LEDs driven by Control4.
Processor buttons (HomeWorks virtual keypads) pressed from Control4 programming, to trigger Lutron system scenes.
Automatic reconnection, with every state refreshed on each reconnection.
Prerequisites
HomeWorks QS processor on the same network as the controller, with a static IP.
An integration login created in the HomeWorks QS software (user and password) and the project transferred to the processor.
Lights, shades and keypads that should show up in Control4 must have an Integration ID in the Lutron project (the HomeWorks QS software creates them automatically).
ZOOM Universal Light, Universal Blind and Universal Keypad drivers available (see Installation).
Installation
Add the ZOOM – Lutron HomeWorks QS Gateway driver in Composer Pro.
Fill in IP Address with the processor IP and Login / Password with the integration login of the HomeWorks QS project.
Once Connection Status = Connected, discovery runs on its own on the first connection (or run Discover Devices).
The Universal drivers are created and connected automatically, each one in the Control4 room named after its area in the Lutron project. Rooms that do not exist yet are created on the same floor as the gateway.
Requirement: the ZoomDH_Universal_Light.c4z, ZoomDH_Universal_Blind.c4z and ZoomDH_Universal_Keypad.c4z drivers must be on the controller. If automatic creation fails, manually add one instance of each type in Composer (this sends the driver to the controller) and run Create Missing Devices.
Discovery
Discovery uses the project's Integration Report, which the processor itself provides. It carries the names of lights, shades and keypads, the areas, the type of each output and the names engraved on the buttons. The source is shown in Report Source.
Automatic (default): leave Integration Report URL blank and the driver fetches the report from the processor.
Report somewhere else: if the processor does not provide the report, put the XML file exported from the HomeWorks QS software on a web server on the network and enter its address in Integration Report URL.
No report: the driver still finds the lights and shade groups through the processor connection, but without names (Output 23, Shade Group 5). In this mode each keypad shows up in Control4 the first time one of its buttons is pressed. Rename them in Composer.
Running discovery again after changing the Lutron project adds whatever is new and updates the connection names, without duplicating or deleting anything.
Supported devices
Lutron project item
Driver created
Notes
Dimmed lighting zone (incandescent, ELV, MLV, LED, DALI, EcoSystem, 0-10 V, GRAFIK Eye)
Up to 10 buttons per keypad, with the engraved names. Press, release and hold events.
Processor buttons (virtual keypads)
—
Pressed with the Press Keypad Button command.
Sensors, HVAC and other items
—
Ignored.
Keypads with more than 10 buttons keep the first 10 in Control4 and are listed in Notes. The other buttons remain available in the Press Keypad Button command.
Names and rooms
Each device is created in the Control4 room named after its Lutron area (or an area above it), with its Lutron project name (e.g. Pendants in room Living Room).
If the room does not exist, the driver creates it on the same floor as the gateway. An existing room with the same name is always reused, even with different capitalization.
With Device Room = Lutron Area (existing rooms only) the driver creates no rooms: anything without a room goes to the gateway's room with the area in front (e.g. Porch Sconces). With Gateway Room, everything goes to the gateway's room that way.
Keypads without their own name in the project use the name of the location they are in (e.g. Entry).
Once created, devices can be renamed and moved freely: the link with the Lutron item does not change.
Keypads and LEDs
Each button pressed on the Lutron keypad triggers the matching Universal Keypad button, which can be used in programming or linked to Control4 scenes and lights.
HomeWorks QS lets integration drive the LEDs: a Universal Keypad button linked to a Control4 device lights the Lutron button LED according to that device's state.
If the HomeWorks QS programming already handles the LEDs, use Control Keypad LEDs = No so Control4 does not interfere.
Picos have no LEDs.
Properties
Property
Description
IP Address
HomeWorks QS processor IP.
Port
Integration port (default 23).
Login / Password
Integration login created in the HomeWorks QS software.
Connection Status
Connection state.
Discovered Devices
Number of lights, shades and keypads found.
Integration Report URL
Blank (default): the report comes from the processor. Fill in only if the report is at another address.
Report Source
Where the last discovery came from and the Lutron project name.
Notes
Discovery warnings (e.g. keypads with more than 10 buttons).
Auto Create Devices
New Only (default): creates only what discovery found for the first time; a driver deleted on purpose does not come back. New and Missing: also recreates missing ones. No: creates nothing on its own.
Auto Discover On Connect
Runs discovery on the first connection if nothing has been discovered yet.
Device Room
Lutron Area (create if missing) (default): room named after the Lutron area, created if missing. Lutron Area (existing rooms only): only rooms that already exist. Gateway Room: everything in the gateway's room.
Control Keypad LEDs
Lets Control4 turn the Lutron keypad LEDs on and off.
Reads the processor's project. Running it again duplicates nothing and adds new items.
Create Missing Devices
Creates any missing Universal drivers.
Refresh All
Refreshes the level of every light and shade.
Reconnect
Reconnects to the processor.
Press Keypad Button
Presses a button of a keypad or of the processor (to test Lutron scenes).
Show Devices
Lists what was found and the drivers created in the Lua log.
Send Command (diagnostics)
For technical support (only with support mode on).
Clear Discovery
Removes every connection and everything discovered (confirm with Yes). The Universal drivers are not deleted.
Commands
Command
Description
Press Keypad Button
Presses and releases (or only presses, or only releases) the chosen button of a keypad or of the processor. The button number is the same as in the Lutron project (for processor buttons, the virtual button number).
Wrong login or password. Check the integration login in the HomeWorks QS software and that the project was transferred.
Report Source = Telnet (no names)
The processor did not provide the report. Export the project XML from the HomeWorks QS software, put it on a web server on the network and enter it in Integration Report URL; then run Discover Devices.
Project item did not show up
It has no Integration ID in the Lutron project, or its type is ignored (see Devices).
Shade showed up as a light
Only happens without the report. Use the report (see Discovery).
Keypad button does not trigger in Control4
Check that the keypad has an Integration ID and that the integration login receives button events.
Universal driver was not created
Driver missing on the controller; see Requirement in Installation.
To investigate, use Log Level = 5 - Trace and Log Mode = Print: all communication shows in Composer's Lua tab.
Licensing
Includes a 720-hour (30-day) trial; remaining time is shown in License Status.
After buying a license, enter the key in License Key. Status changes to Activated.
The controller needs internet access for activation and periodic re-checks.
Once a day, also during the trial, the driver sends the license server technical data about the installation (controller model and version, driver version, project name and license state). No personal data is sent. When a new driver version is available, it shows in License Status.
First release: HomeWorks QS lights, shades, shade groups and keypads found and created automatically with the names and rooms from the Lutron project, keypad LEDs and processor buttons from Control4 programming. Missing Control4 rooms are created automatically.