Published: 4 September 2026 | Updated technical review: 4 September 2026 | Specification context: DiiA Specification Part 341 v1.04 (September 2025)
Technical review basis: public Silvair, Bluetooth SIG, and DALI Alliance materials cited inline. This guide is not a product certificate, wiring instruction, or site-specific engineering sign-off; selected controller and driver documentation remains controlling.
Silvair does not replace the DALI interface inside a luminaire. In a DiiA Specification Part 341 – Bluetooth NLC Gateway architecture, Silvair-powered firmware runs in a compatible gateway or control device that joins the Bluetooth NLC network and converts supported wireless lighting commands for the wired DALI side. The DALI-2 or D4i driver remains DALI control gear; it does not become a Bluetooth mesh node. [1][2]
Silvair DALI lighting control therefore describes a control architecture, not a single universal hardware output. Silvair Firmware can be integrated by manufacturers into different component designs. Silvair’s public firmware material identifies UART, DALI, and 1–10V as integration paths; a controller advertised as Silvair-compatible must still be checked for its actual electrical interface and certified functions. [3]
How Does Silvair Connect Bluetooth NLC to LED Drivers?
Silvair connects wireless intent to an LED driver through a selected control device or integrated driver; Bluetooth NLC handles the wireless side, while DALI, 0–10V, 1–10V, or a product-specific PWM implementation handles the physical driver side. The interface is determined by the luminaire and controller design, not by Bluetooth NLC alone.
Three practical architectures
An external fixture controller places a Bluetooth NLC control device between the network and a conventional driver. An integrated wireless driver combines driver electronics and wireless control in one component. A sensor-controller arrangement receives occupancy or daylight input, participates in Bluetooth NLC, and commands a separate driver. Each can support scenes, manual control, occupancy response, and daylight behavior, but the driver interface and serviceability differ.
For Silvair DALI lighting control, the normal chain is control input → Bluetooth NLC → Part 341-capable gateway/control device → two-wire DALI interface → DALI control gear → LED module. For silvair 0-10v or silvair 1-10v projects, the control device must instead provide the compatible analog output. A silvair PWM implementation is only valid when the exact hardware datasheet documents that output.
How Does Silvair DALI Lighting Control Work?
Silvair DALI lighting control works by provisioning the Bluetooth NLC gateway onto the wireless network and using that gateway to translate supported NLC commands to the wired DALI interface. A DALI driver is controlled through the gateway; it is not Bluetooth-provisioned itself. This preserves a clear boundary between the radio network and DALI control gear. [1][2]
Part 341: version, firmware support, and certification evidence
The complete name is DiiA Specification Part 341 – Bluetooth NLC Gateway. The DALI Alliance download page lists v1.04, published in September 2025, and identifies certification availability in Q4 2025. Silvair announced support for the Bluetooth NLC-to-DALI interface with Silvair Firmware 2.32 NLC on 26 June 2025. Firmware support is not product certification: only a specific gateway that has passed the applicable tests and is listed in the DALI Alliance Product Database should be represented as DALI-2 certified. [1][4]
This distinction is essential for procurement. Ask for the gateway model, firmware version, declared Bluetooth NLC Profile support, DALI-2/Part 341 certification evidence, and the driver’s own DALI-2 or D4i status. Do not infer that every device using the same firmware stack has identical interface, data, or certification capabilities.
What Can—and Cannot—DiiA Specification Part 341 Do?
Part 341 standardizes a gateway boundary: Bluetooth NLC is wireless, DALI remains wired. It can translate supported light-output and fade-related control between those domains and, where the driver and gateway support it, expose selected status or data. It does not turn the DALI bus into “wireless DALI,” DALI+, or a collection of Bluetooth nodes. [2][4]
Control, data, and addressing limits
A D4i driver may store luminaire, energy, and diagnostics data under Parts 251, 252, and 253; the gateway must explicitly support reading and mapping the relevant fields before those data become available to an NLC application. The driver providing data is necessary, but not sufficient. Part 341 gateway behavior, data aggregation, and the selected application determine what is exposed. [5][6]
Do not promise independent Bluetooth NLC addressing for every driver simply because a DALI bus supports addressing concepts. Current gateway documentation and the chosen gateway data sheet define the accessible control model. Where multiple drivers are controlled together, broadcast control is common. Likewise, DALI sensors, buttons, and other wired control devices do not automatically appear as Bluetooth NLC devices.
| Terminology note: A Part 341 Bluetooth NLC-to-DALI gateway translates between Bluetooth NLC and wired DALI. A Silvair Connected Services or remote-management gateway connects systems to internet or cloud services. They are different functions; local lighting control does not inherently require an internet gateway. |
DALI, DALI-2, and D4i: What Is the Difference?
DALI is the digital lighting-control interface defined in IEC 62386. DALI-2 is the DALI Alliance certification program based on current DALI requirements; it is not a separate radio protocol. D4i is a DALI-2 extension for intelligent luminaires, adding mandatory power and data features for the certified driver. [6]
For D4i LED drivers, Part 250 integrated bus power and Parts 251, 252, and 253 for luminaire, energy, and diagnostics data are mandatory. A D4i driver can power connected DALI devices on the bus, whereas an ordinary DALI-2 driver may not include bus power. D4i is valuable when a project needs intra-luminaire control and standardized data, but it is not automatically required for every Silvair DALI lighting control project. [5][6]
DALI version-1 compatibility must be confirmed against the exact Part 341 gateway documentation. Never assume that an older driver supports the same control, data, or bus-power behavior as a DALI-2 or D4i device.
How Do 0–10V, 1–10V, and PWM Fit into a Silvair System?
Analog and PWM interfaces are product-specific alternatives to DALI, not default capabilities of the Silvair platform. A compatible controller can convert a wireless command into an analog dimming signal for a driver, enabling a silvair 0-10v retrofit or a silvair 1-10v fixture design when its documented output matches the driver input. The radio layer does not make the two analog conventions electrically identical.
Analog retrofit conditions
For a wireless 0-10v lighting retrofit, compare control-voltage range, polarity, source/sink behavior, control current, minimum output, and OFF response. A driver that dims does not necessarily turn off at 0 V. The specification must state whether dim-to-off is supported or whether the design needs relay switching, driver-native OFF behavior, or another documented method.
PWM requires a real electrical specification
silvair PWM should be specified only for a controller or driver whose datasheet identifies PWM frequency, logic level, output polarity, duty-cycle range, channel count, common-ground or isolation arrangement, minimum pulse width, and OFF behavior. “PWM-capable” without those constraints is not enough to approve a luminaire. This is especially important for multi-channel or specialized constant-voltage LED assemblies.
How Does Tunable White Affect DALI, 0–10V, and PWM Integration?
Tunable-white control requires a supported colour-control path in addition to light-level control. For standardized DALI tunable white, a DALI-2 DT8(Tc) driver under IEC 62386 Part 209 is the normal driver foundation: Tc denotes correlated-colour-temperature control. It is necessary, but it is not sufficient by itself. [7]
The Part 341 gateway must explicitly support the required Part 209 colour commands, and the selected Silvair-enabled hardware must expose compatible CCT control, such as a suitable Bluetooth Light CTL or manufacturer-defined implementation. Bluetooth NLC support and a DT8 driver alone do not prove end-to-end tunable-white interoperability. Verify supported CCT range, control channels, gateway command support, dimming interaction, calibration, and OFF behavior before release.
How to Specify the Correct Silvair-to-Driver Interface
Specify the whole chain rather than a keyword. For silvair DALI lighting control, name the Part 341 gateway, its firmware, certification evidence, DALI bus-power source, driver type, and required data fields. For silvair 0-10v, name the analog output specification and driver input behavior. For silvair 1-10v, document the precise controller-to-driver electrical compatibility. For silvair PWM, attach the timing and channel requirements.
Use the same discipline with search terms. bluetooth mesh DALI and bluetooth NLC DALI describe the wireless-to-DALI architecture, but do not prove a gateway’s data or commissioning scope. bluetooth mesh 0-10v and wireless 0-10v lighting describe retrofit concepts, not a universal output feature. Evidence must come from the selected component documentation, qualification records, and prototype test results.
Terminology for a defensible specification
A silvair DALI lighting control submittal should identify the gateway, wired DALI gear, and proof of the functions requested. In a bluetooth mesh DALI or bluetooth NLC DALI proposal, state the Part 341 gateway model rather than implying that the driver itself is wireless. For a silvair 0-10v upgrade, document the analog-output limits; for bluetooth mesh 0-10v, document the same physical controller-to-driver match.
A silvair DALI lighting control package should keep DALI, analog, and PWM claims separate. A silvair 1-10v design must identify the 1–10V driver behavior; a silvair PWM design must include its output timing specification. The terms wireless 0-10v lighting, bluetooth mesh DALI, and bluetooth NLC DALI are useful project descriptors, but none replaces a component data sheet.
In the final schedule, use silvair DALI lighting control only for the documented NLC-to-DALI control chain. List bluetooth mesh DALI, bluetooth NLC DALI, and bluetooth mesh 0-10v only where their exact gateway or controller architecture has been selected; this prevents a keyword from becoming an unsupported product promise. A bluetooth mesh 0-10v schedule must still identify the exact output and driver input.
Interface selection summary
| Decision factor | DALI / Part 341 | 0–10V / 1–10V | PWM |
| Control signal | Digital, wired DALI behind gateway | Analog control voltage | Product-specific pulse signal |
| Communication direction | Potential command and supported data return | Usually control only; no standard driver data | Usually control only; implementation-specific |
| Addressing / feedback | Gateway exposure is product-limited; do not assume per-driver NLC addressing | No standardized driver feedback | No standardized commercial-lighting feedback |
| Bus power | Confirm driver, gateway, or separate supply; D4i has integrated bus power | Not a DALI bus | Not a DALI bus |
| OFF / low end | Driver and implementation dependent | Verify dim-to-off; 0 V is not universal OFF | Verify duty cycle and OFF specification |
| Tunable white | DT8(Tc) + gateway command support required | Suitable multi-channel analog design | Specified multi-channel timing/output required |
| Best fit | Digital DALI/D4i integration and supported data needs | Existing compatible analog-driver retrofit | Engineered fixture electronics |
| Main risk | Assuming certification, data, or addressing beyond gateway scope | Voltage/source-sink/OFF mismatch | Undefined logic, timing, channels, or isolation |
How to Test Controller-to-Driver Compatibility
A compatibility check should be a repeatable acceptance test, not a datasheet-only review. Start by recording the control-device model, Silvair firmware version, Bluetooth NLC Profile, and physical output interface. For DALI, record the gateway’s Part 341 status, driver’s DALI-2/D4i/DT8 claims, bus-power source, and required Parts 251–253 data. Then create a controlled fixture test before volume production.
Recommended test sequence
- Test 100%, 75%, 50%, 10%, 1%, and OFF. 2. Record fade smoothness, lowest stable output, flicker, and actual OFF behavior. 3. Test power restoration, driver fault, lamp fault, and replacement behavior. 4. If data services are specified, read and record available energy, operating-time, fault, and diagnostic fields. 5. Test the final antenna position and radio quality inside the finished metal enclosure. 6. Preserve controller/driver model numbers, measurements, and firmware versions in the project submittal.
This sequence is the appropriate place to capture actual standby power, measured dimming range, and data-readout results. They must be measured on the selected hardware, not copied from a generic integration guide.
New-Build and Retrofit Decision Framework
For a new build, select DALI when digital driver control, D4i data, or a standardized Bluetooth NLC-to-DALI gateway path is required and verified. Select 0–10V or 1–10V when the project favors a compatible analog driver with clear low-end and OFF behavior. Select PWM only when the fixture electronics are deliberately designed, documented, and tested as a matched system.
For a retrofit, start with the installed driver. Existing DALI gear may support a gateway solution; existing analog drivers may be retained in a wireless 0-10v lighting plan if their electrical behavior matches the controller; existing PWM-controlled assemblies require an exact output match. Evaluate driver condition, wiring, available power, sensor placement, enclosure space, antenna performance, zoning changes, and required data or tunable-white functions before selecting the wireless component.
Silvair-Compatible LED Lighting Integration from FY LIGHTING
FY LIGHTING can support project-level integration work by matching Silvair-compatible controllers and drivers; selecting DALI, D4i, 0–10V, or PWM interfaces; preparing a control architecture and wiring documentation; verifying dim-to-off and low-end dimming; assessing sensor/controller placement and metal-enclosure wireless performance; and arranging prototype samples, compatibility testing, certification-document support, and technical submittals.
For a useful review, provide the luminaire type, driver model, power and voltage, dimming interface, requested dimming range, D4i data requirements, DT8/tunable-white requirements, installation environment, and project region. This allows the engineering discussion to start with verifiable component constraints rather than generic compatibility claims.
Frequently Asked Questions
Can a DALI driver be controlled through a Silvair Bluetooth NLC network?
Yes—through a compatible Bluetooth NLC-to-DALI gateway. The gateway joins the wireless network; the driver remains on the wired DALI interface. Verify driver compatibility, bus power, gateway functions, and certification independently.
Does a DALI driver become a Bluetooth NLC node?
No. The Part 341 gateway is provisioned on Bluetooth NLC. The DALI driver remains DALI control gear and communicates with the gateway on the wired DALI side.
Is a Part 341 gateway the same as wireless DALI or DALI+?
No. Part 341 defines a Bluetooth NLC Gateway that bridges wireless NLC to a wired DALI interface. It should not be described as DALI+ or as a DALI bus made wireless.
Can one Part 341 gateway independently control multiple DALI drivers?
It depends on the gateway’s documented control model. Do not infer individual Bluetooth NLC addressing from DALI addressing capabilities; broadcast control and limited data exposure are common considerations.
Can Silvair read energy and diagnostic data from a D4i driver?
Conditionally yes. D4i drivers implement standardized Parts 251–253 data, but the selected Part 341 gateway and application must support reading and mapping the fields needed by the project.
Is D4i required for Silvair DALI lighting control?
No. D4i is not universally required. It is relevant where integrated bus power and standardized luminaire, energy, or diagnostics data are required.
Does a Part 341 gateway work with DALI version-1 drivers?
Do not assume so. Confirm compatibility, supported control functions, and bus-power behavior in the exact gateway and driver documentation.
Who provides power to the DALI bus?
It depends on the architecture. A D4i driver includes integrated bus power, while other systems may use another driver, the gateway, or a separate supply. Document and test the source.
Does Part 341 automatically support DT8 tunable white?
No. A DT8(Tc) driver is only one requirement. Confirm the gateway supports the required Part 209 colour commands and that the Silvair-enabled hardware exposes compatible CCT control.
Is an internet gateway required for local lighting control?
No. A Part 341 gateway provides local Bluetooth NLC-to-DALI translation. A cloud or remote-management gateway is a separate function used only when remote connectivity is required.
How can a buyer verify Part 341, DALI-2, and Bluetooth NLC claims?
Request the exact model, firmware version, certificates or database listing, declaration of supported Profiles and interfaces, and a documented prototype test. Do not rely on a generic firmware claim.
What happens if a 0–10V driver does not support dim-to-off?
A 0% request may leave the luminaire at its minimum output. Specify a compatible dim-to-off driver or another documented switching method, then verify the final fixture response.
References
[1] Silvair. “Silvair announces full support for DALI ahead of the new DALI Alliance certification program” (26 June 2025).
[2] Bluetooth SIG. “The Bluetooth NLC to DALI Gateway Specification.”
[3] Silvair. “Silvair Lighting Control Firmware” — public interface overview.
[4] DALI Alliance. “DiiA Specifications” — Part 341 v1.04, September 2025; certification availability listed as Q4 2025.
[5] DALI Alliance. “DALI Data” — Parts 251, 252, and 253.
[6] DALI Alliance. “D4i overview.”
[7] DALI Alliance. “DALI Colour Control” — IEC 62386 Part 209 / DT8(Tc).
English