Editorial and review policy

HomeHubAtlas publishes two kinds of content, and we think readers deserve to know which is which.

Data-generated pages

Device pages, hub compatibility ("works with") pages, and comparison tables are generated by templates from a structured dataset. They are only as good as the data behind them, which is why the methodology page documents the source of every field — Matter certifications from the CSA's Distributed Compliance Ledger, Zigbee support from the Zigbee2MQTT project, Z-Wave support from the Z-Wave JS project, hub specs from manufacturer pages — and how compatibility between a device and a hub is determined. When the dataset refreshes, every generated page updates with it — there are no stale hand-edited copies of specifications.

Written content

Guides, hub notes, and glossary entries are written and reviewed by the site's editors. Writing may be drafted with software assistance, but every claim is checked by a person against the dataset, the published specifications (Matter, Thread, Zigbee, Z-Wave), or manufacturer documentation before publication, and each guide lists its sources. Guides carry a visible last-updated date and are re-reviewed when the underlying data or standards change.

How compatibility listings work

A device is listed as working with a hub based on the protocols and certifications in the source data: the hub's radios and controller capabilities, hand-curated from manufacturer documentation, matched against the device's certified or community-supported protocol. Price, affiliate commission, and brand relationships play no part — the dataset contains no prices, and no manufacturer can pay to appear, rank higher, or have a limitation softened.

Independence and monetization

The site may earn revenue from advertising and affiliate links, described in the affiliate disclosure. Monetization never feeds back into listings or editorial judgments: the listing code has no access to affiliate data, and editors are not compensated based on what readers buy.

Corrections

We correct errors promptly. If you find a compatibility claim that disagrees with the manufacturer's documentation, a hub spec that is out of date, or a factual error in a guide, contact us with a link to the authoritative source. Data errors are fixed in the dataset (so the fix propagates to every affected page); guide errors are corrected in place and the guide's updated date is bumped.