Three fixes for sensors that silently stopped reporting, a new segment mode, and a README that finally credits where this project came from.
Expired account sign-ins no longer fail silently
If your battery levels or gateway-bridged sensor readings stopped at some point and never came back, this is probably why — and it is worth updating even if you never filed an issue about it.
The account token obtained at setup was cached and reused indefinitely. Nothing refreshed it, and the refresh_token we stored was never used anywhere. When it eventually expired, Govee began answering every account-API call with an error envelope returned as HTTP 200, which the integration read as "this account has no devices" — silently. MQTT stayed connected the whole time, because it authenticates with long-lived certificates rather than that token, so the integration reported itself perfectly healthy while battery levels and gateway-bridged readings quietly stopped.
Now: in-body errors are detected rather than read as an empty device list; an expired token triggers a re-login and a retry, throttled to once per 15 minutes; and when re-login can't succeed on its own — 2FA required, or a changed password — you get a repair notification naming exactly what stopped working instead of nothing at all.
Found from diagnostics downloads by @matteotomasoni and @thrstnbecker (#132), whose two accounts showed the same signature and made it possible to distinguish a real bug from a Govee-side change. @matteotomasoni reasonably concluded Govee had withdrawn the data; the evidence they attached is what showed otherwise.
Dual-probe thermometers now report both probes
The H5112 fridge/freezer thermometer carries two independent probes and reports them separately. Only the first was ever read.
@mikejhendricks' diagnostics (#150) showed three units behind one gateway where two had nothing connected to probe 1 — correctly decoded as "no reading" — while probe 2 read normally the whole time. Those two devices showed no temperature at all, despite carrying a perfectly good one we never looked at. The third unit had both probes reporting, so this was a second reading being discarded on every device, not merely a fallback for a missing first.
Each probe now gets its own entity, created only where a reading actually exists, so single-probe owners don't gain a sensor that can only read unknown. A probe plugged in later triggers a one-time reload so its entity appears.
New "both" segment mode for RGBIC devices
Segment mode was previously exclusive: a device got either the grouped "all segments" light or the individual per-segment lights. both runs them together — the group for "set the whole strip", the individual entities for picking out particular segments.
The part that isn't obvious: Govee never reports real per-segment state, so both entity types are purely optimistic and nothing reconciles them. Without extra wiring, a light.turn_off on the group would leave every individual entity still showing "on". @chrisns spotted that and built the sync, deliberately one-way with the reasoning written down (#167).
Also in this release
- Fixed: a data-only config-entry write (such as storing a refreshed token) triggered a full integration reload — tearing down every entity, dropping the MQTT connection and re-fetching scenes. The update listener now reloads only when options actually change.
- README: now credits LaggAt/hacs-govee, the project this began as in August 2020 and whose author remains the copyright holder. It had no attribution at all, which was the single most significant omission in the documentation. Also adds contributors, the reverse-engineering projects this depends on, and a section recording what specific reporters established — because several root causes here were found in diagnostics attachments rather than in the code.
Upgrading
No action needed. If you were affected by the expired sign-in, updating restores readings automatically unless your account needs 2FA or your password changed — in which case you'll now get a repair notification telling you so.
Full Changelog: v2026.8.3...v2026.8.4