Does Zigbee replace radio certification (RED, FCC)?

No. Zigbee is a network and application stack that runs on top of the IEEE 802.15.4 physical layer, most often in the 2.4 GHz band. The underlying radio link still has to clear the usual regulatory regimes: EN 300 328 for RED in Europe, FCC Part 15.247 in the US, plus national regimes for the 868 or 915 MHz sub-GHz variants. CSA Zigbee certification sits on top, it does not substitute for any regulatory regime.

Are Zigbee and Matter the same certification?

No, even though both programs have been operated by the CSA since the 2021 rebrand. Zigbee and Matter are two distinct specifications, two distinct test plans, two distinct certification entries. Matter runs on IP (Wi-Fi or Thread), Zigbee does not run on IP. A product that speaks both Zigbee and Matter has to be certified twice. Zigbee-to-Matter bridges are a frequent case that additionally requires bridge logic, certified on the Matter side.

What is the difference between Adopter, Participant and Promoter?

These are the three CSA membership tiers. Adopter is the minimum tier to certify a Zigbee product, gain access to the specifications and use the logo. Participant adds access to the technical working groups. Promoter holds a seat on the board and orients the roadmap. Annual fees scale accordingly, refer to the CSA pricing page for current amounts.

Can Zigbee and Thread coexist on the same SoC?

Yes. Zigbee and Thread are two application stacks on the same IEEE 802.15.4 physical layer at 2.4 GHz. Most modern SoCs (Silicon Labs EFR32MG, Nordic nRF52840 and nRF54, Espressif ESP32-H2/C6, NXP K32W and RW61x, Texas Instruments CC2652/CC2674) support both stacks, often as concurrent dual-stack or as switched modes. Each stack is certified independently in its own program.

Does a pre-certified Zigbee module have to be recertified?

Not at the Zigbee layer if the module is used without modification of the stack firmware and if the certified firmware is shipped as delivered. The host product then inherits the module certification for the Zigbee stack. The host product still has to clear its own radio regulatory conformance, and any modification of the Zigbee firmware (cluster extensions, different Zigbee version, MSC) triggers a partial recertification at minimum.

Does the MSC cluster let me step outside the Zigbee spec?

The Manufacturer Specific Cluster (MSC) is a mechanism provided by the Zigbee spec to expose proprietary features outside the standardised clusters. It remains framed by the spec, its use has to be declared at certification time, and it does not waive the correct implementation of the standard clusters required by the device profile. A product that relies mostly on MSC to bypass the standard clusters typically fails the ATL test plan.

Is Zigbee Green Power automatic for any Zigbee device?

No. Zigbee Green Power is a spec extension for energy-harvesting devices (self-powered switches, batteryless sensors). It introduces a commissioning and exchange scheme different from classical Zigbee commissioning. A Green Power product has to declare that profile and pass an adapted test plan, forgetting it is a frequent cause of ATL return on energy-harvesting products.

Is a sub-GHz Zigbee variant (868/915 MHz) common?

Zigbee is defined over the 2.4 GHz, 868 MHz (Europe) and 915 MHz (North America) bands. In practice the overwhelming majority of deployed devices use 2.4 GHz, and the sub-GHz variants known as Zigbee PRO sub-GHz remain marginal. The associated regulatory regimes are different (EN 300 220 for European sub-GHz instead of EN 300 328), which must be scoped very early in the project.

Zigbee + CSA: certification of the 802.15.4 mesh protocol

Author Hugues Orgitello Last updated 27 May 2026 ~13 min read

Guide · Zigbee / CSA

Zigbee holds a singular place in the history of wireless home automation. Older than Thread, older than Matter, built on the IEEE 802.15.4 physical layer at 2.4 GHz, the mesh protocol has outlived more than twenty years of announced successors. Zigbee certification is now operated by the Connectivity Standards Alliance, whose very name still carries a trace of the founding standard. This page describes the exact scope of Zigbee certification, its active versions, how it interacts with the two other programs operated by the CSA (Thread is not one of them, Matter is), and the recurring pitfalls observed on first submissions, in particular the structural confusion between Zigbee and Matter.

A history in three acts

The Zigbee program began in 2002 with the founding of the Zigbee Alliance, an industrial consortium built around the then-finalising IEEE 802.15.4 specification. The first public Zigbee specification dates from 2004, followed by major iterations Zigbee 2006, Zigbee PRO 2007, then a convergence of profiles under Zigbee 3.0 in 2016. In 2021 the Zigbee Alliance was renamed Connectivity Standards Alliance on the occasion of the Matter launch, which became the organisation's second flagship standard. The rebrand did not retire Zigbee: the specifications continue to evolve, with Zigbee PRO 2023 and Zigbee Direct both released under the new CSA name.

What this history implies for certification:

The Zigbee logo and the Zigbee certification program belong to the CSA, exactly like the Matter logo and program.
CSA membership grants access to both programs, with a distinct certification dossier for each.
Historic resources (test plans, cluster documentation, lists of modules certified before the rebrand) remain accessible, sometimes redirected from the old Zigbee Alliance portal to the CSA portal.

What Zigbee is, and what it is not

Zigbee is a low-power application and network stack, designed for the mesh of domestic and industrial sensors and actuators. Three layers structure the stack on top of the 802.15.4 PHY provided by the radio SoC:

Layer	Zigbee	Role
Application	Profiles + clusters (ZCL, Zigbee Cluster Library)	Define functional behaviour (lighting, plugs, sensors, energy metering, etc.)
Network	NWK (mesh routing, AODV-like)	Mesh routing between coordinator, routers and end-devices
MAC	IEEE 802.15.4 MAC	Channel access, CSMA/CA, beacons
PHY	IEEE 802.15.4 PHY (2.4 GHz, 868 MHz, 915 MHz)	Low-rate radio (typ. 250 kbps at 2.4 GHz)

Three properties define Zigbee:

Mesh as native topology. Any Zigbee router relays the traffic of neighbouring end-devices, extending the logical reach of the network far beyond the radio range of a single node.
No IP. Unlike Thread and Matter, Zigbee does not run over IPv6. Zigbee addresses are 16-bit short addresses internal to the network, and any bridge to IP requires a dedicated gateway (Zigbee gateway, sometimes Zigbee bridge).
An application profile that standardises the interpretation of messages. This last point is central: two Zigbee devices may share the same network stack and still fail to interoperate if their application profiles do not overlap.

Zigbee does not define a new radio. The 802.15.4 layer it uses is the same as Thread, which makes dual-stack possible on nearly every SoC on the market.

Active Zigbee specifications

The Zigbee program has gone through several versions, some of which still coexist in the deployed base:

Version	Year	Status	Notes
Zigbee 2004 / 2006	2004 / 2006	Historic	Original profiles, no longer used in active certification
Zigbee PRO 2007	2007	Historic baseline	Introduced stochastic mesh, basis of most later stacks
Zigbee 3.0	2016	Main reference in deployment	Convergence of earlier profiles (HA, ZLL, partial ZSE) under a single stack, unified commissioning
Zigbee PRO 2017	2017	PRO update	Security and routing improvements
Zigbee PRO 2023	2023	Active evolution	Security and mesh performance reinforcements
Zigbee Direct	2023	Extension	Direct connection of a BLE-equipped device (smartphone) to a Zigbee network via a BLE proxy, simplifies commissioning
Zigbee Green Power	Ongoing extension	Active extension	Energy-harvesting devices, specific commissioning scheme

Certification is awarded against a specific specification version. A Zigbee 3.0 test plan is not equivalent to a Zigbee PRO 2023 test plan, and migration between versions may trigger a partial recertification, or a full one depending on the scope of changes.

Profiles and clusters

Zigbee interoperability rests entirely on application-layer alignment. The Zigbee Cluster Library (ZCL) describes standardised clusters (for example OnOff, LevelControl, ColorControl, Thermostat, OccupancySensing) that devices implement according to their function.

Historical profiles consolidated under Zigbee 3.0:

ZHA (Zigbee Home Automation): historic home-automation profile for lighting, plugs, sensors, thermostats, locks. Became the baseline of Zigbee 3.0.
ZLL (Zigbee Light Link): colour-lighting profile. Also folded into Zigbee 3.0.
ZSE (Zigbee Smart Energy): utilities profile for metering and energy management. Retains a separate cycle in some countries for regulatory utility reasons.
Zigbee Building Automation: commercial / building profile.
Zigbee Retail Services, Zigbee Health Care, Zigbee Telecom Services: more marginal vertical profiles.

Under Zigbee 3.0 and then Zigbee PRO 2023, most consumer products rely on the extended ZCL rather than on the older named profiles. For specific needs not covered by standard clusters, the spec defines the Manufacturer Specific Cluster (MSC), tied to a Manufacturer Code assigned by the CSA.

MSC use remains framed by the spec and must be declared at certification time. It does not waive the correct implementation of the standard clusters required by the device profile. A product that bypasses the standard clusters through MSC typically fails the ATL interoperability test plan.

Place in the certification stack

For a Zigbee 3.0 product launched in both the EU and the US, the minimum certification stack looks like this:

Regime	Scope	Required when...
CE marking + RED	EMC, safety, spectrum (3.2), cybersecurity (3.3)	Placed on the EU market
FCC Part 15 (15.247 at 2.4 GHz)	Intentional radiators	Placed on the US market
CSA Zigbee	Stack + profile + cluster conformance	Zigbee logo used, interoperability asserted
CSA Matter	Distinct from Zigbee, see Matter certification	The product also speaks Matter (in addition or as a bridge)
Thread Group	Distinct from Zigbee, see Thread Group	The product also uses Thread
Bluetooth SIG	Bluetooth SIG qualification	Zigbee Direct BLE commissioning

None of these regimes substitutes for another. See RED procedure and FCC scope for the underlying radio regimes.

CSA membership, the three tiers

Access to the Zigbee program goes through CSA membership, exactly as for Matter:

Adopter: minimum tier to certify a Zigbee product, obtain the Manufacturer Code, download the full specifications and use the certified Zigbee logo. Sufficient for the majority of manufacturers shipping directly.
Participant: adds access to the technical working groups (Zigbee Working Group, ZCL evolution, drafts) and to enhanced support channels.
Promoter: holds a seat on the CSA board, orients the roadmap and strategic positioning. Reserved for major actors.

Annual fees scale at each tier. Exact amounts evolve and must be confirmed with the CSA, the public pricing page remains the only up-to-date reference. A project budgeting Zigbee must include the annual membership fee on top of per-product certification fees.

Certification process, step by step

The standard path of a Zigbee project, from design to listing on the CSA certified products page:

CSA membership at the Adopter tier as a minimum. Obtain the Zigbee Manufacturer Code.
Choose the target spec version (typically Zigbee 3.0 or Zigbee PRO 2023) and the target application profile.
Design and implementation of the stack, in practice on top of a silicon vendor SDK (Silicon Labs Z3GatewayApp and Gecko SDK, Nordic nRF Connect SDK Zigbee, Espressif ESP-Zigbee-SDK, NXP MCUXpresso Zigbee, Texas Instruments Z-Stack).
Internal pre-test of declared clusters: attribute read/write, command responses, correct report generation, network behaviour (rejoin, coordinator loss, etc.).
Conformance declaration to the application profile and to mandatory/optional clusters. Exhaustive list of any MSC with its semantics.
Select an Authorized Test Lab (ATL) from the CSA list. Submit the product, the target spec and the accompanying dossier.
Execute the test plan at the ATL: spec conformance, cluster conformance, interoperability with reference Zigbee certified devices, network robustness.
CSA review of the test report. Possible clarification requests.
Certification decision and listing of the product on the CSA public certified-products page.
Place on the market with the certified Zigbee logo applied.

Exact durations vary and must be confirmed with the chosen ATL, but industrial experience puts a first-time certification at several weeks to several months between ATL engagement and listing on the public page.

Pre-certified modules, the industrial lever

The fastest path to Zigbee certification, especially for a secondary product or moderate volume, is the reuse of a radio module already Zigbee-certified by its vendor. Silicon vendors typically offer:

An RF module with integrated antenna and Zigbee stack pre-certified at a given version (often Zigbee 3.0).
A reference firmware that implements a fixed set of clusters.
A reusable certification dossier, subject to no modification of the stack firmware.

The host product then inherits the module certification at the Zigbee layer, provided the integration respects the vendor's constraints (power, antenna, layout, EMC requirements). On the other hand:

Radio regulatory conformance (RED, FCC) of the host product is not always inherited automatically, it is often partially inherited (FCC modular approval, for example) but must be verified case by case.
Any modification of the Zigbee firmware (cluster extensions, MSC additions, different version) breaks the inheritance and triggers a product recertification.

Zigbee, Thread and Matter, who does what

The Zigbee / Thread / Matter triplet generates the bulk of confusion on first IoT projects. The following table clarifies:

Criterion	Zigbee	Thread	Matter
Layer	Application + network + MAC + 802.15.4 PHY	Network (6LoWPAN, IPv6) + MAC + 802.15.4 PHY	Application on IP (Thread or Wi-Fi), BLE for commissioning
Radio band	2.4 GHz mainly, 868/915 MHz minor	2.4 GHz	Wi-Fi 2.4/5/6 GHz + Thread 2.4 GHz
IPv6	No	Yes	Yes (uses Thread or Wi-Fi as IP transport)
Certification operator	CSA	Thread Group	CSA
Logo	Zigbee certified logo	Thread certified logo	Matter logo
Dual-stack on same SoC	Yes with Thread (same 802.15.4)	Yes with Zigbee	Yes on Wi-Fi+BLE or Thread+BLE depending on the port
Bridging to the others	Zigbee-to-Matter bridge frequent	Thread Border Router to expose to Matter ecosystems	Native hub

A few practical implications:

A modern 802.15.4 SoC (Silicon Labs EFR32, Nordic nRF52840/54, Espressif ESP32-H2/C6, NXP K32W, TI CC2652) can run Zigbee or Thread, sometimes both concurrently (dual-stack). The choice is made at firmware level and drives the certification stack to clear.
A product that wants to be both Zigbee and Matter has to be certified twice, in two distinct CSA programs, with two distinct test plans.
A Zigbee-to-Matter gateway (frequent case to expose a historic Zigbee fleet to Matter) has to clear Matter certification for the bridge, on top of Zigbee for the 802.15.4 side.
Major consumer smart-home ecosystems (Apple Home, Google Home, Amazon Alexa, Samsung SmartThings) consume Matter as the interoperability layer. Zigbee remains massively supported by proprietary hubs (Hue, Aqara, IKEA, SmartThings v1, etc.) but is not an interoperability protocol with native Matter ecosystems without a bridge.

Underlying radio conformance

Zigbee at 2.4 GHz falls under the same radio regimes as any other transmission in that band:

Europe: RED article 3.2, harmonised standard EN 300 328 for 2.4 GHz wideband emitters. See RED procedure.
United States: FCC Part 15.247 for DSSS/FHSS emitters in the 2.4 GHz ISM band, modular approval available for certified modules. See FCC scope.
Sub-GHz Zigbee (868 MHz Europe, 915 MHz North America): distinct regime, EN 300 220 in Europe, FCC Part 15.249/247 by sub-band. Commercial penetration of sub-GHz Zigbee remains minority, but can fit long-range low-rate use cases.

CSA Zigbee certification covers none of these radio regulatory aspects. The two dossiers are built in parallel.

Zigbee Direct and BLE commissioning

Zigbee Direct is a more recent extension that simplifies Zigbee commissioning from a smartphone. Rather than using a dedicated Zigbee coordinator to add a device, Zigbee Direct lets a BLE-equipped device (typically a smartphone) serve as a BLE proxy into the Zigbee network through a proxy device in the network.

Implications for certification:

The BLE link of Zigbee Direct adds to the scope. Its SIG qualification and radio conformance must be treated as for any other BLE link, see Bluetooth SIG qualification.
The Zigbee Direct profile is declared at CSA certification time and triggers an extended test plan.
A product that does not support Zigbee Direct is unaffected, but must then define its commissioning flow clearly (dedicated coordinator, residual Touchlink, install code, etc.).

Zigbee Green Power, the often-forgotten topic

Zigbee Green Power (ZGP) is an extension for energy-harvesting devices: self-powered switches (Enocean-like), batteryless sensors, devices powered by solar cell or piezo-electric effect. ZGP introduces a communication scheme distinct from classical Zigbee, optimised for short and infrequent frames emitted without prior negotiation.

Implications:

A ZGP device has to declare that profile at certification time and pass an adapted test plan.
A product marketed as "energy-harvesting Zigbee" without implementing ZGP will typically be returned by the ATL.
On the network side, Zigbee proxies that must relay ZGP traffic also have to support and declare that capability.

Recurring pitfalls

The most frequent non-conformities on first Zigbee submissions, as reported by ATLs and community feedback:

Conflating Zigbee and Matter. Both programs are operated by the CSA, but they are two specifications, two test plans, two distinct entries. A Matter certification grants no Zigbee credit, and vice versa.
Thinking Thread Group equals Zigbee. Same 802.15.4 physical layer, different certification programs (Thread Group on one side, CSA on the other), different specs above the PHY. A Thread certification grants no Zigbee credit.
Forgetting mandatory profile clusters. Each application profile (lighting, plug, occupancy sensor, etc.) imposes a subset of mandatory clusters and attributes. A product that does not implement them all fails the test plan, even if business functionality looks covered through other clusters or through MSC.
Using MSC to bypass standard clusters. MSC is legitimate for extensions, not for replacing mandatory clusters. A dossier mostly relying on MSC is typically returned for revision.
Not declaring Zigbee Green Power on an energy-harvesting product. Frequent error on batteryless sensors, results in a product that works on the bench but is not certifiable.
Migrating to Zigbee PRO 2023 without recertification. A major spec update changes the applicable test plan. A Zigbee 3.0 certified product does not automatically become Zigbee PRO 2023, the recertification procedure must be engaged.
Underestimating the Zigbee-to-Matter bridge. Many teams think exposing a Zigbee fleet to Matter is just "opening Matter" on the gateway. It is in practice a Matter product in its own right, with its own DAC, its own VID/PID and its own Matter certification.
Reusing a pre-certified module while modifying the Zigbee stack. Module certification inheritance breaks as soon as the stack firmware is modified. The vendor stack has to be used as delivered, otherwise the product is in fact to be recertified.
Ignoring radio regulatory conformance. CSA Zigbee certification gives no assurance of RED or FCC conformance. Both dossiers are built in parallel, and a Zigbee-certified product that fails EN 300 328 or FCC Part 15.247 remains banned from market placement.

Costs, what can be stated without inventing

CSA fees evolve frequently and cannot be quoted here reliably. Refer directly to the CSA pricing page for current amounts. Typical cost items in a Zigbee project are:

Annual CSA membership (Adopter at minimum), tiered by manufacturer revenue.
Per-product certification fees, invoiced by the CSA on submission.
ATL fee for executing the test plan, billed by the lab and dependent on profile complexity and number of declared clusters.
Cost of the pre-certified Zigbee module where applicable, which can save a substantial fraction of certification fees but adds a unit cost.
Radio regulatory conformance in parallel (RED, FCC, national regimes), comparable to other 2.4 GHz regimes.
Partial recertifications to anticipate when migrating Zigbee versions or adding clusters.

For a cross-cutting view of certification budgets, see certification costs.

See the certification glossary for the precise definition of ZCL, MSC, PAN, NWK, ZSE, ZHA and Zigbee Green Power.

Operational summary

For a Zigbee product to reach the market under the CSA logo, six cumulative conditions must hold:

The manufacturer is a CSA member and holds a Zigbee Manufacturer Code.
The product targets a precise spec version (typically Zigbee 3.0 or Zigbee PRO 2023), with an identified application profile.
All mandatory clusters of the profile are implemented according to the ZCL, any MSC is declared and documented.
The test plan matching the version and profile has been passed at a listed ATL, possibly reduced by inheritance from a pre-certified module.
Underlying radio regulatory conformance is handled in parallel (RED EN 300 328 in the EU, FCC Part 15.247 in the US for 2.4 GHz; specific sub-bands for sub-GHz).
If the product must interoperate with Matter ecosystems, a distinct Matter certification is engaged, either for the product itself or for the Zigbee-to-Matter gateway.

Missing any one of these conditions is enough to block use of the Zigbee logo, and depending on the defect, may also block the interoperability asserted by the manufacturer.