2026-09-10 · 8 min read · Comparison
The short answer
For a new multi-vendor project — especially an office, education or hospitality scheme in Europe with sensors, scene controllers and products from more than one manufacturer — specify DALI-2: its certification program enforces the interoperability that classic DALI promised but never guaranteed. For a small, single-brand retrofit — one dimmable circuit, one supplier's drivers and panel, everything from the same catalogue — classic DALI remains perfectly adequate and slightly cheaper. The difference is not the wire protocol (both run the same two-wire bus) but the governance around it: DALI-2 extended the IEC 62386 standard, added application controllers to the specification, and wrapped both in a tested, logo-bearing certification program. Our smart lighting program defaults to DALI-2 drivers and sensors for exactly the multi-vendor reasons below.
The standards underneath the names
DALI (Digital Addressable Lighting Interface) began as an industry standard and matured into IEC 62386. Classic DALI in practice meant the original core: control gear (drivers) addressable on a two-wire bus, a single master controller commanding up to 64 addresses, and — critically — enough implementation freedom that devices from different vendors occasionally refused to cooperate cleanly. The protocol worked; the ecosystem's interoperability was uneven because the test and certification regime lagged the paper standard.
DALI-2 is the current generation of IEC 62386: the standard was restructured into parts (system components, control gear, control devices), behaviours were tightened where vendors had drifted, and the industry body's DALI-2 certification program put every product through defined compliance testing before it may carry the DALI-2 logo. The practical meaning for buyers: "DALI-2" on a datasheet is a claim someone else verified; "DALI" on a datasheet may mean anything from fully compliant classic hardware to a loosely implemented subset.
What DALI-2 actually adds
Three additions matter in real projects. First, control devices enter the standard: the new part 103 covers application controllers, input devices (sensors, pushbuttons, sliders) and the logic that lets them behave consistently on the bus. Classic DALI had no standardized role for sensors or pushbuttons, so every vendor invented its own — which worked until you mixed brands. DALI-2 makes occupancy sensors, daylight sensors and button panels first-class, testable citizens, and adds instance-based addressing so one physical sensor can drive several logical groups.
Second, interoperability is tested, not assumed: certified devices pass standard conformance tests, and the certification program runs interoperability events where vendors' gear is exercised together. Third, more device types are standardized — extended colour control (tunable white, RGBW), emergency lighting (self-contained emergency drivers), and several part-types covering dimming behaviour more precisely — so a tunable-white specification or an emergency-and-DALI combined scheme can be written against defined parts rather than vendor promises. The EPBD-driven European controls wave leans on all three additions, which is why DALI-2 keeps appearing in EU-adjacent tenders as a de facto requirement.
Commissioning: where the difference shows up
On site, the two generations feel different long before the client reviews the result. Classic DALI commissioning leans on the master controller's own tools: discover the gear, assign short addresses, build groups and scenes by hand, and hope the vendor's panel remembers what you built. DALI-2 adds standardized discovery and instance reporting, so a certified toolchain sees sensors and drivers with consistent behaviour, and features such as emergency device testing and colour control operate through defined commands rather than vendor-specific sequences. For a single-circuit retrofit this is invisible; for a floor of a thousand devices across three brands (illustrative scale), it is the difference between a commissioning week and a commissioning month. Budget commissioning time as a line in the controls scope — it is the most commonly forgotten cost in lighting controls tenders.
Compatibility: mixing DALI and DALI-2 on one bus
The systems were designed to coexist. A DALI-2 application controller can address and command classic DALI control gear, and most classic masters can drive DALI-2 drivers for basic dimming — the underlying addressing and telegrams remain family-compatible. The caveats live at the edges: advanced features (instance-based sensor logic, extended colour, standardized emergency behaviour) only work end-to-end when every device in the chain supports the relevant part; mixed buses inherit the lowest common denominator of each feature.
So the retrofit rule is practical: adding a DALI-2 driver to an existing classic bus for plain dimming is usually fine and often the economical path; building a sensor-and-scenes scheme on a legacy bus is where projects acquire integration surprises. When we quote controls, we ask for the existing gear schedule and flag which features survive the mix before pricing, rather than after commissioning stalls.
Procurement implications: wording, certificates and cost
Tender language should be explicit. "DALI dimmable" is the weakest possible clause — it specifies a connector, not a capability. Stronger wording names the generation and the parts: "DALI-2 certified control gear, part 2xx as applicable, with DALI-2 certified input devices and application controller," plus a requirement to submit the DALI-2 certificate or listing per item with the offer. That single paragraph filters out the datasheet drift that classic-DALI projects absorbed as integration risk, and it costs nothing to include.
On price: DALI-2 certified drivers carry a modest premium over classic equivalents — commonly in the low single-digit percentage range at volume (illustrative), varying by brand and device type — and certified sensors or application controllers price against a smaller competitive field. The premium buys defined behaviour across vendors, which in multi-brand schemes is cheaper than the commissioning time it saves. For single-brand, single-function schemes, paying it is optional. As with all compliance paperwork in our offers, DALI-2 certificates and destination-market certifications are provided via certified partner factories and verified per order — the same discipline described in our certification centre.
Comparison at a glance
| Dimension | DALI (classic) | DALI-2 |
|---|---|---|
| Standard basis | Original IEC 62386 core | Restructured IEC 62386 with parts 101/102/103/2xx |
| Certification | No enforced logo program | Tested DALI-2 certification with logo |
| Sensors and pushbuttons | Vendor-specific implementations | Standardized input devices, instance addressing |
| Application controllers | Outside the standard | Defined in part 103 |
| Extended features | Varies by vendor | Standardized tunable colour, emergency, part types |
| Multi-vendor interoperability | Usually works, occasionally surprises | Tested requirement of certification |
| Relative cost (illustrative) | Baseline | Low single-digit percent premium on drivers |
| Natural use | Single-brand retrofits, simple dimming | New multi-vendor projects, sensor-rich schemes |
How to choose: three rules
- Count the brands on the bus. One brand, one function: classic DALI is fine. Two or more brands, or any sensor: DALI-2, certified, no exceptions.
- Let the features decide, not the name. Tunable white, emergency integration or scene logic via pushbuttons require the DALI-2 parts that standardize them — specify the part, not the logo alone.
- Retrofit at the edges, rebuild at the core. Adding DALI-2 drivers to a classic bus for plain dimming works; expect full feature parity only when the controller, sensors and drivers are all DALI-2.
Advice for contractors and procurement teams
Write the controls scope before the fixture schedule, because the controls decision flows upstream: sensor-rich office and education schemes push drivers, sensors and the application controller toward DALI-2, while scene-dimmed commercial fit-outs without sensors can often stay classic and bank the saving. Then hold suppliers to paper: require the DALI-2 certificate or listing per item in the offer, not a datasheet claim, and keep the bus architecture drawing (addresses, groups, instances) as a contract document so commissioning has a target.
One boundary note for smart-building clients: DALI-2 is a wired backbone, not a competitor to wireless ecosystems — it coexists with them, and gateways bridge the two where mobile control or analytics are required. Send the project type, controls scope and brand mix, and we will return DALI and DALI-2 options priced side by side, with certificate copies attached, within 24 hours.