A UL 924 emergency lighting control device forces designated corridor, lobby, and ballroom fixtures to a preset full-output level the moment normal power is lost, overriding whatever dimming scene or occupancy state was active, and it does this using a dedicated power-loss sensor wired to the lighting processor rather than through the everyday scene logic. The override only works if the designated circuits are actually fed from generator or inverter backup power, and the sensor itself is tested by simulating a phase loss, not by pulling a breaker. Getting this right on a Crestron-based system means understanding three linked components: the dimmer module's override input, the power-loss sensor, and the acceptance test sequence an inspector expects to see documented. Cave Group designs hotel guest-room and public-space lighting control on Crestron and Lutron platforms, and this kind of code-driven override is one of the details that has to be resolved with the electrical engineer before a property's lighting scope is signed off.
How does a UL 924 override actually force lights to full output?
On a Crestron Green Light system, the override behavior lives in the dimmer module itself, not in the room's scene programming. Crestron's GL-EXP-DIMU-CN is a single-channel dimmer module that is UL 924 listed for emergency lighting control applications, and it has a dedicated low-voltage OVERRIDE input pair separate from its normal Cresnet control connection. When a contact closure is sensed on that input, the module enters override mode and drives the load to a preset level that is configured during commissioning — "so even if the load is already on prior to a power failure, it will change to the preset level when override mode is activated," as Crestron's own product documentation puts it. That means a dimmed lobby scene at 20 percent does not simply stay at 20 percent during an outage; the override input pulls that specific circuit to its designated emergency level regardless of what the scene engine was doing a moment before.
This is a hardware-level behavior, not a software scene recall. The override input bypasses the dimming program entirely while a closure is present, which is precisely why it satisfies UL 924: it does not depend on the control processor staying online, responsive, or correctly programmed at the moment of a power event.
What triggers the override, and how does it tie to backup power?
The trigger comes from a separate device: the power-loss sensor. Crestron's GLS-PLS-120/277 is built specifically for this role — it is "used to satisfy UL 924 (Emergency Power Equipment) requirements" and senses each leg of a 120 or 277 volt, 3-phase feed independently, per Crestron's GLS-PLS-120/277 product page. When any phase drops, the corresponding status LED turns off and the sensor closes two isolated contact outputs. Those outputs feed the OVERRIDE inputs on each designated dimmer module, and the design intent is explicit in the source material: the lighting program is "temporarily overridden while designated emergency lighting circuits are changed to their override preset levels and unnecessary lighting and other devices are shut down to minimize the demand on emergency power equipment." In other words, the sensor's job is not just to turn emergency fixtures on — it's also part of load shedding, reducing demand on whatever generator or inverter capacity is actually carrying the building during the outage.
That makes the tie to backup power a design dependency, not an afterthought: the override preset only produces usable light if the circuit feeding that fixture is actually on the emergency bus. An integrator and the electrical engineer need to confirm, circuit by circuit, which dimmer channels are fed from backup power before any override preset levels are assigned — a question worth raising directly with your electrical contractor during design, since the lighting control system cannot create emergency power where none was wired.
How does the override interact with dimming scenes and occupancy sensors?
Because the override operates at the dimmer module hardware level, it takes priority over whatever the room's control logic was doing, including occupancy-sensor-driven dimming or scheduled scenes in a corridor or ballroom. While the OVERRIDE contact is closed, the module holds its preset level and effectively ignores further commands from the Cresnet bus for that channel. When normal power returns and the sensor's phase LEDs indicate restored power, the contact opens and the module should return to following the lighting program again — but this handoff, and how cleanly it happens, is exactly the kind of behavior that needs to be verified in the field rather than assumed from a spec sheet.
This is also where hospitality lighting design intersects with guest-room and public-space automation more broadly: a property's hospitality lighting and control scope should map out, zone by zone, which circuits carry the UL 924 override and confirm that occupancy sensors and scene controllers in those same spaces don't fight the override logic during an actual event.
What does an inspector check before sign-off?
The GLS-PLS-120/277 includes a built-in test function specifically so this can be verified without staging a real outage: three test switches behind a cover plate let you "simulate a loss of power on the corresponding phase leg, providing a test of the unit's internal circuitry and any connected equipment." That test function is the practical basis for an acceptance test — setting each phase to TEST individually confirms the sensor correctly detects a single-leg loss and that the downstream override contacts close and reach every designated dimmer module.
Before an inspector signs off, plan to walk through and document, for each designated emergency circuit: which dimmer module it runs through, what override preset level was commissioned, confirmation that the circuit is fed from generator or inverter backup, and a recorded test of the power-loss sensor using its built-in TEST switches. Ask your commissioning team to produce a written log of this sequence per floor or zone, since that documentation — not just a functioning fixture — is typically what a fire marshal or electrical inspector wants to see at final walkthrough.
Frequently asked questions
What makes a lighting control device UL 924 listed?
A UL 924 listing means the device is rated for emergency lighting control applications and is designed to force a load to a specific output state on a power-loss signal; Crestron's GL-EXP-DIMU-CN carries this listing specifically for its override behavior when triggered by a power loss sensor contact closure.
Does the override preset level have to match the normal dimming scene?
No. The override preset is configured separately during commissioning and takes effect regardless of what level the circuit was dimmed to before the outage, including forcing a fixture to full output that had been dimmed low or switched off.
Can one power-loss sensor cover an entire hotel floor?
The GLS-PLS-120/277 senses all three legs of a single 3-phase feed and provides two isolated contact closure outputs, so the number of sensors needed depends on how many separate feeds and how many designated dimmer modules the floor's emergency lighting circuits actually use; that circuit count should be confirmed with the electrical engineer during design.
How is the power-loss sensor tested without cutting real power?
The GLS-PLS-120/277 has three built-in test switches that simulate a loss of power on each phase leg independently, allowing the sensor's detection circuitry and the connected override-mode dimmer modules to be verified without an actual outage.
Who is responsible for confirming emergency circuits are on backup power?
That confirmation sits with the electrical engineer and contractor, since the lighting control system can only activate an override preset on circuits that are physically wired to generator or inverter backup; a hospitality integrator can document which dimmer channels are assigned to the override but cannot substitute for that electrical design verification.