Hold-to-dim stopped working on your phantom load.
You programmed a Lutron keypad button against a phantom load so it could drive a fixture Lutron does not make. The tap works. The hold does nothing. On an Alisse there is no raise/lower button to fall back on, so the client has no way to dim at all.
This page is for the integrator who is standing in the room right now. It describes what is happening, why it shows up hardest on tunable white and Alisse, and how to get press-and-hold ramping back without changing the keypads.
What you are seeing
- A button assigned to a real Lutron dimmer holds and ramps normally.
- The same button assigned to a phantom or virtual load taps fine and holds dead.
- Raise/lower buttons, where the keypad has them, do nothing on that load either.
- On an Alisse keypad there are no raise/lower buttons, so hold was the only dimming gesture — and now there is none.
- It bites hardest on tunable white and other fixtures not made by Lutron, where a phantom load was the reason for the integration in the first place.
Why it happens
A Lutron dimmer is a load the processor can ramp: it holds a level, and the processor knows how to walk that level up and down while a button is held. A phantom load is a trigger, not a dimmer. There is no level behind it for the processor to walk, so the press-and-hold gesture has nothing to act on and the keypad reports nothing useful. Tap-to-toggle survives because a tap is a single event; hold does not, because holding is a ramp.
That is a description of the behaviour integrators encounter, not a claim about intent. It is the reason the workaround below exists.
The usual workarounds, and why they run out
Give the load a real Lutron dimmer
Works, and is the right answer when the fixture will accept it. It stops being an answer the moment the fixture is DALI, DMX, tunable white with a separate CCT channel, or anything whose driver is not a Lutron dimmer.
Use raise/lower buttons instead
Fine on a keypad that has them. Alisse does not, and re-specifying keypads on a finished job is not a fix, it is a re-order.
Programme repeated steps on the processor
You can approximate a ramp with a sequence of level steps. It feels like a ramp for about a second, and then it feels like a sequence — and every fixture you add is more programming that lives in the processor rather than with the fixture.
What Ctrlable does about it
A Ctrlable Pro appliance sits on the same network as the processor and speaks to it over Lutron's own integration protocols. Buttons Machine takes the keypad press — including press, double-tap and hold — and turns it into an action against whatever the fixture actually is: a DALI ballast, an Art-Net channel, a tunable white pair, a Matter device.
The part that matters here
Hold becomes a ramp again, because the ramp is being run by the appliance against the real fixture rather than by the processor against a load that has no level. The keypad does not change. The engraving does not change. The client presses and holds the same button they always did.
- Any button, any gesture. Press, hold, double-tap and off-level are all action types, on any of eleven keypad families.
- Alisse gets dimming back without raise/lower buttons, because hold is the gesture.
- Tunable white as one gesture. Hold can drive level, colour temperature, or both, on fixtures whose CCT is a separate channel.
- Programmed from a browser. Changing what a button does is a browser tab, not a laptop with processor software and a site visit.
Questions integrators ask
Do I have to replace the Lutron system?
No. The processor stays, the keypads stay, the engraving stays. The appliance sits alongside and takes the button events.
Does this work with Alisse specifically?
Yes — and Alisse is the clearest case for it, because without raise/lower buttons a hold gesture is the only way to dim from the keypad.
What about tunable white that is not a Lutron fixture?
That is the common reason a phantom load exists in the first place. Level and colour temperature can both be driven, including from a single held button.
Is this a cloud service?
No. The appliance is self-hosted on the site's own network and is licensed per appliance. It does not need a forwarded port to be reachable.
Can I try it before specifying it on a job?
Yes. Dealers get a licensed instance to commission a real project on. There is also a working system you can walk through in a browser with nothing to install.
Lutron, Alisse, RadioRA and HomeWorks are trademarks of Lutron Electronics Co., Inc. Ctrlable is an independent company and is not affiliated with, endorsed by, or sponsored by Lutron. Product names are used here only to describe interoperability.