1.Two kinds of statement, and which one you are reading
Every compatibility statement on this site is one of two things. We keep them apart because collapsing them is how stores end up claiming tests they never ran.
Documented
The manufacturer’s own documentation states it — protocol, hub requirement, voltage, ecosystem support. We are repeating their claim, not testing it, and the page says so.
Tested
We paired the unit ourselves and recorded the hub model, the hub firmware and the date. This is the only kind that lets us write “verified”.
As of 2026-11-04, no product page on this site carries a Tested record. See section 5 for what that means in practice — we would rather write it here than let you assume otherwise.
2.The four checks
These apply to every device before it is listed. They are ordered: a device that fails C1 is not carried forward to C2.
| Check | Looks at | If it fails |
|---|---|---|
| C1 | Identity and certification.Manufacturer, model number and the certificate ID behind any certification claim: Matter VID/PID (CSA Distributed Compliance Ledger), FCC ID, or an EU/UK notified-body number. | No certificate ID means no certification claim — no logo, no badge, and the word “certified” does not appear. |
| C2 | Radio and power.The protocol comes from the manufacturer’s specification sheet, together with the voltage, plug type and mounting dimensions for the market we ship to. | A device whose radio or power we cannot pin down is not listed. |
| C3 | Hub dependency.A yes or no, and when yes, at least one named hub model with the firmware range we know it works on. | The page says the hub requirement is unconfirmed, and makes no claim about any ecosystem. |
| C4 | Ecosystem status.One of three values per ecosystem — native, via hub, or unsupported — never a fourth value like “works with”. | An ecosystem we have not checked stays blank rather than defaulting to compatible. |
3.Three status values — and no fourth
Compatibility is not a yes/no question, and the usual answer (“works with everything”) is the least useful one. Every ecosystem cell on this site holds one of three values:
| Value | What it means |
|---|---|
| native | Pairs directly with that ecosystem. No bridge, no vendor cloud account required for basic control. |
| via hub | Pairs only through a specific hub. The hub model and firmware are named on the product page, not just “a compatible hub”. |
| unsupported | Does not pair. We print this rather than leaving the cell empty — “unknown” and “no” are different answers, and only one of them is useful to you. |
The most useful thing a compatibility page can say is often “no”. A device that does not pair with Apple Home will never be described here as broadly compatible “with an app”.
4.How long a claim stays valid
A compatibility statement is a snapshot of a specific firmware on a specific hub. It goes stale on its own, so it expires on its own:
- Every statement carries the date it was last checked, and that date is visible to you.
- Older than 180 days: the claim is shown as unverified with the date it was last checked, and the compatibility status is removed from the machine-readable data — so a search engine cannot repeat a claim we have stopped standing behind.
- Older than 365 days: a review notice appears at the top of the product page.
- Quarterly: every SKU is listed for re-check, oldest first. The list is not optional housekeeping — it is the only thing that stops a catalogue from quietly rotting.
5.What we have not verified
Written down so that you do not have to guess, and so that we cannot quietly forget it:
- No physical pairing test has been recorded for any SKU. Every compatibility statement you can read today is Documented, not Tested. We use the words “verified” and “guaranteed” nowhere on this site until that changes.
- We do not hold a CSA Distributed Compliance Ledger record for the Matter SKUs, which is why no page shows the Matter logo or the word “certified”.
- We have not yet published a confirmed model number for every SKU. Where we have not, the listing does not invent one.
The next step is a bench: one unit of each SKU, the hubs we name, and a written record per pairing. When the first record exists it will be dated on the product page, and this section will say so.
6.A case we got wrong
Duo Centre-Closing Track Kit. For several weeks the page led with “native Matter, no hub” and stopped there. That is true of the Thread variant. The same product is also sold with a Zigbee 3.0 radio at $20 less — and that one needs a Zigbee hub, because it is not a Matter device at all.
The variant selector said “Zigbee 3.0” and the specification table listed both radios in one line. Nothing was factually false; the hub requirement was simply hidden behind a variant label and a slash. A shopper who picked the cheaper option could reasonably have expected it to pair the way the headline said.
First fix, 2026-11-04: state the hub requirement on each variant and in the specification table. Final fix, the same day: split it into two SKUs, one per radio. Compatibility facts live at SKU level — a single SKU can carry only one hub requirement, one protocol list and one verification date, so no amount of careful variant wording could make one record describe two different radios. The Thread kit kept its original SKU and address; the Zigbee kit has its own. The cause was not a typo — it was describing a product by its best variant.
7.Check our claims yourself
Nothing here asks you to take our word for it. These are the sources we use:
- Matter — the CSA Distributed Compliance Ledger, searchable by vendor and product ID. Ask us for the VID/PID of any SKU and we will send it, or tell you we do not have it.
- FCC — the FCC ID database (fcc.gov/oet/ea/fccid). An ID we cannot point you to is an ID we do not have.
- CE / UKCA — the EU NANDO register and the UK designated-standards lists, by notified-body number.
- Specification sheets — ask for the manufacturer’s PDF for any product. If we cannot produce one, that is a gap in our records, not a secret.
8.Corrections
Email matrixgrowth@foxmail.com with the product URL and the claim you think is wrong. We answer within three business days. A correction is published on the page within one business day of us confirming it, and written into the editorial log with the date. We would rather be corrected in public than be right in private.
Kunsmart is operated by Beijing Matrix Growth Technology Co., Ltd.. The selection rules behind these checks are on our editorial policy.