Using the built -in Govee integration doesn’t discover the devices. It comes up “No devices found on the network.”
The lights are on a separate subnet which I use for 2.5Ghz devices, so generally IOT things. I can communicate with other devices like Hue Hub and Elgato lights. The subnet is listed in the system network settings:
Is the built-in integration broken, as I can only seem people using the HACS ones? If so which HACS one works best for local control?
I’ve been having issues with the official govee integration for a little while so decided to reinstall but not I’ve reinstalled I’m getting the same issue you are.
Integration installs ok but when setting up it finds nothing, where previously it recognized 4 govee devices. all are connected to 2.4GHz, accessible in the govee app and all have the lan option enabled.
Bit confused…
I don’t get the integration installing, I just get it failing with no devices found. As no one had responded I just installed the Goveemqtt add-in and that found the devices immediately, so it would seem to be a problem with the built-in integration.
I’m also running into this issue. I’m hosting home assistant in a docker container, but with host networking so I don’t think it should have any issues with multicast device discovery. I wish the integration gave us the option of just supplying an IP address.
Same issues as described above. Don’t suspect any weird local network issues or MDNS problems. Hoping for a solution!
This is looks to be a known issue, it is only checking for devices on the primary interface. I tried disabling that interface but it still didn’t look to be checking the 2nd one. There is a fix waiting to be merged into HA. So I guess when that get released it should work>> Add multiple NICs in govee_light_local by itewk · Pull Request #128123 · home-assistant/core · GitHub
I guess you could possibly merge the changes yourself on your system but I’ve not done it before and don’t have time to research the process.
Having exact same issue here, recently got 2 H607C Floor lamps, Set in Govee app for API control. Install Govee Integration & put in API key & Integration installs fine, but does not see the lamps. Tried 3 times, removing integration & deleting Govee folder, but same result. Very frustrating.
FIXED IT!!
When in the add integration search, you need to type
“Govee Lights Local”
To get the correct integration (& it does not need an API key)
Lamps now visible & controllable!!
@kriscii i actually have this problem too, but my HA is on the same VLAN / subnet as the lights, the only thing i can think of is taht i allready have goveetomqtt installed that that si a problem?
I only have 1 nic on my HA box. HAOS is installed bare metal on a mini pc. HA and lights are on the same vlan, “No devices found on the network” error when trying to use Govee lights local
I am not an expert on it, just someone with a similar problem. Either you have a Wi-Fi adapter which, even if you are not using it, is the primary adapter or it is a different issue.
Looks like the device has a wifi adapter, however it is not in use (not connected to any ssid).
How can I address this?
Thx for the tip, this worked for me
How does this integration find the light controllers? I have 2 controllers on a different VLAN from HA. I have mdns enabled across the VLANs, but the integration still cannot find them.
Does it rely on broadcast? Is there a way to manually configure the IPs of the controllers?
@mwheeler not sure it how it locates the devices, I have mdns enabled as well. I’m thinking I might manually patch the files myself as per the change, just to get it working. I’ve not done it before so need to look at how you are supposed to do it to avoid issues with future updates.
I looked through the source code and found this:
const LOCAL_PORT = 4002;
const SEND_SCAN_PORT = 4001;
const CONTROL_PORT = 4003;
const M_CAST = '239.255.255.250';
When I do a PCAP looking for that address and those ports, I see that my homeassistant sends a UDP message to that multicast IP source port 4002 destination port 4001.
Looks like I need to get igmp proxy working on my router for this to be forwarded to the VLAN where my govee devices are.
I also found this in the code:
const devices: { [ip: string]: string } = {};
So you may be able to hard-code the IPs of your controller(s)
@mwheeler I just tried to look at how to add the changes to the goove local code. I thought I’d done it correctly but even after a full restart of HA I still get no devices found. I looked at mdns again against what you said you’d found I can’t see anything in my router that might help athough it runs mdns on port 5353 so not sure if that would cause issues I’ve not got enough time to do more research for the next few days.
@mwheeler Thought I’d have another go at it but although I now have the changes loading it is erroring with: Failed setup, will retry
You mentioned some settings but I’m seeing different stuff in the code, so not sure where you are looking, mine is:
CONF_MULTICAST_ADDRESS_DEFAULT = "239.255.255.250"
CONF_TARGET_PORT_DEFAULT = 4001
CONF_LISTENING_PORT_DEFAULT = 4002
CONF_DISCOVERY_INTERVAL_DEFAULT = 60
Resolved this about an hour ago. MQTT made this easy! Followed these steps: govee2mqtt/docs/ADDON.md at c9d27764095fabb1d1ee339ab187fc840cf00c83 · wez/govee2mqtt · GitHub
@jamesrweaver Yes, I had it working with Govee2MQTT, see my message on 2nd October. I had one device the ceiling light it was having problems, so wanted to try this. Also I’d rather have the built in support, as usually it is supported better. However, this is a case where the HA team are letting us down big time given a patch has been ready for ages but not released. Poor show on them.
I had the exact same issue… I had HomeAssistant running in Truenas Scale as an app, but just like many of you, I have one vlan for iot devices (actually exame same network Id (192.168.20.0) as Kriscii lol) and home assistant was running on my titan server on a 192.168.30.0). I put it on a pi 5 with HA OS and it found it straight away. Just make sure that on the govee device you setup a wifi and enable the LAN management api under the settings or it won’t recognise anything. Once I HA in the same vlan subnet as my iot devices (ie govee) it worked.