Tapo leak sensor works in vendor app but not Matter: check the documented prerequisites in order, then retry only the affected path.
Start with these checks
A sensor connected to its vendor hub has only passed the first hop. Read the hub’s current Matter export list for that specific sensor, including which hub generation is required. A leak event in the vendor app does not prove an external platform exposes the same event.
- Check H100 versus H110.
- Check current hub firmware and supported child types.
Stop when you find the first unmet requirement. Fix it and try pairing again before changing the next variable.
How to interpret the outcome
H100 negative is for current Matter exposure only.
A failed path does not prove every alternative path is unsupported. For example, a missing direct radio may still leave a separately documented bridge or cloud route.
Avoid these risky shortcuts
- Reset a working vendor sensor to fix a missing bridge feature
Relevant model records
Official references
- TP-Link — Tapo hub Matter bridging limits Reviewed 2026-10-30
These are evidence-based editorial checks, not a diagnosis of your individual home network.