Methodology & data sources
HomeHubAtlas is a structured database, not a review site. Every device record and every compatibility verdict traces to a primary source, and every page shows its data. This page documents the sources, the update process, and the exact rules that produce the verdicts.
Data sources
- Matter (1824 devices): the Connectivity Standards Alliance's public Distributed Compliance Ledger (DCL) — the authoritative registry of Matter-certified products, read via its public API. Records carry vendor/product IDs, device type, commissioning flow, and certification dates. HomeHubAtlas is not endorsed by the CSA.
- Zigbee (5405 devices): the open-source Zigbee2MQTT project's device definitions (zigbee-herdsman-converters, MIT license) — vendor, model, and per-device capability data maintained by the largest Zigbee community in existence.
- Z-Wave (2311 devices): the open-source Z-Wave JS project's device configuration files (MIT license) — manufacturer, model, and product identifiers for every device the driver supports.
- Hubs (32): hand-curated from manufacturer specification pages — each hub record links its source. Radio hardware, Matter roles, and border-router status change with firmware updates; we re-verify on every dataset refresh.
Records from the three device sources are merged when they describe the same product (matching brand and model identifiers), so a device certified for Matter that also has Zigbee driver support appears once, with both protocols.
How compatibility verdicts work
Verdicts are computed from each hub's documented capabilities and each device's protocols. A device that speaks several protocols gets the best verdict any of its protocols achieves.
| Device | Hub | Verdict |
|---|---|---|
| Matter over Wi-Fi/Ethernet | Matter controller | Compatible |
| Matter over Thread | Matter controller with Thread border router | Compatible |
| Matter over Thread | Matter controller without border router | Adapter needed (border router) |
| Matter, transport unpublished | Matter controller | Compatible, with a Thread caveat noted |
| Zigbee | Open Zigbee radio | Compatible |
| Zigbee | Same-brand-only Zigbee radio | Compatible only for that brand |
| Zigbee | Zigbee via USB add-on | Adapter needed (coordinator) |
| Zigbee only | No Zigbee radio, Matter controller | Adapter needed (Matter bridge) |
| Z-Wave | Z-Wave radio | Compatible (regional frequency caveat) |
| Z-Wave | Z-Wave via USB add-on | Adapter needed (USB stick) |
| No shared protocol | — | Not compatible |
Where reality contradicts the rules — a device that pairs but loses features, or a documented exception — we record a curated override that takes precedence, with a note and source.
Known limitations
- Zigbee2MQTT support ≠ native driver parity. A device on the Zigbee list speaks standard Zigbee, and hubs with open radios will generally pair it — but the depth of native driver support (SmartThings Edge, Hubitat drivers) varies by device. The verdict notes say this explicitly.
- Matter transport is often unpublished. The DCL does not record whether a device uses Wi-Fi or Thread; where we haven't curated it, verdicts carry a Thread border-router caveat rather than a guess presented as fact.
- Firmware moves. Hub capabilities (Matter roles especially) change with updates. Each hub record links the manufacturer page it was verified against, with the retrieval date.
Updates
The dataset is regenerated from all sources on a regular schedule; every page footer's sitemap date reflects the current snapshot. Corrections are welcome — contact us with a source and we'll re-verify.
Independence
No manufacturer pays for placement, verdicts, or rankings. Revenue, when present, comes from clearly-labeled advertising and affiliate links that never influence the data — see the editorial policy and affiliate disclosure.