How We Verify
This page exists so a Confirmed, Workaround, or Investigating label can actually be checked, not just trusted on faith. It explains the status system, what we cite, and the boundary on safety and recall claims.
The status system
- Confirmed
- Independently tested or checked against the specific device, hub, and ecosystem combination described, as of the verification date shown.
- Workaround
- Resolves the symptom in practice, but relies on a non-standard step, a bridging limitation, or a configuration outside the manufacturer's documented path.
- Investigating
- A reported symptom or compatibility question without a confirmed resolution yet — an honest "we don't know for certain" instead of a guess presented as fact.
Primary sources and sourcing boundaries
Certification and standard claims are checked against primary registries: the CSA-IOT certified products database (Matter, Zigbee), the Z-Wave Alliance certified product catalog, and Home Assistant's certified and integration directories. Recall or safety status is sourced only from CPSC/SaferProducts.gov — never from forum inference, and never implied when no official notice exists.
No single external source tracks cross-ecosystem interoperability (e.g. a specific Zigbee lock, bridged through a specific hub, under Matter, on a specific firmware). That synthesis is our own testing, disclosed with a test date and configuration wherever possible, not a citation-only claim.
Recheck and decay
Firmware updates, app updates, and hub OS updates can silently break or fix pairing. A verification date is a claim about a specific date and version combination, not a permanent fact — that is the core difference from an undated forum thread. If the date on a fix or profile looks stale relative to your own firmware, treat it as a starting point to re-check, not a guarantee.