Methodology

How compatibility records are made

Most records are built from primary documentation, not from our own testing. Every record says which kind of evidence it uses.

Research process

1. Start from the manufacturer's specifications, manuals and support pages.
2. Check each platform's own supported-device and integration documentation, certification registries such as the Matter product registry, and official integration repositories.
3. Record status, route, requirements, minimum firmware and limitations per platform, with the source and the date checked.
4. Where sources disagree, we say so and prefer the platform's own documentation for what the platform supports.

Research and drafting are tool-assisted. Every published claim is checked against the cited source by the editorial desk.

Evidence tiers

T1

Primary documentation only.

T2

Adds attributed findings from named external testers, community issue trackers or release notes. Their tests are theirs, not ours.

T3

Checked on a real device. We state the date, firmware and setup. We only describe our own experience when this record exists.

Samples

Manufacturers may send devices. A sample lets us add T3 notes and screenshots. It does not guarantee coverage, timing or a favourable status, and every sample is disclosed on the page.

Updates

Records are rechecked when something that can change the answer happens: a firmware or platform release, a certification change, a new model or a reader correction. Each record has a visible change log. We do not change dates without a real change.

Money

We may earn affiliate commissions and accept clearly labelled sponsorship formats. Nobody can buy a compatibility status, a data change, a ranking or the removal of a competitor. See the disclosure policy.

Corrections

If a record is wrong, use the contact form with the page address. Factual errors are corrected regardless of who reports them.