Methodology & Review Console Sources, review gates, freshness, and stated limits
Public editorial policy
Methodology & review policy
How a compatibility answer is researched, reviewed, and dated.
Smart-home compatibility gets confusing where standards, ecosystems, firmware versions, and device features overlap. This page explains how those answers are built, what review they pass, and — just as importantly — what they do not claim.
How we research
Four habits behind every compatibility note.
The goal is a narrow, practical answer: what works, where it works, what is still uncertain, and when the evidence was last checked. These habits keep that answer honest as ecosystems change.
Start from primary sources
Manufacturer pages, standards-body release notes, and official ecosystem documentation come before blogs, roundups, or summaries.
Label community signals
Forum and Reddit reports can surface real friction, but they stay marked as unverified signal until a primary or secondary source confirms them.
Separate fact from caveat
Firmware version, region, setup path, and ecosystem limits are recorded as their own fields, not folded into a single "compatible" label.
Date every answer
Each claim carries the date it was checked and the next recheck date, so a reader can judge whether it is still current.
How to read an answer
What each field on a compatibility row means.
A single "compatible" badge hides the parts that actually trip people up. Public answers are broken into fields so a reader can see what is known, how strong the evidence is, and where the caveats live.
01 Support status
Whether standard, radio, or ecosystem support is present — stated only at the level the source actually confirms.
02 Feature behavior
Which specific controls appear after pairing, because a device can be "supported" yet lose features inside one ecosystem.
03 Known caveats
Firmware, region, border-router, bridge path, or controller limits that can change the answer in a real home.
04 Source and date
The public page or document behind a claim, plus the date it was last checked.
05 Confidence
High, medium, or low, reflecting how directly the evidence supports the exact claim.
06 Review state
Whether a row is still in research or has cleared the review route on this page.
Review route
No compatibility verdict ships from a single author.
Before a model-level claim becomes reader-facing guidance, it moves through review for evidence, accuracy, editorial clarity, legal and platform policy, monetization risk, and a final human sign-off. A claim that fails any gate stays in research instead of going live.
- Compatibility research
- Fact check
- Editorial quality
- Legal and platform policy
- Monetization risk
- CEO / Andy approval
Stated limits
What these pages do not claim.
Being useful means being clear about the edges. The following limits apply across the site unless a specific page links direct evidence to the contrary.
We do not test devices ourselves
Pages are compiled from cited public sources. We do not claim hands-on testing, teardown, or signal measurement unless a page explicitly links that evidence.
Describing a standard is not certifying a product
Naming or explaining a standard such as Matter or Thread does not certify any device. Certification comes from the relevant standards body, not from this site.
No platform or maker affiliation
Brand and standard names identify the systems being researched. They do not imply affiliation, endorsement, or access to private compatibility data.
A researched read, not a promise
Compatibility can depend on firmware, region, and setup. A source-backed answer is a best current read, not a guarantee that a device will work in every home or every configuration.
General information, not legal advice
Disclosure, privacy, and policy notes describe how this site operates. They are general information and not legal, financial, or professional advice.
Related policy
Read these alongside the methodology.
Corrections and source pointers are welcome. If a claim looks stale or wrong, the contact page is the fastest way to flag it for recheck.