--- title: "Govee Cloud Integration" description: "Govee Cloud Integration is a Marketplace integration for Home Assistant. Its installs are not shown, because another integration uses the same domain, govee. It needs the vendor's cloud and was last updated October 27, 2026." canonical: "https://vulpo.app/integrations/marketplace/lasswellt-govee-homeassistant" url: "https://vulpo.app/integrations/marketplace/lasswellt-govee-homeassistant.md" last-updated: "2026-10-27" version: "1.4" --- # Govee Cloud Integration > Govee Cloud Integration is a Marketplace integration for Home Assistant. Its installs are not shown, because another integration uses the same domain, govee. It needs the vendor's cloud and was last updated October 27, 2026. Govee Cloud Integration is a custom component that controls Govee lights and other smart devices through Govee's cloud. It covers lights, plugs, fans, humidifiers, heaters, thermometers, air quality monitors, and presence and leak sensors, with entities created from the capabilities Govee reports for each device. Adding the Govee account email and password alongside the API key enables real-time updates over MQTT and support for hub-based leak sensors. Devices with Govee's LAN API enabled are found automatically and controlled locally, with the cloud as fallback. Options include the polling interval, a daily cloud request budget, scene and DIY scene selectors, group devices, and segment modes for RGBIC lights. Setup is done in the UI with a Govee developer API key. Automatic summary of the README and code of lasswellt/govee-homeassistant. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=lasswellt&repository=govee-homeassistant&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=lasswellt&repository=govee-homeassistant&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **Found by itself**: Home Assistant spots it on the network and offers to add it. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Govee API key - **API key**: The API key from your Govee Developer account (a long string of letters and numbers). ### Govee account (optional) - **Govee app email**: The email address you use to sign in to the Govee mobile app. - **Govee app password**: The password you use to sign in to the Govee mobile app (not the website). ### Govee verification code - **Verification code**: Check your email for a code from Govee. ### Re-authenticate Govee - **API key**: A current API key from the Govee Developer account this integration was set up with. ### Reconfigure Govee - **API key**: Your Govee Developer API key from developer.govee.com. - **Govee app email (optional)**: Email for the Govee mobile app. Leave empty to remove real-time updates. - **Govee app password (optional)**: Password for the Govee mobile app. Leave empty to keep the existing password. ### After setup - **Polling interval (seconds)**: How often every device is polled over the Govee cloud API for its state. Real-time updates over MQTT and LAN arrive between polls. Range 30 to 300 seconds, default 60. Each poll spends one request per device against Govee's limit of 100 per minute and 10,000 per day. - **Daily cloud request budget**: How many Govee cloud requests per day this integration aims to spend on polling. The polling interval is stretched automatically so the day's spend lands on this figure. Govee's own cap is 10,000 per day; the default of 9,000 leaves headroom for commands, scene lookups and device rediscovery. - **Leak sensor polling interval (seconds)**: How often standalone Govee water and leak detectors (for example H5054) are checked for a leak. These RF-only sensors have no push channel, so a leak surfaces with up to this much delay. Lower reacts faster but makes more account API calls; raise it if you have many detectors. Range 60 to 3600 seconds, default 120. Requires email and password login; ignored if you have no such detectors. - **Probe thermometer polling interval (seconds)**: How often an armed probe (cooking) thermometer such as the H5192 is read over AWS IoT while its Live polling switch is on. These devices never volunteer a reading, so this interval is the update rate. Costs battery rather than API quota. Range 10 to 600 seconds, default 30. Requires email and password login. - **MQTT status re-query interval (seconds)**: How often every MQTT-connected device is asked for its current status over AWS IoT. Devices are largely poll-triggered responders, not autonomous pushers; this mirrors what the Govee app itself does while its device list is on screen, so state keeps updating without the app open. Lower reacts faster but publishes more per device; raise it if you have many devices. Range 60 to 3600 seconds, default 300. Set 0 to turn the re-query off and rely on what devices push on their own. Queries go out one device per second; a device whose query makes AWS IoT close the session twice is left out until the next reload (a warning names it). If the session closes right after queries to three different models in a row with none answered, AWS IoT is refusing status queries for the whole account, and the re-query stops until the next reload (a warning says so). Requires email and password login (MQTT credentials); ignored when MQTT is unavailable. - **Temperature unit from Govee API (thermometers)**: Auto (default) first uses the temperature unit your Govee account reports for the device, then falls back to converting the thermometers known to report Fahrenheit (for example H5179, H5109, H5110, H5111, H5053, H5075, H5100), and trusts the rest. Choose Fahrenheit if a reading still looks about 1.8 times too high (for example 74 instead of 23), or Celsius to force no conversion. Govee's API omits unit metadata, so the value cannot always be auto-detected. - **Enable group devices**: Surfaces the device groups you created in the Govee app as single light entities. A command to a group is sent once and synced to all members by Govee's cloud, so it syncs better than grouping the lights with Home Assistant helpers. State is best-effort (groups cannot be polled), and group lights only support power, brightness, and color. - **Enable scene selector**: Creates a scene dropdown per device that has scenes, and exposes the scenes as light effects. Turn off to save one API request per device at startup. - **Enable DIY scene selector**: Creates a DIY scene dropdown per device that has DIY scenes created in the Govee app. - **Expose per-device transport connectivity sensors**: Adds one connectivity binary sensor per transport (cloud API, MQTT, Bluetooth, LAN) for every device. Off by default because it creates four extra diagnostic entities per device. - **Send power, brightness, and color over MQTT (faster, experimental)**: Routes power, brightness, and color commands through Govee's MQTT channel instead of the REST cloud API, reducing latency and bypassing REST rate limits. Requires email and password login (MQTT credentials). Falls back to REST automatically when MQTT is unavailable, and for any device that has not yet answered over MQTT (it answers the periodic status query, so keep that on). Experimental: it uses an undocumented channel, so leave it off if commands behave unexpectedly. - **Confirm light commands and resend dropped ones**: After a power-off, brightness, colour or colour-temperature command to a light, waits a few seconds for the light's own real-time (AWS IoT) report and asks for one status if none comes. If the light still shows the old value, the command is sent once more over the cloud API. Lights only: appliances such as kettles, heaters and fans are never resent, and a power-on is never resent. A resend uses one cloud request, only when the daily budget and rate limit allow it. Requires email and password login; lights that have not reported over AWS IoT are left as they are. Off by default. - **LAN device addresses and subnets (advanced)**: Only needed when LAN-enabled Govee devices are on a different subnet or VLAN than Home Assistant, so the local discovery scan cannot reach them. Enter a comma-separated list of device IPs (10.20.0.51), broadcast addresses (10.20.0.255), and subnets in CIDR notation (10.20.0.0/24, /24 or smaller). Subnets are scanned device by device, since most routers drop cross-VLAN broadcasts. Leave blank if all devices share Home Assistant's network. Advanced: if a device still is not found because its scan reply cannot cross the VLAN, pin it with device\_id=ip (AA:BB:CC:DD:EE:FF:00:11=10.20.0.51) to skip discovery for that device. Add a trailing ! (=10.20.0.51!) only for firmware that accepts LAN commands but never answers a status read. That turns off every LAN health check for the device, so a wrong IP will look like it is working while the device never responds. Enter off to turn LAN discovery and local control off entirely. - **Custom 1** - **Custom 2** - **Custom 3** - **Custom 4** - **Devices to configure**: Devices to set a segment mode for. Devices you leave out keep their current mode. - **Segment mode**: Disabled creates no segment entities, grouped creates one entity for all segments, individual creates one entity per segment, and both creates the grouped entity alongside the individual ones. Texts from the code of [lasswellt/govee-homeassistant](https://github.com/lasswellt/govee-homeassistant). ## Entities - **Binary sensors**: Connectivity, Reported online, Cloud API, MQTT, Bluetooth, LAN, Water tank full, Pump state, Water leak, Occupancy, LoRa, Internet, and 4 more - **Buttons**: Refresh scenes, Clear water alert, Clear leak alert - **Events**: Button - **Fans**: Fan - **Humidifiers**: Humidifier - **Lights**: Night light, Segments, Main light, Ring light - **Numbers**: Music sensitivity, Target temperature - **Selects**: Scene, Snapshot, DIY scene, HDMI source, Music mode, Fan speed, Mode, Night light scene, Brew mode - **Sensors**: API rate limit remaining, MQTT status, Last MQTT received, Temperature, Mode, Voltage, Current, Power, Energy, Power factor, Probe 2 temperature, Humidity, and 17 more - **Switches**: Live polling, Plug, Night light, Music mode, DreamView, Auto stop, Thermostat, Oscillation, Power, Main light, Background light, Nebula light, and 3 more ## Actions - **Refresh scenes**: Refreshes the available scenes from the Govee API. Fields: Device - **Set segment color**: Sets the color of specific segments on an RGBIC light. Fields: Device, Segments, RGB color - **Send raw ptReal frame**: Developer/debug tool that sends a raw Govee BLE command frame to the device over AWS IoT (a checksum is added automatically when 19 bytes or fewer are given). A wrong frame can leave the light in an unexpected mode. Fields: Device, Frame - **Request status**: Asks a device to report its status over AWS IoT (the real-time connection), once or repeatedly for a while. Needs the account login. Spends no cloud API requests. Fields: Device, Duration, Interval ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. - **Repair notices**: Notices it can show in Settings, Repairs: Govee account requires verification, Govee account sign-in expired ## From the README > Control Govee lights, plugs, fans, humidifiers, heaters, thermometers, air‑quality & CO₂ monitors, presence & leak sensors — with optional real‑time push over Govee's AWS IoT MQTT and automatic local LAN control for devices that support it. > > Hub (cloud) · IoT class cloud\_push (MQTT + polling) · UI‑only config, no YAML From the README of [lasswellt/govee-homeassistant](https://github.com/lasswellt/govee-homeassistant#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Lighting](https://vulpo.app/integrations/category/lighting.md), LED strips and controllers - Brand: [Govee](https://vulpo.app/integrations/govee.md) - Number: Installs not shown: shared domain govee; 149 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v2026.10.2, last updated October 27, 2026 - Domain: `govee` - Source: - Issues: In Vulpo: Light card, Quick Toggle card, Fan card, Button card, Apple Watch, Control Center ## Other ways in for Govee | Name | Kind | Installs or stars | Connection | Upkeep | | --- | --- | --- | --- | --- | | [Govee lights local](https://vulpo.app/integrations/core/govee-light-local.md) | Built-in integration | 15.3k installs sharing analytics | Works locally | Part of Home Assistant | | [Govee Bluetooth](https://vulpo.app/integrations/core/govee-ble.md) | Built-in integration | 14.2k installs sharing analytics | Works locally | Part of Home Assistant | | [Govee](https://vulpo.app/integrations/marketplace/laggat-hacs-govee.md) | Marketplace integration | Installs not shown: shared domain govee | Needs the vendor's cloud | Updated in the last 6 months | | [Govee Life](https://vulpo.app/integrations/marketplace/disforw-goveelife.md) | Marketplace integration | 1.1k installs sharing analytics | Needs the vendor's cloud | Updated in the last 6 months | | [Govee LED BLE](https://vulpo.app/integrations/marketplace/teh-hippo-ha-govee-led-ble.md) | Marketplace integration | 235 installs sharing analytics | Works locally | Updated in the last 6 months | Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-27. Source: https://vulpo.app/integrations/marketplace/lasswellt-govee-homeassistant --- - HTML version of this page: https://vulpo.app/integrations/marketplace/lasswellt-govee-homeassistant - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml