We learned this firsthand when we tried to integrate our first A-Sample of an NLC (Networked Lighting Control) node into the Silvair platform — one of the most reputable commercial Bluetooth Mesh platforms for professional lighting control. What started as a promising beginning quickly turned into a valuable lesson about the realities of industrial certification.

A Strong Start: Testing with Silicon Labs and Nordic Semiconductor

Both Silicon Labs and Nordic Semiconductor offer free mobile apps that let you test NLC functionality straight from your phone:

• Silicon Labs: Bluetooth Mesh by Silicon Labs (Android / iOS)
• Nordic Semiconductor: nRF Mesh (Android / iOS)

Our first tests with the A-Sample went surprisingly well. Commissioning, on/off control, dimming — everything worked. Even more impressive: cross-ecosystem interoperability held up. A node developed with Silicon Labs' stack was successfully commissioned and controlled via the nRF Mesh app. That felt like a solid foundation to build on.

Stepping Into Reality: Integration with the Silvair Platform

Silvair was kind enough to support us — together with our development partner — in integrating our NLC nodes into their platform. The goal was to run our uncertified nodes alongside already-qualified NLC motion sensors in a real Silvair environment.

The results were sobering — and eye-opening.

Why Free SDKs Alone Are Not Enough

This is the core takeaway: Bluetooth SIG Qualification is mandatory — and for good reason.

The free SDKs from Silicon Labs (Simplicity SDK) and Nordic Semiconductor (nRF Connect SDK) are technically excellent, and both companies offer them at no cost deliberately — as a way to make their chips more attractive to developers. Only the hardware itself and the certification process carry a price tag. The logic is straightforward: the faster and easier a developer can work with a stack, the more likely that chip ends up in the final product.

That's completely legitimate — and for prototypes and early functional testing, it's more than sufficient.

Small deviations in how a Bluetooth Mesh stack is implemented, subtle timing differences, requirements from the specification that aren't fully met — none of these show up in an isolated test app. But they surface immediately in a production-grade platform.

The QDID: The One Number That Actually Matters

There's one concept that sits at the center of all of this, and it's worth understanding clearly: the QDID — Qualified Design ID.

When a product successfully completes the Bluetooth SIG qualification process, it receives a QDID. This is essentially the proof of record that a specific design has been tested, reviewed, and officially recognized as compliant with the Bluetooth specification. It's not just a certificate on paper — it's a traceable, searchable identifier in the Bluetooth SIG's public qualification database.

Supply Chain Implications

The QDID also has practical implications for the supply chain. If you're designing a product that incorporates a third-party Bluetooth stack or chipset, you need to check whether the chip vendor's existing QDID covers your use case and product configuration — or whether you need to pursue your own qualification. Using a chip with an existing QDID is a starting point, but it doesn't automatically make your end product qualified.

What This Means for Your Development Process

For anyone on a similar path: the free development tools from Silicon Labs and Nordic Semiconductor are an excellent starting point. They enable rapid prototyping, solid early interoperability checks, and a real understanding of the NLC architecture.

But the moment your target is integration into a certified, commercial platform — whether Silvair or any other — official Bluetooth SIG Qualification is non-negotiable. It's not just a bureaucratic checkbox. It's the actual quality gate that ensures a node will perform reliably under real-world conditions.

Our A-Sample showed us exactly where we still need to do the work. That's uncomfortable — but it's precisely what early sampling phases are for.

The Bottom Line

Have you had similar experiences with NLC development or Bluetooth Mesh certification? We'd love to hear from you.