Original research

Original analyses built from published rubrics and public inputs, with the raw data downloadable so you can disagree with our weighting and recompute it.

The work#

How this differs from a review#

We do not run a testing lab, and we do not pretend to. What we do instead is take inputs that anyone can check (specifications, certification records, vendor documentation, release notes) and apply a stated rule to them consistently. That produces conclusions you can argue with in a useful way: if you think local voice control deserves more than ten points, you can take the dataset and reweight it in a spreadsheet in five minutes.

Three principles run through all of it, and they are set out in full on the methodology page:

  1. Inputs are facts, weights are opinions, and the two are kept separate.
  2. Unknown is not zero. Where a vendor does not document a behavior, we say so rather than scoring it as a failure.
  3. Everything is versioned and dated. A rubric change is announced, not applied silently.

The datasets#

DatasetWhat it holdsUsed by
[local_control.json](/data/local_control.json)Eight-criterion scores for seven platforms, with reasoningLocal Control Index, outage audit
[matter_gaps.json](/data/matter_gaps.json)Feature by feature controller support statesFeature gap tracker
[matter_adoption.json](/data/matter_adoption.json)Certified product counts by Matter device typeFeature gap tracker
[matter_versions.json](/data/matter_versions.json)Every Matter release with device type counts from the published data modelMatter versions
[border_routers.json](/data/border_routers.json)Every shipping Thread border router with its documented Thread versionBorder routers, finder tool
[platforms.json](/data/platforms.json)The full platform matrixPlatform comparison, picker
[channels.json](/data/channels.json)Computed 802.15.4 channel map against US Wi-Fi channelsInterference, channel planner

All seven are published under Creative Commons Attribution 4.0. Use them, adapt them, credit us with a link.

Corrections welcome#

If a score is wrong, the fastest way to change it is a link to vendor documentation showing the behavior. That gets read first and acted on. Errors we find or that readers report are logged on the corrections page.