Matter Certification for a Combined Fan & Light Device: The Full Procedure

What a combined fan and light device is in Matter

A combined fan and light device is a Matter composed device: one physical product that exposes two independent endpoints — a fan endpoint and a light endpoint — each modelled with its own clusters, so that a controller can operate the fan and the light separately rather than treating them as a single function. The two functions share a housing, a power supply and a radio, but they do not share a data model. This is a standard device-type combination, not a custom non-standard product, which is good news: the specification already knows how to describe it.

The consequence for engineering is that "one product" and "one test subject" are no longer the same thing. A composite device accumulates the test cases of both device types and adds the interaction cases between them — which is why the firmware, not the paperwork, decides the schedule.

Glossary

Phase 1 — CSA membership and vendor ID

This is mandatory and it comes first, because nothing else can be submitted without it.

1. Join the Connectivity Standards Alliance. Certification and a VID are available to members only; the Adopter tier is the minimum level that can certify.
2. Apply for a permanent Vendor ID, which is bound to the company rather than to a product.
3. Define a Product ID for this fan-and-light model — one PID per model. If a family of similar SKUs is planned, plan the family structure now, because Product Family Certification is far cheaper than certifying each variant separately.

Membership is an annual fee and the VID does not expire with it. Budget one month for this phase if the paperwork is clean.

Phase 2 — Hardware and firmware development

This phase holds essentially all of the technical risk.

Select the wireless transport layer

The common choice for a mains-powered fan and light is Wi-Fi with Bluetooth LE, for direct compatibility with the major smart home ecosystems. Thread with Bluetooth LE is the other credible option and is well suited where a border router is already present in the home.

Whichever you pick, the transport must already be certified in the configuration you ship — Wi-Fi Alliance certification, Bluetooth SIG qualification or Thread certification. That evidence can normally be inherited from the connectivity module you buy, which is precisely why module selection deserves to be an early, deliberate decision rather than a late substitution. Without valid wireless pre-certification, Matter certification cannot proceed, regardless of how good the application code is.

Firmware development with a dual-endpoint architecture

• Endpoint 1 — fan. On/off, speed level, direction control and fan state events, exposed through the standard fan device type and its clusters.
• Endpoint 2 — light. On/off and level control as the baseline; add colour temperature or full colour control only if the product genuinely tunes colour.
• Independent control. Apple Home and Alexa must be able to operate the fan and the light separately, with no forced binding and no automatic linkage between them.
• Version choice. Implement the Matter specification version that the ecosystems in your target markets certify against today, and freeze it before generating the PICS. The specification moves; a newer version is not automatically the better-supported one, and changing version mid-project invalidates test evidence.

DAC certificate management

Every mass-produced unit needs its own DAC. The samples sent for testing must be flashed with production-grade DAC material — development-only test certificates are not accepted for official certification, because device attestation is part of what the laboratory verifies. Decide early whether the attestation chain will use an existing PKI provider or a self-operated Product Attestation Authority, since that choice affects both the certification application and the production line.

Commissioning material

Generate the Matter pairing QR code and the manual setup code, and place them on the product housing and the packaging. This is a production deliverable, not an afterthought: the code that ships on the box has to match the identity burned into the device.

In-house pre-testing

Run the product against the Matter Test Harness and the chip-tool before a single sample leaves the building. A composite device carries substantially more test cases than a standalone fan or a standalone light, so every protocol bug found at this stage is a bug you do not pay an authorized laboratory to find twice. This is comfortably the highest-return engineering time in the whole project.

Export the PICS

Complete the PICS for both endpoints, selecting every supported attribute, command and event for the fan and light clusters — and nothing else. The PICS becomes the test plan, so an over-ticked PICS buys test cases you then have to pass.

Phase 3 — Testing at an authorized test laboratory

1. Select a CSA-authorized ATL and submit the project documents together with the PICS.
2. Ship test samples — typically a minimum of three units, running DVT firmware close to the production release.
3. The laboratory runs protocol conformance testing (TIS) and interoperability testing (TRP) across the major ecosystems: Apple Home, Google Home and Amazon Alexa.
4. On failure, revise the firmware and retest until all cases pass; the ATL then issues the official test report.

Expect the test plan to probe independent control of the two endpoints, commissioning and re-commissioning, fault recovery, retention of state across a power cycle, DAC security and multi-admin behaviour — the cases that describe a real home, not a bench.

The characteristic risk on composite devices is state synchronisation between the two endpoints. If the fan endpoint and the light endpoint disagree about their reported state after a power interruption or a network drop, controllers can display a mismatched status — a light shown as on when it is off. This class of bug is invisible on a bench and obvious in a commissioning test, so deliberately exercise it in-house: pull power mid-state, drop the network, and re-commission.

Phase 4 — CSA application, review and issuance

1. Submit through the CSA certification portal: test report, PICS, product documentation, user manual, product photography and the VID/PID information.
2. The CSA reviews the documents and test records. A few weeks is the normal order of magnitude, and supplementary documents are frequently requested — plan for at least one round.
3. On approval you receive the certificate and a unique certification identifier.
4. Register the product in the Distributed Compliance Ledger so platforms can discover and validate it.
5. Matter logo usage is authorised for packaging and marketing material.

Phase 5 — After certification

• Validity. Certificates are issued with a long term — a ten-year validity is commonly cited — but confirm the current term in the certification portal rather than relying on a figure from an older project.
• Recertification. Cluster changes or a Matter version upgrade require re-certification. Minor bug fixes may qualify for a simplified change process; agree that route with the laboratory before assuming it.
• Derivative models. Where the hardware is identical and only cosmetics change, Certification by Similarity is the cheaper, faster path — and it is only available if the parent product was certified first.

Two routes to a certified product

Two things are mandatory on both routes, and no supplier can remove them: CSA membership with a VID, and full device-level testing at an authorized laboratory against your own PICS. Anyone offering to skip either one is describing something that is not Matter certification.

Indicative timeline

These are planning ranges drawn from how these projects actually run, not commitments — phases overlap in practice, and firmware maturity moves the total more than any other single factor.

Pitfall checklist

• Endpoint definition. Do not implement the fan as a sub-cluster under the light. Independent endpoints are mandatory, or controllers will not present the two functions correctly.
• PICS discipline. Do not tick clusters you will not implement — each one adds test cases. Equally, do not omit features your target market expects, because a missing required feature is a failed case, not a smaller scope.
• Safety certification is separate. Matter covers interoperability only. CE LVD and EMC, UKCA and FCC remain mandatory, and retail platforms including Amazon require them. See our compliance checklist for that track.
• Cost structure. Budget membership, laboratory testing, engineering debugging and firmware development as separate lines. Composite device testing costs more than testing a standalone light or fan, because there are more cases.
• State synchronisation. Test power-cycle and network-drop behaviour on both endpoints before submitting, not after a failure notice.

What the factory owns

Shenan Yangguang builds these products in-house: schematic and PCB design (画板), prototyping and board bring-up (打板), firmware and product R&D (研发), certification cooperation (配合认证), and mass production (大面积出货). Connectivity is integrated as a standard CSA-certified Matter connectivity module — a purchased component, selected for the transport certifications it already carries, and treated the way we treat any other purchased part. The dual-endpoint application firmware, the enclosure, the optical design and the certification are ours.

That is the important distinction for a brand evaluating a supplier. Inheriting a module's certification is engineering, not outsourcing: the vendor ID, the PICS, the DAC chain and the certification identifier belong to the party that built and tested the finished device — and they have to survive every firmware upgrade the product receives.