About Hardware Matrix
An open index of 177 device-and-platform pairings: protocols, logic levels, wiring notes, reset sequences and compatibility verdicts — compiled from published documentation, and honest about where that leaves gaps.
What this is
The consumer smart home landscape is fragmented by inconsistent radio implementations, undocumented GPIO assignments and hidden cloud dependencies. Hardware Matrix is an open index for hardware builders, home automation users and tinkerers: one page per device-and-platform pairing, saying what it speaks, what it needs, and what has to be true before it works.
The fields it tracks are the ones a product page tends to leave out — 3.3V versus 5V logic tolerance, whether a bridge or border router is required, the factory reset sequence, which entities an integration actually exposes, and whether the thing keeps working with the internet unplugged.
How an entry is compiled
Where the numbers come from, and what checks them
Published documentation first
Manufacturer datasheets and product pages, integration documentation (ZHA, Zigbee2MQTT, Z-Wave JS, ESPHome, Matter), and community reports. Where a figure has a specific published source, the page names it — 20 of 177 entries currently carry one.
One vocabulary, not forty
Verdicts come from a fixed set of three — natively supported, bridge needed, or compatible with manual configuration — derived from the record rather than written by hand. Protocol spellings are normalised, and near-duplicate entries for the same part are merged into one page with variants.
A validator that blocks the deploy
Every build runs a dataset validator that fails on the specific mistakes this project has already made: spec strings invented from a device's name, safety flags guessed by keyword match, FAQ answers filed under the wrong question, a verdict badge that contradicts the paragraph beneath it. Separately — it needs a Python toolchain the deploy image does not carry — every ESPHome configuration here is put through ESPHome's own validator before it is added or changed.
Field reports beat our guesses
Every device page carries a correction form that opens an issue against the repository. A reset sequence that does not work, an entity that never appears or a verdict that does not match what you see on your own network is the most useful thing anyone can send us.
What this is not
- Not lab tested. No device here has been bench tested by us. Nothing on this site measures pairing time, radio range or response latency, and no page should be read as if it had.
- Not a substitute for the manufacturer's documentation. Confirm terminal assignments, voltages and current limits against the datasheet before you wire anything — particularly on the mains-voltage entries, which are flagged as such.
- Not a live compatibility feed. Integrations change. An entry reflects the documentation as read on the date shown in the footer, not the state of a platform's latest release.
- Not exhaustive. Fields with no sourced value are left empty rather than filled with a plausible-looking number. An empty field means we do not know.
Help expand the matrix
Run a device that is not indexed here, or found an entry that does not match what your own network does? Both are worth sending — the second one more than the first.