How Does Silvair Connect Bluetooth NLC to LED Drivers?
Silvair DALI lighting control describes a system architecture, not a new driver protocol. The usual chain is sensor, switch, or control input → Bluetooth NLC network → Silvair-enabled fixture controller or integrated wireless driver → DALI, analog, or PWM output → LED driver or LED load → luminaire.
Choose where the intelligence lives
An external fixture controller can add Bluetooth NLC to a standard controllable driver. An integrated wireless driver combines power conversion and wireless control. A sensor-controller design can convert wireless occupancy or daylight behavior into DALI or analog output. In each case, the luminaire design, firmware configuration, output type, driver input, dimming target, and product approvals determine the result.
Use the terms Silvair-enabled Bluetooth NLC controller, Silvair-enabled fixture controller, Bluetooth NLC-to-DALI gateway, Bluetooth NLC-to-0–10V controller, and PWM-capable Silvair-enabled controller. Avoid treating “Silvair 0-10V protocol” or “Silvair PWM system” as standardized protocols.
What Does Part 341 Actually Standardize?
Silvair Firmware 2.32 NLC, announced by Silvair on June 26, 2025, introduced support for the Bluetooth NLC-to-DALI interface defined by DALI Alliance Part 341. That firmware capability can enable a hardware manufacturer to develop a standardized gateway; it does not certify every finished controller that uses the firmware. For Silvair DALI lighting control, verify the exact gateway model, GTIN, hardware revision, firmware revision, and certification record in the DALI Alliance Product Database.
Gateway, proprietary controller, and firmware support are different claims
A Part 341-certified Bluetooth NLC-to-DALI gateway is a standardized, certified product. A proprietary Bluetooth-to-DALI controller may output DALI but need not implement or be certified to Part 341. Firmware support is only an implementation building block. Part 341 v1.04 was published in September 2025; current specifications and certifications must be checked at the time of procurement.
What a Part 341 gateway can—and cannot—be assumed to do
On the wireless side, the gateway joins the Bluetooth NLC network. On the wired side, it acts as a DALI application controller. Core gateway behavior includes light-output control, fades, and querying lamp or light-source failure information. When connected control gear implements Parts 251–253, luminaire information, energy data, and diagnostics may be available to the wireless ecosystem.
The DALI bus must be powered. A D4i driver commonly provides integrated bus power; an ordinary DALI-2 driver may not, so the gateway, another DALI device, or a separate bus power supply may be required. DALI can have up to 64 short addresses or logical units, but gateway addressing, grouping, broadcast behavior, data aggregation, DT8, emergency functions, DALI input devices, and advanced data access are product-specific. Do not equate DALI capability with a guaranteed Part 341 gateway feature.
DALI, DALI-2 and D4i: Why the Distinction Matters
DALI is the IEC 62386 digital lighting-control technology. DALI-2 adds product testing and certification requirements intended to improve cross-brand interoperability. D4i builds on DALI-2 for intelligent luminaires, with requirements focused on luminaire, energy, and diagnostics data plus luminaire-internal power capability. Every D4i device is DALI-2, but not every DALI-2 driver is D4i.
A Bluetooth mesh DALI search term is useful only as a discovery label; it does not mean DALI messages travel wirelessly as DALI. In a Bluetooth mesh DALI project, Bluetooth NLC remains the wireless ecosystem and a gateway translates its lighting behavior to a wired DALI bus. This is the boundary that makes Bluetooth NLC DALI integration interoperable when the exact gateway and control gear support it.
How Do 0–10V and 1–10V Integrate with Bluetooth NLC?
A Bluetooth NLC-to-0–10V controller converts wireless light-level behavior into an analog signal for a compatible driver. This makes Silvair 0-10V and Silvair 1-10V approaches relevant to fixture upgrades where drivers are already installed. A wireless 0-10V lighting retrofit can retain a suitable driver, but only after electrical matching—not simply because the datasheet uses a familiar label.
The analog parameters that must be verified
- Whether the controller sources or sinks current, and whether the driver provides or receives control current.
- Maximum controller source/sink current and the aggregate control-current demand of all connected drivers.
- Polarity, control-voltage range, minimum voltage, dimming curve, minimum stable light level, and behavior when the control line is open, shorted, or unpowered.
- How many drivers one channel can operate; drivers on the same analog channel normally respond together, with no individual addressing or driver feedback.
- Whether 0 V or 1 V gives minimum light or true OFF, and whether a dim-to-off driver or a relay is needed.
- Whether mixed drivers create low-end mismatch, flicker, or unequal response.
Silvair 0-10V is not an interface specification by itself, and neither is Silvair 1-10V. A controller and driver must be matched for polarity, source/sink behavior, control current, minimum voltage, curve, and OFF behavior. In a Bluetooth mesh 0-10V installation, write those values into the fixture test record rather than relying on generic interface labels.
Where Does PWM Fit Into the Luminaire?
Silvair PWM is possible only where a PWM-capable Silvair-enabled controller and compatible driver or LED-control stage are selected. PWM is not a universal output of Silvair firmware. It can be appropriate for specialized or constant-voltage designs, integrated electronics, and single- or multi-channel luminaires, but the physical signal must be specified.
PWM parameters to match
- Signal voltage, such as 3.3 V, 5 V, or 10 V; PWM frequency; duty-cycle range; and the meaning of 0% and 100%.
- Source or sink output, maximum output current, shared ground/reference requirements, and whether the input is isolated.
- Channel count—single, dual CCT, or multi-channel—and whether the output is a low-level PWM control input or a power stage that can drive LEDs directly.
- The driver’s response to PWM frequency and the risk of visible flicker or stroboscopic effects.
As a product-specific example rather than a Silvair-wide specification, the notWired NW-MESH-STAMP-PWM-1CH datasheet identifies a 10 V PWM output with a maximum 10 mA source current; related variants include a dual-channel CCT option. This shows why a Silvair PWM decision must use the selected product datasheet. A Bluetooth mesh 0-10V controller cannot be assumed to provide the same PWM capability.
How Do Dimming, Switching and Tunable White Change the Design?
0% requested is not necessarily OFF
Silvair DALI lighting control may request 0% after vacancy, yet actual luminaire response depends on the controller output and driver. Dim-to-off means the driver can transition to OFF through its control interface. Some analog drivers only reach a minimum light level; they require an explicitly dim-to-off-capable driver or a separate relay/switching method for true OFF.
Tunable white needs independent capability
DALI dimming does not automatically mean tunable white. DALI tunable-white control generally involves IEC 62386 Part 209 (DT8) Tc colour control, and a Bluetooth NLC-to-DALI gateway must explicitly declare DT8 support before it is specified for that task. Analog and PWM implementations normally need at least two independent channels for warm and cool light, or intensity and colour-temperature control. Confirm CCT range, channel mapping, total-lumen normalization, minimum-level behavior, calibration, and OFF behavior across controller, driver, and LED module.
How FY LIGHTING Can Validate Silvair-Enabled Luminaires
No unverified product should be described as “fully compatible” or “seamless.” For an FY LIGHTING project, the validation record should identify the exact controller and driver models, firmware version, DALI/analog/PWM output type, minimum stable dimming level, actual result of a 0% command, tunable-white channel mapping, antenna location in the metal luminaire, radio performance, fault recovery, and power-cycle behavior. This evidence-based process gives Silvair DALI lighting control claims a testable boundary.
DALI/Part 341 vs 0–10V/1–10V vs PWM
| Comparison item | DALI / Part 341 | 0–10V / 1–10V | PWM |
| Signal type | Bidirectional digital communication | Analog voltage | Pulse signal |
| Control-wire polarity | DALI bus normally non-polarized | Normally polarized | Product dependent |
| Driver feedback | May support faults, energy, diagnostics | Normally none | Normally none |
| Multiple drivers | Depends on gateway broadcast/address/group functions | Same channel responds together | Same channel responds together |
| True OFF | Depends on control gear and gateway implementation | Needs dim-to-off or relay | Depends on PWM input and power stage |
| Tunable white | Confirm DT8 / Part 209 | Normally two channels | Normally two or more channels |
| Primary constraints | Bus power, address count, gateway certification/functions | Source/sink, current, low-end behavior | Voltage, frequency, current, channels, isolation |
For a new project, select DALI/Part 341 where a verified gateway, digital functions, and applicable driver data are required. Select analog control where the installed or specified driver is electrically compatible and grouped response is acceptable. Select PWM when the driver architecture explicitly expects it. For retrofit work, begin with the existing driver and wiring, then choose the compatible wireless control layer.
Certification and Compatibility Checklist
- Bluetooth layer: verify Bluetooth Mesh/Bluetooth NLC qualification and the implemented NLC Profile.
- DALI layer: verify Part 341, DALI-2, or D4i status as applicable, including the exact GTIN, hardware version, and firmware version in the database.
- Finished-product layer: verify the luminaire’s required UL, CE, EMC, electrical-safety, and radio-regulatory approvals.
- Control-chain layer: verify interface signal, driver response, OFF method, tunable-white behavior, bus power where applicable, thermal limits, wiring, fixture space, and antenna location.
Certification cannot be inferred from a similar model, a common firmware component, or a product family name. Bluetooth NLC DALI, analog, and PWM claims should each be tied to an exact tested and documented combination.
Specification language for project documents
A Silvair DALI lighting control specification should identify the installed Bluetooth NLC profile, the gateway or controller output, the LED-driver input, and the verified OFF behavior. This keeps Silvair DALI lighting control tied to a tested luminaire chain rather than a generic feature claim. Where the project uses Silvair 0-10V or Silvair 1-10V, the schedule should state source/sink direction, current limit, polarity, and the number of drivers per channel. Where it uses Silvair PWM, it should state voltage, frequency, duty-cycle definition, current, grounding, isolation, and channel count.
For an existing wired system, a Silvair DALI lighting control retrofit should distinguish a Part 341-certified Bluetooth NLC-to-DALI gateway from a proprietary controller. A Bluetooth mesh DALI search phrase should never replace that distinction. For analog work, a Bluetooth mesh 0-10V controller must be matched to every driver input; the intended wireless 0-10V lighting response must be proven at the lowest dim level and at OFF. These checks make Silvair DALI lighting control evidence-based.
In tender reviews, name the exact products and their firmware versions. Silvair DALI lighting control should state the gateway feature set, including whether it supports broadcast, addressing, grouping, data access, or DT8. A Bluetooth NLC DALI gateway selection should also document bus-power responsibility. For analog luminaires, Silvair 1-10V and wireless 0-10V lighting requirements must distinguish minimum light from true OFF. For PWM luminaires, Silvair PWM must be validated with the selected LED-control stage.
During factory acceptance, test the requested scenes, transitions, vacancy response, fault recovery, and restart behavior. The same record should confirm the chosen Bluetooth mesh DALI or Bluetooth mesh 0-10V architecture and capture relevant current and channel limits. Silvair DALI lighting control is credible when those results are retained with the luminaire test report. A Bluetooth NLC DALI project should not claim driver data functions that its selected gateway does not declare.
For maintenance, preserve the GTIN, hardware revision, and firmware revision for each component. This supports future Silvair DALI lighting control verification and avoids inferring compliance from an adjacent product model. Confirm Silvair 0-10V driver matching again if a controller is replaced, and verify Silvair PWM signal requirements whenever the LED module or control stage changes.
Finally, include the intended wireless 0-10V lighting behavior in the project handover documentation: light-level range, dim-to-off decision, and relay logic if used. Record whether the Bluetooth mesh DALI pathway is certified or proprietary, and verify the Bluetooth NLC DALI gateway record against the current DALI Alliance database. This makes Silvair DALI lighting control maintainable after installation.
Technical Sources
- Silvair, “Silvair announces full support for DALI ahead of the new DALI Alliance certification program,” June 26, 2025. https://silvair.com/blog/silvair-announces-full-support-dali-ahead-new-dali-alliance-certification-program/
- DALI Alliance, “DiiA Specifications: Part 341 – Bluetooth NLC Gateway,” v1.04, September 2025. https://www.dali-alliance.org/specifications/download.html
- DALI Alliance, “DALI Gateways Implementing Parts 341 or 342: Technical Guide,” September 2021. https://www.dali-alliance.org/data/downloadables/2/6/5/dali-alliance-technical-guide-to-dali-gateways-sept-2021.pdf
- DALI Alliance, “Gateways” and Product Database. https://www.dali-alliance.org/wireless/gateways.html ; https://api.dali-alliance.org/products
- Bluetooth SIG, “The Bluetooth NLC to DALI Gateway Specification.” https://www.bluetooth.com/learn-about-bluetooth/feature-enhancements/mesh/bluetooth-mesh-dali/
- notWired, “NW-MESH-STAMP” datasheet, January 4, 2021. https://www.cdiweb.com/datasheets/notwired/nw-mesh-stamp_2021_01_04.pdf
FAQ
Is Bluetooth NLC-to-DALI the same as wireless DALI?
No. Bluetooth NLC is the wireless ecosystem. A gateway translates its lighting behavior to commands on a wired DALI bus.
Does a Bluetooth NLC-to-DALI gateway need DALI bus power?
Yes. Bus power can come from a D4i driver, the gateway, another DALI device, or a separate DALI bus power supply, depending on the design.
Can a Part 341 gateway individually control every DALI driver?
Not automatically. Addressing, grouping, and broadcast capabilities must be confirmed for the exact certified gateway.
Can a Part 341 gateway control DT8 tunable-white drivers?
Only if Part 209/DT8 support is explicitly implemented by the gateway and compatible control gear.
How many 0–10V drivers can one controller operate?
The number depends on the controller source/sink-current rating and the control-current requirement of every connected driver.
What PWM values must be matched?
Match signal voltage, frequency, duty-cycle range, source/sink behavior, current rating, channel count, grounding/reference, isolation, and the type of input.
Does 0 V always switch an analog luminaire off?
No. Some drivers only dim to a minimum level. Confirm dim-to-off capability or provide a suitable switching method.
Does Silvair firmware automatically certify the finished controller?
No. Firmware support does not replace Bluetooth, DALI, safety, EMC, radio, or project-specific product verification.
What evidence should a luminaire supplier provide?
Provide exact models, hardware and firmware versions, interface specifications, test results at low dimming and OFF, tunable-white mapping, and relevant certifications.
English