Lutron Motor Shade
A third-party blind on a Lutron motor module, shown and controlled as a normal Control4 shade.
£ 249.00
£ 249.00
Invalid email
Lutron Motor Shade
A third-party blind on a Lutron motor module, shown and controlled as a normal Control4 shade.
On a HomeWorks QSX processor, Add Zones allocates a Lutron LEAP DRPM Motor driver for each motor zone. That driver moves the blind correctly, but it presents a private proxy, so the blind never appears as a shade in the Control4 app or on a touchscreen.
This driver supplies the missing blind proxy and forwards open, close and stop to that motor driver, which keeps doing all the Lutron communication. It never speaks LEAP itself, opens no connection and holds no credentials. One instance per blind, alongside the motor driver already in the project.
There is no position slider, and that is deliberate. The Lutron motor module ignores levels between 1 and 99 % and reports no position at all, so a slider would be a fiction. The tile shows open or closed, and a stop mid-travel is estimated from the measured travel time.
- A shade the client can see
- The blind gets Control4's blind proxy, so it appears as a shade in the Control4 app and on touchscreens, and works in programming like any other.
- Finds the motor driver for you
- Find Motor Drivers lists every Lutron LEAP DRPM Motor driver in the project with its Control4 device ID, room and name, and Motor Link Status says plainly when the field has been given a LEAP address instead.
- Stops before it reverses
- A change of direction mid-travel stops the motor, waits for it to settle and only then drives the other way, rather than reversing a running motor.
- Direction fixed in software
- If Open closes the blind, Invert Direction swaps them. No rewiring.
- Resync without moving
- Set State to Open or Closed corrects the tile without moving the blind, for when somebody has used a Lutron keypad.
- Commissioning tools
- Raw test actions prove the link to the motor driver before direction matters, and Print Diagnostics shows the resolved device ID, the command each direction sends and the current level.
| Hardware | Third-party blind on a Lutron LQSE-4M-120-D DIN rail power module motor zone |
|---|---|
| Manufacturer | Lutron |
| Processor | Lutron HomeWorks QSX |
| Works with | The Lutron LEAP DRPM Motor driver allocated by the QSX processor's Add Zones, which stays in the project |
| Control | Open, close and stop. No intermediate positions |
| Transport | None of its own: commands are forwarded to the motor driver inside the controller |
| Control4 proxy | Blind |
| Requires | Control4 OS 3.1.0 or later |
| Platform | Control4 DriverWorks, Lua |
Why is there no position slider?
The Lutron motor module ignores any level from 1 to 99 % and reports no position, so the driver offers open, close and stop. A programmed level is treated as open at 50 % or above and closed below it.
What if the blind is moved from a Lutron keypad?
The motor module does not report it, so the driver cannot see it. Use Set State to Open or Closed to bring the tile back in line.
Do I remove the Lutron motor driver?
No. This driver depends on it. Keep it in the project and hide it from Navigator, so the client sees only the shade.