Govee
Govee RGBIC LED Strip Light H619A (5 m, protective coating)
- Wi-Fi
- Bluetooth
Verified September 2026
Half the price of a Hue strip and, crucially, the H619A supports Govee's LAN API, so Home Assistant's built-in 'Govee lights local' integration controls it with no cloud or key. Trade-off: on/off, brightness and colour only — RGBIC segment effects stay app-side (or use the community govee2mqtt add-on for more). Govee doesn't publish an LED count, lumen figure or cut-point spacing for the H619A, and there's no formal IP rating: "protective coating" means splash resistance on the LEDs, not a waterproof strip — the 24V control box and mains adapter are explicitly not waterproof. Best kept indoors: behind a TV, along skirting, under cabinets, not bathrooms or outdoor runs.
In Home Assistant
| Control | Type | What it does |
|---|---|---|
| Light | Light | Primary entity via govee_light_local. Controls on/off, brightness and a single flat colour for the entire 5m run — no per-segment addressing. |
| Segment light | Light (govee2mqtt only) | One entity per logical segment for independent colour. On the H619A, commands are frequently accepted but don't change the physical LEDs — an unresolved upstream bug, not a config error. |
| Scene | Select (govee2mqtt only) | Exposes Govee's built-in and DIY scenes as a selectable list, so pre-made RGBIC patterns can be triggered from HA rather than only from the Govee app. |
| Connected | Binary sensor (govee2mqtt only) | Online/offline status derived from the cloud connection; govee_light_local has no equivalent, so LAN-only setups can't tell a powered-off strip from a dropped Wi-Fi link. |
| LAN control | Config (device-side) | Must be enabled per-device in the Govee Home app before govee_light_local can discover the strip. |
The community govee2mqtt add-on's per-segment light entities are how you'd normally claw back RGBIC effects that govee_light_local can't touch — but on the H619A specifically it's a documented dead end: an open upstream issue shows segment commands logging as sent via Govee's cloud API with no actual change on the strip. Both integrations address the full 5m run as one device/entity regardless of any physical extension, since control is by device ID rather than LED position, so there's no software distinction between a stock 5m strip and an extended one. Net effect: for this strip, govee2mqtt is worth adding for DIY scenes and device-online sensors, but budget for segment control specifically to be unreliable rather than a guaranteed upgrade path over govee_light_local's whole-strip colour.
Specs
- model
- H619A
- length
- 5 m (16.4 ft)
- waterproof
- No official IP rating published; adapter and control box are explicitly not waterproof — 'protective coating' on the LEDs is splash resistance only, not a submersion/outdoor rating
- scene modes
- 64+ preset scenes plus music sync via Govee Home app
- connectivity
- Wi-Fi + Bluetooth
- power source
- 24V mains adapter (UK plug) via control box