I have my HA connected to both vlan’s one on the NIC and the other on WiFi but it only searches the primary network (NIC), which is my main vlan. The vlan Govee is on is all 2.5ghz only devices plus the things I don’t trust to be on the main vlan. I have devices on both vlan’s and as mentioned already there is a fix to cope with multi-LAN HA installs but it hasn’t been released.
I was having the same problem, and it wouldn’t find my Govee device. What I did was go to the Govee app, click the item I want to add to HA → go to settings, then in settings, turn on LAN control. That got it working
That isn’t the same issue. This problem is people that have their devices in a different subnet to their HA server’s primary network card and are unable to get the devices found, we already had LAN control on.
I think this explains my issues since HAOS runs a virtual Lan. It’s sits in 169 & 172… and the main LAN is 192…
I’ve been struggling for a while HA just doesn’t see anything when installing Govee Local.
Seems I wait for the release of the fix?
switch on LAN control in the Govee Home app
2 Likes
?? If you read above this issue is not related to Lan Control being switched on. That works but Home Assistant doesn’t recognise devices on different subnets to the LAN it’s primary NIC is attached to. There is a patch but nobody in the HA team seems to want to sign it off.
Just switched my old outdoor lights for Govee outdoor lights, to find out my HA can’t find the new lights. I enabled LAN control, but it is on another subnet. I have read through this topic and wanted to know if the patch has already been approved by someone of the HA team?
Unfortunately it hasn’t.
Luckily, I found a solution a couple of hours ago. I use the Govee2MQTT add-on. It only requires a local API setup.
Furthermore, I created a bug issue, as I noticed that none of the 6 issues for the official integration mentions this problem and I made a reference to this issue.
My guess is that the Govee integration has changed ownership.
@kriscii i have the same setup, HA installed on a docker and i can’t get govee local lights added. As suggested by others, i already turned on the LAN settings in the Govee mobile app.
yup, another +1 for not being able to find devices on a different vlan. A shame the PR has been open for nearly a year and marked as stale. With a native integration, users shouldn’t have to use a third party addon. Like others, I’d rather use an officially supported integration.
1 Like
Same here … multiple network interfaces and not discovering the devices, cause default interface is in another subnet.
So +1 for fixing this …
I think the issue is that the local integration absolutely won’t let you configure how it detects devices. This means that the moment your LAN setup gets slightly weird (e.g. by running HA in a VM) the detection fails and there is no way to fix it. I would settle for providing IPs manually if this were an option.
qovee2mqtt is, so far as I can tell, NOT a local solution. While some local control methods are advertised, I have seen it rely on the govee API even when it has detected lights locally (generally resulting in a second or two delay and slow status updates), and there does not seem to be a way to tell it to just use local methods.
I’m also having this issue. I had the light working and then upgraded my network to UniFi and put the light on another subnet and now the integration can’t discover it.
I got it to work finally after enabling IPv6 on the network (I also moved HAOS and the lights in the same network). My setup is HAOS is running on a RPi4, the gateway is ubiquiti dream machine and I enabled IPv6 on my dream machine.
my new Govee device is on the SAME LAN as everything (I only have 1 LAN). and yet Govee light local can’t even find it !
and using Thread with HA’s Thread server doesn’t work well, especially with colors, I need to ask twice for a color for it to change.
Can you see the device model in the list of supported devices?
It is. (H6076)
Even with Govee2mqtt add-on, I get:
>
> [2025-09-04T11:29:19 INFO govee::commands::serve] Starting service. version 2025.04.13-17d43d72
> [2025-09-04T11:29:19 INFO govee::commands::serve] Querying platform API for device list
> [2025-09-04T11:29:19 INFO govee::commands::serve] Querying undocumented API for device + room list
> [2025-09-04T11:29:20 INFO govee::service::iot] Connected to IoT: aqm3wd1qlc3dy-ats.iot.us-east-1.amazonaws.com:8883 CONNACK code 0: Connection Accepted.
> [2025-09-04T11:29:20 INFO govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
> [2025-09-04T11:29:20 INFO govee::commands::serve] Starting LAN discovery
> [2025-09-04T11:29:20 INFO govee::commands::serve] Waiting 10 seconds for LAN API discovery
> [2025-09-04T11:29:20 ERROR govee::lan_api] process_packet: Parsing: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}: govee::lan_api::ResponseWrapper msg.data: missing field `ip` at line 1 column 188. Input: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}
> [2025-09-04T11:29:22 ERROR govee::lan_api] process_packet: Parsing: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}: govee::lan_api::ResponseWrapper msg.data: missing field `ip` at line 1 column 188. Input: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}
> [2025-09-04T11:29:26 ERROR govee::lan_api] process_packet: Parsing: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}: govee::lan_api::ResponseWrapper msg.data: missing field `ip` at line 1 column 188. Input: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}
> [2025-09-04T11:29:30 INFO govee::commands::serve] Devices returned from Govee's APIs
> [2025-09-04T11:29:30 INFO govee::commands::serve] Floor Lamp Basic (5F:EC:DD:99:82:06:14:46 H6076)
> [2025-09-04T11:29:30 INFO govee::commands::serve] Platform API: devices.types.light. supports_rgb=true supports_brightness=true
> [2025-09-04T11:29:30 INFO govee::commands::serve] color_temp=Some((2200, 6500)) segment_rgb=Some(0..7)
> [2025-09-04T11:29:30 INFO govee::commands::serve] Undoc: room=None supports_iot=true ble_only=false
> [2025-09-04T11:29:30 INFO govee::commands::serve] Quirk { sku: "H6076", icon: "mdi:floor-lamp", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, platform_temperature_sensor_units: None, platform_humidity_sensor_units: None, iot_api_supported: true, show_as_preset_buttons: None }
> [2025-09-04T11:29:30 WARN govee::commands::serve] This device should be available via the LAN API, but didn't respond to probing yet. Possible causes:
> [2025-09-04T11:29:30 WARN govee::commands::serve] 1) LAN API needs to be enabled in the Govee Home App.
> [2025-09-04T11:29:30 WARN govee::commands::serve] 2) The device is offline.
> [2025-09-04T11:29:30 WARN govee::commands::serve] 3) A network configuration issue is preventing communication.
> [2025-09-04T11:29:30 WARN govee::commands::serve] 4) The device needs a firmware update before it can enable LAN API.
> [2025-09-04T11:29:30 WARN govee::commands::serve] 5) The hardware version of the device is too old to enable the LAN API.
> [2025-09-04T11:29:30 INFO govee::commands::serve]
> [2025-09-04T11:29:30 INFO govee::service::http] http server addr is 0.0.0.0:8056
> [2025-09-04T11:29:34 ERROR govee::lan_api] process_packet: Parsing: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}: govee::lan_api::ResponseWrapper msg.data: missing field `ip` at line 1 column 188. Input: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}
> [2025-09-04T11:29:50 INFO govee::service::state] requesting update via IoT MQTT Floor Lamp Basic (5F:EC:DD:99:82:06:14:46 H6076) None
> [2025-09-04T11:29:50 ERROR govee::lan_api] process_packet: Parsing: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}: govee::lan_api::ResponseWrapper msg.data: missing field `ip` at line 1 column 188. Input: {"msg":{"cmd":"scan","data":{"device":"5F:EC:DD:99:82:06:14:46","sku":"H6076","bleVersionHard":"3.05.00","bleVersionSoft":"1.04.05","wifiVersionHard":"4.01.00","wifiVersionSoft":"1.00.16"}}}
> [2025-09-04T11:29:51 INFO govee::service::hass] Wait 150ms for hass to settle on 15 entity configs
> [2025-09-04T11:29:52 INFO govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
@1aranzant this thread is about issues for people with multiple NICs you may do better to ask a new question in the community.
For everyone waiting for a fix for multiple NICs it was supposedly included in 2025.9 but I have tried it and no luck for me, still the same error. Hopefully others will have better results.
Try turning off IGMP snooping in your network if you have it enabled.