v2026.8.2

A regression fix for v2026.8.1, plus some housekeeping. Update if you have standalone Govee water detectors (H5054).

Fixed

Battery entity missing on standalone water detectors (#145) — a regression introduced in v2026.8.1.

That release stopped hub-attached leak sensors getting two competing battery entities, but it identified them by SKU: anything carrying a leak-sensor SKU was assumed to take its battery from the hub path instead. That holds for an H5058 behind an H5043. It does not hold for a standalone H5054, which the hub never reports, and which gets its battery from the water-detector poll — through the very entity the SKU check was removing. Those detectors lost their battery entity entirely.

The exclusion now keys off whether the device is actually in the hub-discovered leak list, which is the only case where two entities would collide. Hub-reported sensors keep getting exactly one battery entity; standalone detectors keep their own. Both cases are covered by tests now.

Thanks to @Danimal4326 for spotting it within the hour.

Housekeeping

• Removed two config options that nothing read. enable_segments and segment_mode were written into new entries and then ignored — segment behaviour has been driven by the per-device mode you pick in the options flow for some time. Existing entries keep the two now-inert keys; nothing reads them, and dropping them isn't worth a migration.
• The default segment mode now has a single definition rather than being hardcoded in three separate fall-back paths.
• Corrected the services module docstring, which advertised a "send raw commands" service that has never existed. The integration provides govee.refresh_scenes and govee.set_segment_color.

Documentation

The README has been audited against the code rather than patched release by release. Several claims had drifted — LAN control was documented as carrying colour before it did, the leak-sensor and thermometer model lists were incomplete, account login was undersold, and segment mode read as a global setting when it is chosen per device. It also now documents command routing, the per-device diagnostic entities, and troubleshooting steps for the failure modes that actually generate issues here.