How to check smart home compatibility before you buy (a five-minute checklist)
Updated · Reviewed against the current HomeHubAtlas dataset
Short answer: never trust the box. "Works with Alexa" tells you almost nothing about how — cloud account, bridge, or direct radio. The reliable method is the one this site's database is built on: find the exact model number, look it up in the authoritative registry for its protocol, then check your hub's radios. Five minutes, three lookups, no surprises.
Step 1 — pin down the real model number
Marketing names are many-to-one: one "smart blind motor" listing can hide six hardware revisions, and hundreds of Tuya-made devices ship identical hardware under different brands. Find the alphanumeric model on the spec sheet or the product label photo (e.g. TS0601, ZW062, MSZ-90) — that's the key every registry below is indexed by, and the reason our device pages list Zigbee model IDs and Z-Wave product IDs prominently.
Step 2 — look it up in the right registry
| If the listing says | Check | What a hit proves |
|---|---|---|
| Matter | The CSA's public Distributed Compliance Ledger | Real certification, vendor + product ID, and often the transport (Wi-Fi vs Thread — which decides if you need a border router) |
| Zigbee | Zigbee2MQTT's supported-devices database | The open-source stack has a converter for it — the strongest available signal that it speaks standard Zigbee and what its features expose |
| Z-Wave | The Z-Wave JS device database | Known device with config files — and the listing's frequency region, which must match your hub (US and EU are not interchangeable) |
| Only "works with Alexa/Google" | Nothing else on the box | Usually a Wi-Fi device bound to the maker's cloud account — fine for casual use, but no local control and no hub portability |
These three registries are exactly the sources this site's 9,530 device records come from — the methodology documents how — so the fastest version of this step is often searching the model number here and reading the verdict table.
Step 3 — check your hub's side of the handshake
- Radios. A Zigbee device needs a Zigbee radio (or bridge path); every hub page on this site lists its radios. Remember the brand-locked hubs — a Hue Bridge hit on step 2 still won't pair a third-party sensor.
- Matter controller + border router. For Matter-over-Thread devices, your ecosystem needs both a controller and a Thread border router.
- Bridged vs native. "Works with Apple Home" often means "via its own brand's bridge" — functional, but with the caveats in the bridges guide. Our glossary entry summarizes the difference.
Red flags in listings
- "Hub required" in small print — usually means the maker's own gateway, an extra purchase the headline price omits.
- Protocol soup ("Wi-Fi + Bluetooth + Zigbee 3.0!") — often means Bluetooth for setup only, and the Zigbee variant is a different SKU than the Wi-Fi one.
- No model number anywhere — on white-label marketplaces this predicts firmware quirks and zero long-term support. If it's not in any registry, assume you're the beta tester.
- "Matter-ready" or "will support Matter" — a promise, not a certification. Only a ledger entry counts.
The shortcut
Search this site for the model number: if it's in the dataset you get the full hub-by-hub verdict, sources included. If you're still choosing the hub side, start from the hub guide or a works-with page to see each hub's actual device coverage.