TLDR

  • Check the model number first: Govee support is device-by-device, not brand-wide. A name such as “smart bulb” is not specific enough.
  • For supported lights, try LAN control over your home network: use it when the Govee app shows LAN Control. Use Matter—the cross-brand smart-home standard—only when that exact unit has a Matter setup code. Both can keep basic controls local, but Matter may omit Govee effects.
  • Use the separate Bluetooth path for listed sensors: an H5075 temperature and humidity sensor can report locally; this integration is not a way to control Govee lights.
  • Avoid calling every community setup local: govee2mqtt uses the home network where possible, but some extra features still need a Govee login or internet connection.
  • Main caveat: a model on a support list can still vary by device software, region, or hardware version. Keep the receipt and test the exact functions you need.

The short answer: Govee works, but not as one integration

Yes, many Govee lights and sensors work with Home Assistant, and several routes keep everyday control inside the home. The right route depends on the model and the features you care about. A compatible light may offer Govee's official local network (LAN) control, Matter—the cross-brand smart-home standard—over Wi-Fi, or both. A temperature sensor may use Bluetooth. Other products may offer only a cloud or community-supported route.

Start with the model code printed on the device, label, box, or Govee app: H607C, H6006, H6008, and H5075 are examples. Do not buy from a listing that gives only a family name. Govee sometimes sells several generations under similar product wording, and one generation's instructions may not apply to another.

Simple rule: choose one primary control route for each device. Keeping the Govee app for device updates and special effects is fine, but adding the same light through LAN, Matter, and a community bridge can create duplicate controls and confusing automations.

Five Govee paths, clearly separated

Path Official support Local control Cloud dependency Main tradeoff
Govee lights local Built into Home Assistant for listed light models Yes, through Govee's local network interface (LAN API) Normal Home Assistant control is local; the Govee app may still be useful for setup, firmware, and effects Requires an eligible model, the LAN Control setting, and working local discovery; scene support varies
Matter Official standard supported by Home Assistant and Matter-labeled Govee models Yes, normal Matter commands stay on the home network Routine control is local; initial enablement, firmware, vendor extras, or remote app use may still need the internet Usually exposes basic light controls, not every Govee scene, segment, DreamView, or music effect
Govee Bluetooth Built into Home Assistant for listed sensors, buttons, and presence devices Yes, Home Assistant receives nearby Bluetooth broadcasts No cloud is required for supported sensor readings This is a sensor path, not a general Bluetooth-light controller; range may require a Bluetooth proxy
Govee developer API Official Govee web API, but not an official Home Assistant Core integration No Yes; commands go to Govee's hosted API with an API key Internet, account, rate limits, and service availability become part of the automation
govee2mqtt Community project, not Home Assistant or Govee support Mixed: it uses LAN first where a device allows it Some scenes, segments, live state, and other functions can require an API key, Govee account, or cloud messaging Often broader and richer, but installation, updates, credentials, and failure modes belong to you

What current model examples actually show

As of August 1, 2026, official Home Assistant and Govee pages show the following examples. They are not a promise that every product with a similar retail name behaves the same way.

Govee Floor Lamp 2 H607C

Home Assistant lists H607C for the official Govee lights local integration. Govee's current US Floor Lamp 2 page also describes H607C as Matter compatible. That gives this model two documented potential local routes: Matter, plus LAN when the Govee app exposes LAN Control.

For basic on/off, brightness, color temperature, and color, start with one route and compare the controls it exposes in Home Assistant. Keep the Govee app if you want device updates or brand-specific effects. Do not assume Home Assistant will reproduce every app animation, segmented color pattern, or music mode through either route.

Govee A19 bulbs H6006 and H6008

Home Assistant's current LAN support list includes H6006 and H6008, and Govee's current US product pages describe these A19 lines as Matter compatible. Treat both as trial-only choices. An open H6008 report describes failed LAN support, while an H6006 report closed as not planned describes power-only control despite the list entry.

Those reports do not mean every H6006 or H6008 fails. They do mean a model code is the start of verification, not the finish. Buy one returnable bulb, confirm the device software, check whether the app shows LAN Control, and verify brightness, color, and state updates before expanding to a room. Use Matter only if the actual bulb supplies its own Matter setup code.

Govee H5075 temperature and humidity sensor

The H5075 is listed under Home Assistant's official Govee Bluetooth integration. Home Assistant can receive its local temperature, humidity, and battery broadcasts when Bluetooth coverage is adequate. If the sensor is far from the Home Assistant computer, use a compatible nearby Bluetooth proxy rather than assuming you need Govee's cloud.

This distinction matters: seeing “Govee Bluetooth” in Home Assistant does not mean a Wi-Fi-and-Bluetooth Govee bulb can be controlled through that integration. The official Bluetooth page lists the device types it understands.

Choose the path in this order

  1. Write down the exact model and hardware generation. Use the label or Govee app, not the marketplace title.
  2. Check the two official Home Assistant lists. Look separately at Govee lights local and Govee Bluetooth. A device appearing on neither list is not automatically supported by those integrations.
  3. Look for a real Matter code. Matter branding on a newer listing does not upgrade an older unit already in the drawer. The actual device or its app must provide a pairing or sharing code.
  4. Pick the least dependent route that exposes the controls you need. For a listed light, try official LAN control. For a Matter model, Matter is a good local fallback or primary path. For a listed sensor, use Bluetooth.
  5. Use community software only for a feature worth maintaining. Read govee2mqtt's feature matrix before assuming a desired scene or segment stays local.
  6. Test with the internet disconnected. Keep Wi-Fi and Home Assistant running, block or unplug the internet briefly, and try on/off plus the automations that matter. Restore internet before firmware or app work.

Set up the official LAN integration

  1. Update the light in the Govee app and confirm ordinary control works.
  2. Open that device's settings in the Govee app and enable LAN Control if the option is present. If it is absent, do not assume another model's screenshot applies to yours.
  3. Put Home Assistant and the light on a local network that allows device discovery and direct traffic between them.
  4. In Home Assistant, go to Settings > Devices & services, choose Add Integration, and select Govee lights local.
  5. Rename the device and test on/off, brightness, color temperature, color, scenes, and state updates individually.

Home Assistant classifies this integration as Local Push: the light communicates changes on the local network rather than Home Assistant polling a remote service. Home Assistant also warns that not every listed device supports every scene. Basic control can be solid while a particular effect is absent.

If the device lives on a separate IoT network, local discovery packets may not cross the boundary. Keep the first test simple by placing Home Assistant and the light on the same normal LAN, then use Tara's guide to choosing a main LAN or IoT VLAN before adding firewall rules.

Use Matter when the exact Govee device supports it

A Matter-enabled Govee light can be added in the Home Assistant Companion app with its Matter code. If it is already paired to another Matter home app, use that app's sharing flow to create a new code for Home Assistant instead of factory-resetting it. Govee's Matter FAQ says the Govee app can coexist with Matter control.

Pair with Matter before adding the device to the Govee app. Govee says to connect the device to Matter first, then leave its Wi-Fi network alone. Changing the device's network later through the Govee app disables Matter; restoring Matter requires a device reset and a fresh setup.

Current Govee examples such as H607C, H6006, and H6008 use Wi-Fi, so they do not need a Thread border router. Home Assistant still controls normal Matter functions locally. Tara's Matter-without-internet guide explains which setup and vendor tasks can remain online even when everyday control is local.

Matter is a common control language, not a promise of every vendor feature. A light may expose on/off, dimming, color temperature, or color while leaving Govee's named scenes, music response, DreamView, and per-segment effects in the Govee app. Home Assistant's own Matter documentation notes that a native integration can expose more than the matching Matter device type.

Matter and HomeKit are different Apple paths

A Matter-enabled Govee device can be added to Apple Home or shared between Apple Home and Home Assistant with Matter multi-admin, the feature that lets one device belong to more than one home app. That is a Matter relationship; it is not the older HomeKit accessory protocol.

For a non-Matter Govee device already working in Home Assistant through LAN or another path, Home Assistant's HomeKit Bridge can present selected Home Assistant entities to Apple Home. Home Assistant must remain available because it is the bridge. Do not confuse that with HomeKit Device, the integration used when Home Assistant pairs directly to a native HomeKit accessory.

If Apple Home is part of the household, decide where automations live. Sharing a light for Siri and family controls is useful; creating one motion routine in Govee, another in Apple Home, and a third in Home Assistant is a reliable way to produce conflicting commands.

Understand the govee2mqtt caveat before installing it

govee2mqtt is a capable community bridge that sends Govee controls through MQTT, a message service often used with Home Assistant. Its own documentation is unusually clear about the boundary: it prefers the local network when the device supports it, but the feature table shows that some DIY scenes, music modes, segmented color controls, tap-to-run commands, and live updates require a Govee API key, account access, or undocumented cloud messaging.

Use it when the extra device coverage or effects justify the maintenance. Treat it like community software: read release notes, protect credentials, keep backups, and test updates. For a hallway light that only needs dependable on/off and dimming, an official LAN or Matter path is easier to hand to another homeowner.

If a listed Govee light does not appear

  1. Confirm the full model code. Similar retail names can hide different generations.
  2. Update firmware and power-cycle once. Then reopen the app and check whether LAN Control exists and remains enabled.
  3. Test on one normal home network. Guest Wi-Fi and router settings that stop devices from seeing one another can block discovery even while the app still works through the internet.
  4. Remove duplicate paths temporarily. Disable the extra Matter or community control so you know which integration is responding.
  5. Try a direct command and watch state. A command that works while state never updates is a different problem from a device that is never discovered.
  6. Check current issues for the exact model. Include model, firmware, Home Assistant version, network layout, and diagnostics when reporting a reproducible problem; remove private keys and addresses first.

For Bluetooth sensors, first confirm Home Assistant's Bluetooth integration is working and that the device is close enough. The Bluetooth proxy guide shows how to extend local reception without placing the main Home Assistant computer beside every sensor.

What to buy—and what to avoid

  • For a current floor lamp: H607C is a useful example because current official pages document both a Home Assistant LAN path and Matter. Buy only after confirming the exact model on the listing and return policy.
  • For ordinary A19 bulbs: treat H6006 and H6008 as trial-only. Current official pages list them, but an open H6008 report describes failed LAN support and an H6006 report closed as not planned describes power-only control. Test one returnable bulb before a larger purchase.
  • For local temperature and humidity: H5075 is on the official Bluetooth list. Plan Bluetooth coverage, not a cloud subscription, around it.
  • For advanced animated effects: expect to keep the Govee app or accept a community/cloud dependency. Do not buy on the assumption that Matter will reproduce the entire effects library.
  • Avoid vague or old stock: a product title that omits the model, a seller mixing generations, or an unverified claim that “all Govee works locally” is not enough for a dependable system.

Keep a simple manual fallback for important rooms, such as an ordinary wall switch that household members understand or a separate conventional lamp. Cutting power makes any smart bulb unreachable, so a wall switch feeding smart bulbs normally has to stay on for automations to work. Govee's current H6008 page specifically says not to use that bulb with a smart switch. Essential pathways should not depend on a community bridge or internet service.

Tara's practical approach

A reliable setup begins with the exact device and the smallest dependable path. Use official LAN or Matter for ordinary local light control, Bluetooth for listed sensors, and the Govee app only where device updates or special effects genuinely add value. Name or disable duplicate controls so every automation has one obvious target.

A configured local home-automation system should document the model, integration, cloud boundary, physical fallback, and what happens during an internet outage. Test one Govee device before repeating it across a room, and save the working setup alongside the rest of the household handoff.

Frequently asked questions

Does Govee work with Home Assistant?

Yes, but support is model-specific. Compatible lights can use Home Assistant's official Govee lights local integration or Matter. Listed Govee sensors can use the separate Bluetooth integration. Other devices may need a cloud or community path.

Can Govee work locally without the internet?

Yes for supported paths. The official LAN light integration, supported Bluetooth sensors, and normal Matter control are local. Govee's developer API is cloud-based, and some govee2mqtt features require an API key or account-backed cloud connection.

Should I use Govee LAN control or Matter?

Try the official LAN integration when the exact light is listed and the Govee app offers LAN Control. Use Matter only when that exact device has its own Matter QR or setup code; it is especially useful when that model's LAN route is unavailable or incomplete. Matter is local but may expose fewer Govee effects and segment controls.

Does Govee work with Apple Home or HomeKit?

A Matter-enabled Govee device can be added or shared to Apple Home through Matter. A Govee device already controlled by Home Assistant can also be exposed to Apple Home through Home Assistant's HomeKit Bridge, but that is not native Govee HomeKit support.

Why is my Govee model listed but not working locally?

The exact hardware version, region, device software, LAN setting, and network can still matter. Confirm the model and device software, enable LAN Control if available, keep the device and Home Assistant on a network that permits local discovery, and test Matter when the device supports it.