Add support for filling in IP in Govee Local API (VLAN Issue)

[Vato9394]

The problem

At the moment, the integration is doing a broadcast request, it should be nice to have an option to choose a specific IP address, especially because some people are using IOT vlans and this is not always working properly.

What version of Home Assistant Core has the issue?

2024.2.0

What was the last working version of Home Assistant Core?

n/a

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Govee lights local

Link to integration documentation on our website

https://www.home-assistant.io/integrations/govee_light_local

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @galorhallen, mind taking a look at this issue as it has been labeled with an integration (govee_light_local) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of govee_light_local can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign govee_light_local Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

govee_light_local documentation govee_light_local source _{^{(message by IssueLinks)}}

[joostlek]

The whole protocol works via UDP and can't be specified to a single IP iirc

[Vato9394]

Can we somehow solve this another way? Specify the broadcast address for example?

[Galorhallen]

Can we somehow solve this another way? Specify the broadcast address for example?

It cannot be changed right now, but the broadcast address is the one the devices joins and it is used for discovery, change it would break it.

Once the device has been discovered commands and status update requests are sent to the device IP directly. I think that the integration could be extend to have a devices added manually, but I need to do some checks to be sure.

[CDAutomate]

Also have the same issue. Currently using the HACs Govee LAN Control

[andyblac]

atm the moment I use https://github.com/wez/govee2mqtt and I have to enable the following option, Is this something you can add to this integration ?

[Vato9394]

This is also an option in the same addon

[mediacrave]

I'm having the same issues.

Initial discovery works and then after a reboot everything breaks.

[Galorhallen]

This is also an option in the same addon Hi, i'm currently working on something like this.

Initial discovery works and then after a reboot everything breaks.

What is the error on reboot? Can you please attach some logs?

[joostlek]

@Galorhallen sent you a message on discord

[mediacrave]

This is also an option in the same addon Hi, i'm currently working on something like this.

Initial discovery works and then after a reboot everything breaks.

What is the error on reboot? Can you please attach some logs?

Sorry, was on my phone earlier.

The integration just keeps failing to initialize after a reboot: 2024-02-07 15:23:04.335 DEBUG (MainThread) [homeassistant.components.govee_light_local.coordinator] Disconnected 2024-02-07 15:23:44.824 DEBUG (MainThread) [homeassistant.components.govee_light_local.coordinator] Finished fetching GoveeLightLocalApi data in 0.000

It looks like it fails without even properly trying. If I remove the integration and re-add it, it works until I reboot home assistant.

[Lincoln-Jones]

Also would love to use this integration but having my Govee lamps on my IOT VLAN makes it impossible.

[011V32]

I also had bevor the Govee LAN Control for Home Assistant and it worked without problems. But my device is H61BE which is not listed (but it even didn't find it) ...

[gmstrowabarton]

Also same issue all Govee product are on a IOT VLAN and are not discoverable even when I start the integration I have been using the Govee to MQTT bridge for Home Assistant Add-on as of late with not too many issues except on reboots. Wanted this to work but had to go back to the previous control which uses the Govee API.

[Snowrisk]

Same here. Using IOT VLAN and my Govee is not discoverable.

[andyblac]

just an update from me, I have recently switched my router from OPNsense to a Unifi Gateway Ultra, and the integration is now detecting my devices fine on my IoT VLAN.

So I suspect it is a mDNS multicast issue or firewall issue on OPNsense not allowing / routing the mDNS packets.

[Vato9394]

I have an unifi gateway, and the integration is not detecting it. @andyblac Unifi is ALLOWING traffic between vlans by default. you have to make a rule to block it, and allow only the ports to only the hassio server. after this, this integration is not working anymore between Vlans. The other integration mentioned before is working accross vlans.

[andyblac]

I have an unifi gateway, and the integration is not detecting it. @andyblac Unifi is ALLOWING traffic between vlans by default. you have to make a rule to block it, and allow only the ports to only the hassio server. after this, this integration is not working anymore between Vlans.the other integrsrion mentioned before is working accross vlans.

my Home Assistant server is sitting on the same VLAN as my IoT, I know that have to open ports, I also open ports for IP 224.0.0.251 that the default mDNS broadcast IP.

[Vato9394]

@Galorhallen any updates on this issue? any chance to add "add device manually function"? Still using this add-on https://github.com/wez/govee2mqtt but native would be "nicer"

[Galorhallen]

Hi @Vato9394, I've no news on the issue, I'm still investigating it. For sure something like entering a list of "manual IP" could be a workaround, but I'm trying to find the culprit of the problem.

I too have a unifi gateway but for some reason the Govee multicast is not crossing the the VLANs (actually it doesn't cross VLANs only if the "target" device is on Wifi).

@andyblac Govee doesn't use standard mDNS address, it uses 239.255.255.250 iirc.

[JOHLC]

I also ran into this today with my first Govee product. Going to try setting up the govee2mqtt addon. I agree that native would be 'nicer' as well.

[kanzie]

Joining the choir, would love to see this getting some attention as it is currently not working for me either. I beleive @Galorhallen is on to the issue here. So ability to add additional IP, or that the IP is changed to the one used by these lights

[grigorgeous]

Same issue here. Spent 3 days fighting with it. I tried everything to allow multicast between LANs -- IGMP proxy, firewall rules, VLAN tagging, adding second IP on the same VLAN to HA OS, etc. Nothing helped. Worked like a charm when all devices were on the same VLAN.

[danielebra]

Same issue here. Spent 3 days fighting with it. I tried everything to allow multicast between LANs -- IGMP proxy, firewall rules, VLAN tagging, adding second IP on the same VLAN to HA OS, etc. Nothing helped. Worked like a charm when all devices were on the same VLAN.

Hey @grigorgeous, have you tried https://github.com/wez/govee2mqtt? I am using that with direct IP address of the Govee device across VLANs. I went down the same rabbit hole you mentioned 😅

[011V32]

Have someone tried NAT Masquerading?

[grigorgeous]

Hi @danielebra, no, I haven't tried it so far as I used native integration before I started to introduce VLANs in my network. Feature-wise, is it the same or not?

@011V32 I have NAT Masquerading enabled by default but that doesn't solve the issue.

[011V32]

@grigorgeous What do you mean with "enabled"? (I didn't mean NAT masquerading on the WAN port, but an extra NAT masquerading between the VLANs/subnets.) Thx

[kanzie]

That’s set up by default when you have multiple vlans on UniFi network and I can confirm this does not solve the problem. I went with the mqtt solution to make it work myself

On Tue 27. Aug 2024 at 15:56, 011V32 @.***> wrote:

@grigorgeous https://github.com/grigorgeous What do you mean with "enabled"? (I didn't mean NAT masquerading on the WAN port, but an extra NAT masquerading between the VLANs/subnets.) Thx

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109993#issuecomment-2312639594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGFGAAREAYYH7POLJYBPPLZTSASVAVCNFSM6AAAAABC7TXUW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGYZTSNJZGQ . You are receiving this because you commented.Message ID: @.***>

[011V32]

That’s set up by default when you have multiple vlans on UniFi network and

I can confirm this does not solve the problem. I went with the mqtt

solution to make it work myself

@kanzie I also use UniFi and NAT masquerading is not done automatically (why should it be?). The configuration itself was only recently added with version 8.3.x.

[grigorgeous]

@kanzie @011V32 @danielebra Hey guys, I've just fixed the issue. In my IGMP Proxy setup, I had IoT VLAN upstream and HA VLAN downstream. When I switched it, it started to work. Ensure HA VLAN is upstream. I have IPs assigned to HA OS in 2 VLANs. I will remove the IP in IoT VLAN to check if it still works. It didn't work with 2 IPs before my IGMP Proxy settings were changed. Let me know if that helped.