What Does Bluetooth NLC QDID Deliver for Interoperability?
From "Mesh-capable" to "Full-Stack Interoperable" — why the Qualified Design ID is
Key Takeaway
The Qualified Design ID (QDID) is not a bureaucratic checkbox — it is the only technical guarantee that a Bluetooth NLC device is truly interoperable. Without it, even "Bluetooth Mesh" devices can become digitally stranded, unable to communicate across vendors or comply with modern building standards like EPBD 2024.
The Scenario Every Lighting Engineer Fears
Imagine this: you've successfully commissioned a large-scale wireless lighting project. The sensors are triggering, the dimming is smooth, and the energy savings are rolling in. Two years later, the project needs to expand a wing or replace a few broken devices — only to discover that the original manufacturer has changed their "flavour" of the protocol, or worse, gone out of business. Even though both the old and new devices claim to be "Bluetooth" or "Wireless Mesh," they can't talk to each other.
This is precisely where the Qualified Design ID (QDID) comes in. In the context of Bluetooth Networked Lighting Control (NLC), these identifiers are the only technical guarantee that a device has moved from "Mesh-capable" to "Full-Stack Interoperable" at the device layer.
The Evolution of Bluetooth Lighting Control
Source: Bluetooth SIG — Evolution Chart, bluetooth.com (© Bluetooth SIG, Inc. All rights reserved.)
What is Bluetooth NLC? Networked Lighting Control (NLC) is the Bluetooth SIG's open standard that adds mandatory device profiles on top of Bluetooth Mesh — defining exactly how luminaires, sensors, and controllers must behave, not just how they communicate.
The Architecture: Why Mesh Alone Wasn't Enough
Bluetooth Mesh (2017) standardised the radio and communication layers. However, it left the device layer — how a device actually behaves — largely optional. This created a market full of devices that were technically "Bluetooth Mesh" but practically incompatible without proprietary gateways or complex manual mapping.
Without NLC QDID
Interoperability is "best effort" — relying on proprietary gateways or complex manual message mapping between vendor-specific implementations.
With NLC QDID
Interoperability is "by design." A QDID-verified Basic Lightness Controller is mathematically guaranteed to understand Occupancy Sensor messages from any other NLC-certified vendor.
Bluetooth NLC solves this by introducing mandatory Mesh Device Profiles. When a product earns a QDID under an NLC profile, it confirms that the device adheres to a strict functional template — not just a radio specification.
The QDID Checklist: What Is Actually Validated?
When a design undergoes the NLC qualification process, it is tested against 500 to 1,000 specific test cases. For an engineer, this ID delivers four concrete technical guarantees:
| Feature | Technical Impact of NLC QDID |
|---|---|
| Model Mapping | Mandates specific SIG Models (e.g., Generic OnOff, Light Lightness) so devices don't need custom drivers. |
| Performance Parameters | Standardises "heartbeat" intervals and status message frequency to prevent network congestion. |
| State Consistency | Ensures that "Scenario A" on a wall switch triggers the exact same brightness level across multiple fixture brands. |
| Security Lifecycle | Validates certificate-based provisioning, preventing "trash can attacks" where credentials are leaked from decommissioned hardware. |
NLC Device Profiles: A Job Description for Hardware
Think of a Device Profile as a "job description" for a piece of hardware. While the Bluetooth Mesh protocol handles how a message travels from A to B, the Device Profile defines exactly what that message means and how the device must behave once it receives it. In NLC, these profiles move us from "it can talk" to "it knows what to say."
| Profile Code | Device Role | Reference |
|---|---|---|
| ALSNLCP | ALS Sensor (Ambient Light Sensor) | Bluetooth Mesh Sensor Server |
| BLCNLCP | Basic Lightness Controller | Bluetooth Mesh Light Fixture (LC) |
| BSSNLCP | Basic Scene Selector | Bluetooth Mesh Light Dimmer & Scene Selector |
| DICNLCP | Dimming Control | Bluetooth Mesh Light Dimmer & Scene Selector |
| ENMNLCP | Energy Monitor | Bluetooth Mesh Light Fixture (LC) |
| OCSNLCP | Occupancy Sensor | Bluetooth Mesh Sensor Server |
| HLKNLCCP | HVAC Controller | In development — Bluetooth SIG roadmap |
The Real Risk: The "Digital Dead End"
Starting in 2024, the Bluetooth SIG transitioned from the legacy QDID system to the Design Number (DN) for new qualifications. Any hardware stack that lacks a valid NLC Design Number is a technical liability.
"In the eyes of modern building standards like EPBD 2024, a non-certified device is a black box. It cannot reliably export energy data or occupancy logs to a central BACS without custom middleware."
This lack of a "standardised birth certificate" — the QDID — is what leads to stranded assets: hardware that is physically functional but digitally isolated. Buildings that depend on non-certified devices cannot meet the continuous monitoring, logging, and benchmarking requirements that EPBD 2024 mandates.
Vendor Lock-in
Non-certified devices require proprietary middleware to function — creating dependency on a single vendor's continued support.
EPBD Non-Compliance
Without standardised data export (Wh, occupancy), buildings cannot meet BACS reporting obligations under EPBD 2024.
Stranded Assets
Hardware that is physically functional but digitally isolated — unable to integrate into future-proof building ecosystems.
Frequently Asked Questions
A Qualified Design ID (QDID) is the unique identifier issued by the Bluetooth SIG when a product successfully completes its qualification process. It confirms that a specific hardware and firmware combination has been tested against the full NLC specification and is genuinely interoperable — not just "Bluetooth-capable."
Bluetooth Mesh standardises how messages travel between devices. Bluetooth NLC adds mandatory device profiles on top — defining exactly how a luminaire, sensor, or controller must behave. NLC transforms a communications protocol into a functional interoperability standard.
The QDID was the legacy identifier used by Bluetooth SIG for qualified designs. Since 2024, new qualifications receive a Design Number (DN) instead. The DN fulfils the same purpose — confirming compliance — within the updated qualification framework.
A chip vendor's QDID covers their specific hardware and firmware combination. If you modify the firmware, use a different stack configuration, or add your own application layer, you likely need to pursue your own qualification. Always verify scope with the Bluetooth SIG qualification database before assuming coverage.
EPBD 2024 mandates continuous monitoring, logging, and reporting of energy and IEQ data via a certified BACS. NLC-QDID-certified devices provide standardised, machine-readable data exports (Wh, occupancy, lux) that integrate directly into compliant BACS platforms — without custom middleware. Non-certified devices cannot reliably meet these reporting obligations.
Final Summary
Summary
The transition from proprietary mesh to NLC certification is the single most important roadmap decision for wireless lighting manufacturers today. Achieving a QDID — or Design Number — is the difference between selling a component and selling a future-proof ecosystem. In an era defined by EPBD 2024 mandates, ESG reporting obligations, and open-standard procurement requirements, a device without NLC certification is not just technically limited — it is a commercial and regulatory liability.
Explore OpenBAS NLC-Certified Solutions
From QDID-verified gateways to open-standard commissioning platforms — built for true interoperability.
Contact Us