Lighting
Govee Cloud Integration
lasswellt/govee-homeassistant · vv2026.10.0
HACSCloud push
Govee Integration for Home Assistant - A HACS custom component for Govee lights and smart devices
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
fan | Fan | |
humidifier | Humidifier or dehumidifier | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
1 report below say how a device from this integration behaves in the Home app.
What people report
Govee devices run mostly through Govee cloud with optional LAN and Bluetooth paths; Bluetooth-only devices are unsupported. LAN-capable lights now work locally and a HomeKit fan preset bug was fixed.
- Works3
- Partly works2
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Govee H5192 probe thermometer | Works Cloud | Two-probe cooking thermometer supported via AWS IoT channelSaved copyAdd support for probe (cooking) thermometers, H5192 Closes #174. The H5192 is a two-probe cooking thermometer that reaches the cloud over the same AWS IoT channel as the rest of the account, but it behaves unlike anything else the integration talks to: it never volunteers a reading. It answers a read request and is otherwise silent. That single fact drives most of the design decisions below. Everything here was reverse-engineered from live captures of an H5192 running firmware 1.00.81 and cross-checked against what the Govee app displayed at the same moment. The register map is written up in … Excerpt saved from GitHub on 2026-10-23. | PR #185 · 2026-09 | |
| Govee H7106 fan | Works Cloud | Works in Home Fan adds to Home via HomeKit Bridge after duplicate preset fix | Duplicate Auto preset broke HomeKit add; fixed in 2026.6.21Saved copyHello! There appears to be an issue with Fans (I have two H7106 fans) having duplicate preset speeds/presets overall. It looks like there's two presets named "Auto", and preset speeds don't take effect when chosen. I had this cause an issue when trying to add the fan to Homekit. ## Version of the custom_component v2026.6.20 When adding to homekit via Homekit bridge, I get this error: ``` Failed to create a HomeKit accessory for fan.living_room_fan Failed to create a HomeKit accessory for fan.bedroom_fan Traceback (most recent call last): File … Excerpt saved from GitHub on 2026-10-23. | Issue #120 · 2026-06 |
| Govee LAN-capable lights | Works Local | LAN lights stay available during cloud outages after v2026.10.0Saved copy… 2026.8.3. These are the versions checked after the incident; I have not confirmed which integration version was installed during the outage. ## Configuration Govee LAN Control is enabled in the Govee app, and the integration's LAN transport diagnostic entities are enabled. Home Assistant and the lights remain on the local network when WAN access is lost. ## Describe the bug During an internet outage about a week ago, my LAN-enabled Govee lights became unavailable in Home Assistant, preventing normal control. They had worked normally before the outage. Source inspection and an automated … Excerpt saved from GitHub on 2026-10-23. | Issue #226 · 2026-10 | |
| Govee H1270 Ceiling Light Pro | Partly works Local | LAN writes work but status reads never answered; manual IP override addedSaved copyIssue #164 (H1270 Ceiling Light Pro): this device's LAN control listener accepts `turn`/`brightness`/`colorwc` writes as fire-and-forget but never answers a `devStatus` read, even from its own subnet, a genuine firmware silence, confirmed by testing from a host on the device's own VLAN. That's separate from why scan-based discovery also can't reach it: a scan reply is multicast, and multicast never crosses the VLAN boundary back to the listener regardless of firmware, a plain networking limitation, not a device quirk. Both break LAN control today, for different reasons: `correlate_scan` can … Excerpt saved from GitHub on 2026-10-23. | PR #165 · 2026-08 | |
| Govee Wi-Fi thermometers | Partly works Cloud | Readings refresh about every 10 minutes; Bluetooth sensors up to an hourSaved copyLimitations: Everything runs through Govee's cloud unless a device supports the LAN API or is within Bluetooth range; there is no fully local mode. The developer API allows 100 requests per minute and 10,000 per day per key. Every state poll costs one request per device, so large installs should raise the polling interval and let MQTT push carry the updates. Govee does not report the active scene, per-segment colors, or several appliance settings, so those entities keep the last value the integration sent (optimistic state) and restore it across restarts. Thermometer readings refresh on … Excerpt saved from the README on 2026-10-23. | README | |
| Govee Bluetooth-only devices | Won’t be supported Cloud | Use Home Assistant's built-in govee_ble integration insteadSaved copyLimitations: Everything runs through Govee's cloud unless a device supports the LAN API or is within Bluetooth range; there is no fully local mode. The developer API allows 100 requests per minute and 10,000 per day per key. Every state poll costs one request per device, so large installs should raise the polling interval and let MQTT push carry the updates. Govee does not report the active scene, per-segment colors, or several appliance settings, so those entities keep the last value the integration sent (optimistic state) and restore it across restarts. Thermometer readings refresh on … Excerpt saved from the README on 2026-10-23. | README |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud push
Goes through the maker’s cloud, which sends updates as they happen. Needs the internet and an account.
Found automatically over
- Bluetooth
Details
| Installs (analytics) | 11,458 (1.62%) |
|---|---|
| GitHub stars | 148 |
| Latest version | v2026.10.0 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @lasswellt |
| License | MIT |
Limitations from the README
- Everything runs through Govee's cloud unless a device supports the LAN API or is within Bluetooth range; there is no fully local mode.
- The developer API allows 100 requests per minute and 10,000 per day per key. Every state poll costs one request per device, so large installs should raise the polling interval and let MQTT push carry the updates.
- Govee does not report the active scene, per-segment colors, or several appliance settings, so those entities keep the last value the integration sent (optimistic state) and restore it across restarts.
- Thermometer readings refresh on Govee's schedule, typically every 10 minutes for Wi-Fi sensors and up to an hour for Bluetooth sensors behind a gateway; see Thermometers & sensors.
- Account login, real-time MQTT, LAN control, and Bluetooth passthrough use undocumented interfaces that can stop working when Govee changes them. The developer API path is the stable one.
- Bluetooth-only devices are not supported here; use Home Assistant's built-in goveeble` integration for those.
- One Govee account carries one real-time session: two Home Assistant installs signed in to the same account evict each other from AWS IoT in turn. Use separate accounts.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
