github lasswellt/govee-homeassistant v2026.4.2

latest releases: v2026.5.9, v2026.5.8, v2026.5.7...
one month ago

What's new

Direct BLE support (testing) 🔬

This release adds transparent Bluetooth Low Energy (BLE) control for Govee lights that are within Bluetooth range of your Home Assistant host. When a nearby Govee BLE device is detected, commands are routed through BLE first (~50ms local latency) before falling back to the cloud REST API (~500ms). MQTT continues delivering real-time state updates as before.

⚠️ This is a testing release for BLE support. The BLE transport is new and has not been tested against real hardware yet. If you have Govee BLE lights (devices advertising as Govee_*, ihoment_*, or GBK_*) and want to help test, please install this release and report any issues. Cloud-only users are unaffected — BLE code paths are completely skipped when Bluetooth hardware is not present.

How it works — no configuration needed:

  • The integration automatically listens for Govee BLE advertisements
  • When a nearby device matches a cloud-discovered device (by SKU from the advertising name), a local BLE transport is activated
  • Power, brightness, and RGB color commands go through BLE; scenes, color_temp, and work modes use the cloud API
  • If BLE fails for any reason, the command transparently falls back to the cloud REST API

BLE-capable commands: power on/off, brightness, RGB color
Cloud-only commands: scenes, color temperature, work modes, DIY scenes, music mode, DreamView

Supported BLE devices: Any Govee light that advertises via Bluetooth with a Govee_*, ihoment_*, or GBK_* name prefix. Segmented RGBIC devices (H6053, H6072, H6102, H6199) use the segmented color encoding automatically.

Requirements: Home Assistant with Bluetooth support (built-in adapter or ESPHome Bluetooth proxy). No additional setup steps.

Bug fix: Air purifier device type (#37)

Fixed DEVICE_TYPE_PURIFIER — the constant held the wrong string (devices.types.purifier) which never matched any real Govee device. Replaced with the canonical devices.types.air_purifier confirmed by four independent sources. Air purifiers like the H7126 now correctly produce fan + purifier-mode-select entities. Credit: @kami587 for the diagnosis.

Full changelog

  • fix: Recognize devices.types.air_purifier as fan+purifier (H7126) — closes #37
  • feat: Add api/ble.py — Govee BLE wire protocol + device library
  • feat: Add multi-transport BLE dispatch to coordinator
  • chore: Bump version to 2026.4.2

Testing BLE — how to help

If you'd like to test BLE support:

  1. Install this release via HACS
  2. Ensure your HA host has Bluetooth (built-in adapter or ESPHome proxy)
  3. Check your logs for BLE transport available for <device> (SKU=<sku>, BLE=<address>) — this confirms a device was matched
  4. Try controlling the matched device (power, color, brightness) and note latency vs cloud
  5. Report issues at https://github.com/lasswellt/govee-homeassistant/issues with:
    • Your device SKU and advertising name
    • Whether BLE commands worked
    • Any errors from custom_components.govee.coordinator or custom_components.govee.api.ble in the logs

Don't miss a new govee-homeassistant release

NewReleases is sending notifications on new releases.