How to Connect Govee Devices to Home Assistant

Integration Options Compared

• Official Govee integration: Built into HA, easy setup, uses cloud API. Works with Wi-Fi Govee devices. ~1–3 second latency for commands.
• HACS Govee LAN: Uses Govee's local LAN API (available on some devices). Fast local control, no cloud for commands. Requires enabling LAN mode in the Govee app.
• Bluetooth local: HA's Bluetooth integration can control some Govee devices directly over BLE. No Govee app or account required. Limited to devices within Bluetooth range (~10m).

Official Govee Integration Setup

1. Get your Govee API key: open the Govee app → tap your avatar → About Us → Apply for API Key. Key arrives via email within minutes.
2. In HA: Settings → Integrations → Add Integration → Govee Lights
3. Enter your API key
4. All compatible Govee devices on your account appear automatically

HACS Govee LAN Integration

The Govee LAN integration (by LaggAt on GitHub, installable via HACS) uses Govee's official LAN control protocol, available on select devices since Govee added it in late 2022.

1. In the Govee app: tap the device → gear icon → LAN Control → enable it
2. Install HACS in HA if you haven't already
3. In HACS → Integrations → search "Govee LAN" → install
4. Restart HA
5. Settings → Integrations → Add → Govee LAN
6. The integration auto-discovers Govee devices on your network

With LAN control, commands respond in <100ms and work even when Govee's cloud is down.

Bluetooth Local Control

Some older Govee devices (especially bulbs and strips) communicate over BLE. HA's Bluetooth integration can discover and control these devices if your HA host has a Bluetooth adapter (Raspberry Pi has built-in BLE).

1. Ensure HA's Bluetooth integration is set up (auto-discovered on Pi)
2. Put the Govee device in pairing mode
3. HA should discover it under Settings → Integrations → Bluetooth

Bluetooth range is limited to ~10 meters. Not all Govee devices support this — check the HA Govee Bluetooth integration supported device list.

Entity Examples

After adding Govee H6199 light strip via official integration:

• light.living_room_strip — on/off, brightness, color (RGB)
• Color mode, color temperature (on supported devices)

Govee strips support scenes (preset effect modes like "Rainbow", "Sunrise") via the effect attribute in the light entity.

Lighting Scene Automation (YAML)

automation:
  - alias: "Movie mode at sunset"
    description: "Dim and color-shift Govee lights when TV turns on after sunset"
    trigger:
      - platform: state
        entity_id: media_player.living_room_tv
        to: "playing"
    condition:
      - condition: sun
        after: sunset
    action:
      - service: light.turn_on
        target:
          entity_id: light.living_room_strip
        data:
          brightness_pct: 20
          rgb_color: [255, 50, 0]
          transition: 3

  - alias: "Restore lights when TV off"
    trigger:
      - platform: state
        entity_id: media_player.living_room_tv
        to: "off"
    action:
      - service: light.turn_on
        target:
          entity_id: light.living_room_strip
        data:
          brightness_pct: 80
          color_temp: 4000
          transition: 2

Known Limitations

• Official API is cloud-dependent and rate-limited — not suitable for rapid automations
• LAN control is only available on newer Govee devices (H6199, H615x, H617x, and many 2022+ models)
• Govee scenes/effects can't always be read back — you can set an effect but may not see the current effect name in HA
• Bluetooth devices must stay within range of the HA host's Bluetooth adapter

Troubleshooting

• Entities don’t appear in Home Assistant: Confirm the integration is loaded correctly and double-check that the device is supported by the platform you chose.
• Commands feel delayed: This is usually caused by cloud polling, weak Wi-Fi, or a slow Zigbee mesh rather than Home Assistant itself.
• Things work in the vendor app but not in HA: Re-check credentials, local API permissions, and whether the device is using the correct network path.
• Automations misfire: Open the automation trace in Home Assistant and verify the exact entity IDs and state changes being used.

FAQ

SmartWired uses affiliate links. If you buy through our links, we may earn a commission at no extra cost to you. See our Affiliate Disclosure.