New
- New oscillation switch for heaters that support it, such as the H7130. These heaters have no fan entity, so there was previously no way to control oscillation from Home Assistant at all. A new switch, driven by the device's own oscillating state, is now added for any heater that advertises this capability. #265
Fixes
- H7130 heater's Auto Stop switch now targets the field the device actually responds to, and gets its own separate Thermostat switch. Auto Stop was wired to a toggle the H7130 never acts on; the real control lives inside the target-temperature setting as a separate field, and Auto Stop now writes that field directly. The thermostat toggle that had been conflated with it is now a separate, independently restored switch. Other heater models are unaffected. This hasn't been verified against real H7130 hardware — if you own one, please update and report back on #265 on whether Auto Stop and the new Thermostat switch now behave correctly.
- H7130 (and similar) heaters now correctly show as on in Home Assistant when a heat level or target temperature is set, and the target temperature no longer gets truncated. Setting a fan/heat level or a target temperature turned the heater on physically, but Home Assistant kept showing the power switch as off until it was toggled by hand; those writes now also set the power switch on. Separately, a Fahrenheit target such as 69.8°F was being truncated after Home Assistant's unit conversion and sent to the device as 20°C instead of 21°C; it's now rounded and clamped to the entity's limits. Fans and purifiers are unchanged. #265
- H7073 can now have its colour set from Home Assistant. Govee's Platform API only lists power, brightness and scenes for the H7073, so no colour picker was offered even though the device reports colour over AWS IoT. With account (AWS IoT) credentials connected, the integration now adds a colour control for this model and sends colour commands over AWS IoT, falling back to the regular REST API otherwise. This hasn't been verified on H7073 hardware — if you own one, please update and let us know on #240 whether colour control now works.
- H66A0 TV Backlight 3 Pro's DreamView switch now reflects what the device itself reports, instead of staying stuck on its last commanded value. Home Assistant kept showing DreamView as on across every poll once it had been switched on, so a sync started or stopped from the Govee app never showed up as a change in Home Assistant. The switch now reads the device's own mode report for the H66A0. #213 stays open for the separate question of DreamView control from Home Assistant itself, and further reports there are welcome.
- H5194 4-probe thermometer: probe 4 (and, to a lesser extent, probe 3) now updates promptly instead of lagging minutes behind probes 1-2. The integration was sending all 8 read packets for a sweep back-to-back, and the device dropped most of the later ones, so probe 4's temperature request was rarely answered. Reads are now paced one second apart, with the rarely-changing limit values read only every 6th sweep (an immediate read on arming still includes them). Diagnosed and verified by @bmcave, who tested the pacing fix directly on the hardware (#266).
- Setting a brightness together with a light effect no longer silently drops the brightness. Calling light.turn_on with both an effect and a brightness only applied the effect: the scene command returned right away, so the brightness was never sent and the light kept whatever brightness it already had. The requested brightness is now sent right after the effect command. Thanks @snoack for this fix (#268).
- Silent-MQTT-session detection now also works for sensors reached through a gateway, such as an H5310 behind an H5044. The detector added in v2026.10.1 only counted status queries sent directly to a device, so a gateway-routed sensor that's never queried that way directly could sit on a silently dead session indefinitely without ever being flagged. The check now also recognizes gateway readings that reach Govee's cloud but never arrive over the MQTT session as evidence of a silent session, and diagnostics and the resulting repair text now say plainly whether a device has its own AWS IoT topic or only shares a gateway's. #222