Silvair Emergency Lighting Testing and UL 924 Integration

Silvair emergency lighting testing (ELT) and Silvair UL 924 Functionality are two independent technical subjects. ELT automates functional and duration tests for supported self-contained emergency luminaires and manages the resulting records. UL 924 Functionality describes a North American control arrangement in which an emergency relay overrides normal dimming when loss of normal power is detected. The two functions may be used in one project, but neither replaces the other, and neither replaces the emergency power design or the required product approvals.

What Silvair ELT Doesand What It Does Not Do

Silvair emergency lighting testing is designed for self-contained emergency luminaires with a backup battery. Each supported luminaire runs scheduled tests and stores its results locally. A project can then use Core ELT, in which a technician collects results on site with the Silvair mobile app for iOS or iPadOS, or optional ELT with Remote Monitoring, in which a gateway collects results automatically and stores reports in the cloud. For a purchaser, silvair emergency lighting testing starts with the emergency luminaire and its hardware evidence, not with the app.

The capability is not a central-battery system design tool. It also does not make an ordinary luminaire an emergency luminaire simply because a wireless controller is added. Silvair ELT is the test and record-management layer; the battery, emergency control gear, driver, luminaire construction, electrical installation, and local approval process remain separate responsibilities. Wireless emergency lighting testing should begin only after the emergency hardware has been identified.

The Three Technical Paths in an ELT Project

The following conceptual diagram separates normal lighting control, emergency operation, and ELT data. It is an architecture map, not an installation wiring diagram. The Bluetooth Mesh network and cloud platform do not supply emergency power. The phrase bluetooth mesh emergency lighting describes the communication layer, not the battery or emergency output.

Normal lighting control path

During normal operation, a Silvair controller or sensor controller can send commands to a supported driver through an available 0-10 V or DALI control interface. Occupancy behavior, schedules, daylight responses, scenes, and manual commands belong to this path. The exact interface and behavior are product-specific.

Emergency power and emergency operation path

When normal power fails, the emergency luminaire and its emergency control gear use the designed backup source. In a self-contained luminaire, that normally means the local battery and emergency driver or control gear. The emergency output is determined by the emergency hardware and electrical design, not by the cloud service.

ELT testing and result path

The luminaire executes a scheduled or manually started test, stores its result, and exposes the result through the supported Bluetooth Mesh environment. Core ELT uses the mobile app for on-site collection. Remote Monitoring adds a gateway, which collects configured results and sends them to the cloud. Automatic test execution is therefore different from automatic remote result collection. This is the practical distinction behind silvair emergency lighting testing in a connected project.

ELT-Compatible Hardware and Project Requirements

The current Silvair application note SN-214 rev. 4.3 identifies the following ELT combinations. These are capability requirements, not a substitute for checking the exact device datasheet or the current compatibility record. Support for ordinary DALI dimming alone must not be treated as support for DALI Emergency testing.

The same application note requires a project commissioned with Silvair Commissioning tools, project version 202201 or later, radio communication between areas, ELT enabled for the project, and an iOS/iPadOS mobile app. Core ELT requires an authorized person on site to collect results. Remote Monitoring additionally requires a gateway installed in the project and the remote-monitoring feature enabled. These requirements should be rechecked before procurement because Silvair notes that operating parameters may change. A complete silvair emergency lighting testing specification should list each dependency explicitly.

Functional Tests and Duration Tests as Maintenance Procedures

Functional test workflow

SN-214 describes a functional test as a short test of circuit integrity and the correct operation of the luminaire, switching device, and backup battery. A practical maintenance workflow is:

1. Confirm that the luminaire is commissioned, powered, in its normal state, and assigned to the intended zone.
2. Confirm the functional-test schedule in the Silvair web app, or select the individual luminaire in the iOS/iPadOS app for a manual test.
3. Let the device execute the test; do not treat a trigger as proof that the test completed.
4. Collect the result on site with the mobile app, or allow the gateway to collect it where Remote Monitoring is enabled.
5. Read the test state and device state separately. Failed, Not yet collected, Triggered, Postponed, and Not availablerequire different follow-up.
6. If the result is a hardware or battery fault, follow the luminaire manufacturer service procedure, repair the cause, repeat the test, and retain the updated record.

Duration test workflow

A duration test checks whether the backup battery can supply emergency power for the required period. SN-214 permits a duration-test interval from 4 to 52 weeks and a functional-test interval from 1 to 52 weeks in the documented application. Those ranges are configuration limits in the application note, not a universal legal schedule.

7. Confirm the required emergency duration and the project maintenance approval before scheduling.
8. Review the evacuation route, emergency-lighting coverage, and the consequences of testing neighboring luminaires together.
9. Place no more than one emergency luminaire in a zone, because luminaires in the same zone are tested together.
10. Use additional duration schedules to separate adjacent zones; SN-214 documents up to four zone groups and allows schedules to be offset by one, two, or three weeks.
11. After the test, check the battery and luminaire state, collect the result, and record any failed, postponed, stopped, dropped, or timed-out status.
12. If the battery is discharged or the duration test fails, follow the luminaire documentation, restore the emergency capability, and obtain approval before returning the device to the normal test plan.

The reason for separating adjacent zones is operational rather than merely geographic. If an emergency occurs during or shortly after a duration test, luminaires with depleted or recovering batteries may not be able to provide emergency lighting. Grouping should therefore follow egress routes, coverage, battery behavior, and the building risk assessment. The responsible designer or facilities authority should approve the plan; this article does not prescribe a fixed group count, recovery time, or safety distance.

Core ELT or Remote Monitoring: A Procurement Decision

The commercial distinction is easy to miss: both options can execute scheduled tests at the luminaires, but only Remote Monitoring automates routine result collection through a gateway. Core ELT is not a failed version of Remote Monitoring; it is a lower-infrastructure operating model that keeps the collection task on site. In procurement terms, silvair emergency lighting testing should be selected by maintenance workflow, not by the word wireless alone.

Results, Statuses, and Fault Handling

SN-214 distinguishes the device state from the test state. Device states include Normal, Emergency, Inhibit, Rest, Functional test, Duration test, Battery discharged, Not yet collected, Unknown, and Not available. Test states include Passed, Failed, Out of date, Triggered, In progress, Postponed, Stopped, Dropped, Timeout, Not yet tested, Not yet collected, Unknown, and Not available.

A communication or cloud problem should not be described as an emergency-light failure without checking the luminaire locally. Wireless emergency lighting testing produces a data record, while emergency operation remains a hardware function. Conversely, a report that has not been collected is not evidence that the luminaire passed. Maintenance staff should record the status shown by the system, inspect the relevant hardware, and repeat collection or testing only when the documented troubleshooting path calls for it.

DALI Emergency Integration and Upgrade Feasibility

DALI Device Type 1 (DT1) is the emergency control-gear context used in the SN-214 ELT requirements. A DALI address or a DALI dimming command is not enough by itself. The emergency control gear must support the required DALI Emergency behavior, and the controller, firmware, driver, battery, and luminaire must form a supported combination.

How to assess an existing luminaire

13. Identify the project country, applicable emergency-lighting rules, required emergency duration, and existing power architecture.
14. Record the luminaire, LED driver, emergency battery, emergency module or control gear, controller, and firmware identifiers.
15. Verify whether the emergency control gear is a supported DT1 device and whether the exact Silvair controller path is documented for ELT.
16. Check the project version, commissioning tools, radio coverage, mobile-app access, and the need for a gateway.
17. Confirm whether the existing driver and emergency module can support the desired operation without changing the luminaire listing or electrical design.
18. Obtain a written compatibility decision before ordering a retrofit.

An ordinary 0-10 V or DALI dimming luminaire cannot gain ELT capability automatically by adding a Silvair controller. The emergency battery and control gear must support the test function, and a change of driver or emergency module may affect certification, thermal design, wiring, and the product approval file.

How Silvair UL 924 Functionality Works

Silvair UL 924 Functionality is not the same as ELT. SN-226 rev. 2.0, dated 25 October 2024, explains a specific implementation using a Silvair lighting system and a UL 924 Emergency Lighting Relay. In the documented arrangement, the relay detects loss of normal power and its dry contacts open the 0-10 V control line between the Silvair sensor controller and the driver, forcing the driver to provide full light output.

UL 924 Functionality is not UL 924 certification

This distinction must be stated plainly. A control arrangement that provides an emergency override is a functionality claim. UL 924 listing or certification belongs to the actual emergency component or product evaluated under the applicable certification process. Complete installation compliance depends on the luminaire, relay, driver, power source, wiring, installation, and jurisdictional requirements. Silvair SN-226 does not authorize a blanket statement that every Silvair controller, every FY LIGHTING luminaire, or every project is UL 924 certified.

Operating sequence and failure boundaries

19. Normal power present: the Silvair controller can apply normal 0-10 V or DALI control commands through the supported driver path.
20. Loss of normal power detected: the external UL 924 relay changes the control path described in SN-226.
21. Emergency state: the driver is forced to the defined emergency output in the documented implementation, rather than being held at a normal dimmed or off command.
22. Normal power restored: the relay and luminaire return according to the actual relay, driver, and luminaire design; the product documentation must confirm the reset behavior.
23. Bluetooth Mesh interruption: do not assume it is equivalent to loss of normal power. A wireless communication failure and a power-failure detection event are different conditions and must be evaluated in the actual hardware.

The SN-226 example specifically documents a 0-10 V override path. It should not be expanded into an unverified universal DALI wiring diagram or assumed to describe every Silvair controller. The external relay, emergency power source, driver, and luminaire listing remain part of the safety-critical design.

Automatic Testing and UL 924: Two Different Compliance Dimensions

A project can require both automated testing and emergency-operation compliance. The standards should be checked by name and by function: DALI communication compatibility, DALI-2 certification, automatic test-system requirements, UL 924 listing, and local installation rules are not interchangeable labels. Bluetooth emergency lighting testing may help with test records, but it cannot be used as shorthand for any one certification.

FY LIGHTING Product Adaptation and Custom Solutions

For FY LIGHTING, the technically defensible sales path is a compatibility assessment rather than a blanket claim. A project review can examine the luminaire structure, driver and emergency battery, control-gear enclosure, controller mounting space, wiring, thermal constraints, required test records, and the intended Silvair or UL 924 architecture.

Where a standard configuration is not already verified, FY can discuss an ELT-compatible or UL 924-oriented project configuration, subject to component selection, engineering review, testing, and the certification documents for the final product. The words compatible, tested, listed, and certifiedshould be used only when the matching model and evidence support them.

Information to Provide for a Technical Quote

24. – Project country, building use, authority requirements, and applicable standards.
25. – Luminaire model, driver model, emergency battery and emergency-module details.
26. – Required emergency operating duration and normal/emergency power architecture.
27. – DALI Emergency or DT1 support evidence, if DALI is used.
28. – Silvair controller type, firmware, project version, and commissioning plan.
29. – Whether Core ELT or Remote Monitoring is required.
30. – Gateway location, network availability, and areas to be monitored.
31. – Required test-report format, retention expectations, and certification or listing documents.
32. – Any retrofit constraints, including housing space, wiring changes, thermal limits, and field-service requirements.

Frequently Asked Questions

Can an ordinary DALI luminaire use ELT?

Not automatically. The emergency control gear, controller, firmware, driver, battery, and luminaire combination must be documented as supported. DALI dimming compatibility alone is not proof of DALI Emergency or ELT compatibility.

Must an ELT luminaire use DALI DT1?

The SN-214 requirements document the supported ELT combinations with a DT1 DALI driver. Check the current Silvair application note and the exact product documentation before assuming another architecture is supported.

Can scheduled tests run without a gateway?

Yes. Core ELT devices can execute scheduled tests and store results locally. A gateway is required for the Remote Monitoring workflow and its automatic result collection.

Does Core ELT provide historical reports?

SN-214 states that Core ELT makes only the latest test report available for each test type and device. Historical reports are available in the documented Remote Monitoring workflow.

Does a gateway outage turn off emergency lighting?

Not on the basis of the gateway outage alone. The gateway collects and transfers test data; emergency operation is provided by the luminaire emergency hardware. The actual device state and local installation should still be checked.

Can ELT be used with a central-battery system?

No. SN-214 states that ELT supports self-contained emergency luminaires only and does not support central-battery systems.

Does UL 924 Functionality mean the complete luminaire is UL 924 certified?

No. It describes an emergency override arrangement. The actual luminaire, relay, driver, and installation require their own applicable certification, listing, and approval evidence.

Can an existing 0-10 V luminaire be upgraded?

Possibly, but not by adding a controller alone. The battery, emergency relay or module, driver, enclosure, wiring, thermal design, and certification status must be evaluated as one system.

What should happen after a failed test?

Read the device and test status, identify whether the cause is the luminaire, circuit, battery, discharge, communication, or collection state, follow the manufacturer service procedure, repair the cause, and repeat the test and record.

Can FY LIGHTING provide a compatible solution?

FY LIGHTING can assess a project or discuss a customized configuration, but support for Silvair ELT, DALI Emergency, or UL 924 must be confirmed for the specific final model and its technical evidence. A proposed bluetooth mesh emergency lighting solution should be checked against the final controller, driver, battery, and firmware combination.

Technical References and Verification Notes

1. Silvair, SN-214 Silvair Emergency Lighting Testing,- application note rev. 4.3, 28 October 2025: https://documents.silvair.com/SN-214_Silvair_Emergency_Lighting_Testing.pdf. Used for ELT scope, supported combinations, project requirements, schedules, result states, reports, gateway behavior, and troubleshooting.
2. Silvair, SN-226 Silvair UL 924 functionality,- application note rev. 2.0, 25 October 2024: https://documents.silvair.com/SN-226_Silvair_UL_924_functionality.pdf. Used for the documented UL 924 relay and 0-10 V override example.
3. Digital Illumination Interface Alliance, DALI Emergency –  https://www.dali-alliance.org/dali/emergency.html. Used for the distinction between DALI Emergency, Device Type 1, IEC 62386-202, automated testing, and DALI-2 interoperability.
4. UL Solutions, Emergency Lighting Systems Testing and Certification Services –  https://www.ul.com/services/emergency-lighting-testing-and-certification. Used for the distinction between UL 924 equipment evaluation, emergency controls, and broader certification or code requirements.
5. Silvair product documents: https://silvair.com/support/product-documents/. Use this library to check the current revision of application notes and project-specific compatibility material before final specification.

For project documentation, silvair emergency lighting testing should identify the supported luminaire, battery, emergency control gear, controller, firmware, test schedule, and result-collection method. Bluetooth emergency lighting testing describes the data and test layer; the electrical emergency path remains a separate design responsibility.

In a Silvair ELT procurement review, the decision should be based on hardware compatibility, maintenance workflow, and reporting needs. Silvair ELT can be appropriate for a project using Bluetooth mesh emergency lighting when the documented controller, DT1 gear, firmware, radio coverage, and project version are confirmed.

A silvair UL 924 review should identify the actual relay, driver, controller, emergency power source, and product evidence. Silvair emergency lighting testing and bluetooth emergency lighting testing may support maintenance records, but neither term should be used as a substitute for a listed emergency component or installation approval.

For retrofit enquiries, wireless emergency lighting testing is only one part of the feasibility decision. The buyer should verify the final luminaire construction, emergency battery, control gear, and certification file before describing a bluetooth mesh emergency lighting product as ready for a project.

The final specification should use silvair emergency lighting testing as a precise description of automated testing and result management, not as a claim about emergency power, listing, or local code approval. Bluetooth emergency lighting testing and wireless emergency lighting testing remain subject to the exact supported hardware.