H5054 Water-Leak Detection via Account API (issue #62)
Standalone Govee H5054 water detectors now report leaks in Home Assistant.
Background
The H5054 is a 433 MHz RF-only sensor — its leak trip never reaches Govee's developer API or AWS IoT (supports_iot=false, no per-device MQTT topic). It reaches the Govee cloud only through your H5040 WiFi gateway, and the Govee app is notified from there. This release polls the same account/BFF endpoints the Govee app uses (the path homebridge-govee calls http).
What's new
- Water Leak moisture binary sensor per H5054, fed by the account API:
bff-app/v1/device/list→ online / gateway-online / battery / last-report timeleak/rest/device/v1/warnMessage→ unreadLeakageAlert→ wet
- Polls every 120 s;
warnMessageis only called when a detector freshly reports or is currently wet, keeping request volume low. - Skips the (useless) developer-API state poll for these devices so it can't overwrite the real state.
- Entity stays available even though H5054s report
online: falsebetween events (sleepy battery devices).
Requirements & limits
- Requires your H5040 WiFi gateway (the bridge that gets H5054 leaks to the cloud). Gateway-less setups need a local RTL_433/SDR path instead.
- Requires the integration's account login (email/password) — same login already used for real-time updates.
- The leak latches wet until you read the alert in the Govee app (the only clear-signal Govee exposes).
Internal
- Removed the speculative MQTT-flat-key parse (H5054 has no MQTT topic).
- Research:
docs/_research/2026-06-06_h5054-cloud-leak-path.md. Two validation passes (self + adversarial critic); 858 tests.