Yes. This last update was almost all about LAN API updates. The LAN API really consists of 3 types of communication. Two of them use Multicast sockets so that a call out can go to multiple devices or a single connection can subscribe to listen to many devices. I suspect by having Hubitat on your main network instead of the same network with our Govee devices you are having this problem.
You will need to adjust your firewall rules to allow this communication. What do you use for firewall management gear. Is it Unifi or something else?
I am not 100% clear on how to setup the firewall rule as this is multicast socket connectivity and not ip to ip.
The communication that would need to be allowed across your networks is as such
Multicast socket 4001 from Hubitat to Multicast address 239.255.255.250 across vlans
Multicast socket 4002 to Hubitat from Multicast address 239.255.255.250 across vlans
UDP socket 4003 from Hubitat to Govee Devices. (This is probably already done)
Then of course firewall rules may be needed as well as they apply above these settings I believe. I know I set this and then added a firewall rule to limit inbound communication from my Home_IoT VLAN to my Default VLAN.
My first try with the help of Perplexi AI didn't work. However, I then paused the firewall rule that blocks IoT to Main and it still didn't work. I already had enabled IGMP Snooping previously.
Strangely, and this was happening before and I failed to mention it, from the Device page, I can change the color of the lights and the new values for Hue and Saturation change even though the Level & On/Off status do not. Additionally, I can set Hue and Saturation alone and get a change in status values but no change to lights. However, if I try to change just the Level, neither the status or light change. Finally, I can change Color Temperature and value changes in status and light changes.
In experimenting in seeing what would and wouldn't work, the light quit responding and this showed up in my logs:
This is very surprising to me. I really need to think we need to focus on one item at a time which we should start with figuring out your issue with firewall/cross-vlan communication. I suspect that is having a large impact on your results. Once that is squared away lets address anything else that isn't quite working right.
I suspect the errors you are seeing are from setting a time value on the set level command try leaving that at 0 so it doesn't do a fade and just sets the value.
I took my dev hub and changed it to run in my default VLAN to try to test this out. I tried a few things and couldn't get it to fully work.
In my basic setup I was able to get the devices status calls from the Govee devices back to my hub. Any time I told it to do a devices scan though I never got the responses from the devices. After reading back through the documentation this appears to be related to the Multicast Group not functioning between VLAN's. The reason the other items worked is because they are point to point communications between the device and the hub.
Online I am finding mixed comments on using multicast groups across vlan's. Would you be able to consider moving the Hubitat to the IOT Vlan?
I have debated for a long time moving all of my hubs including Home Assistant, Lutron, another HE hub, etc to the IoT network but afraid of breaking everything.
Maybe I will just experiment with moving this one. It's currently for running all integrations not related to Zwave or Zigbee so your integration, Home Assistant Device Bridge, Broadlink, Owntracks, etc.
By definition, all of these hubs probably belong on the IoT network instead. Something to consider....
Hub is now on the IoT network and seems to be playing nicely with your integration. Thank you for the kick in the pants!
I also moved my other HE hub as well as the Lutron Hub. Major things seem to be working but I am sure I will find minor glitches. Actually, my wife will probably discover them for me.
Yea. I suspected as much. Please leave you original post though.
One thing I would say though is we need to clearly explain/document the issue and bubble these issues up to support like @bobbyD or @bertabcd1234. This same issue keeps coming up in slightly different ways. If we want a fix we need to make sure they are aware of how it is impacting us.
Honestly at this point i wouldn't trust anything with the color picker. Instead specify the HSB values so you know exactly what to expect.
The problem is it is hard to avoid the color picker at times.
It depeneds on if the device is using Lan API for local Lan control and set to use a Local effect file or if you are using the Cloud API. I would suggest you look at the documentation for the integration.
I attempted the scene extraction process. I did use the documentation but of course Govee has changed the UI so it is a bit different. However, I created a new Tap-to-Run but was unable to successfully extract it. I followed the following process:
I entered the home group name that corresponds to one of my tap and runs. I then clicked on the "Extract Scene from Tap to Run" and the following screen appears:
@mavrrick58 I have a kinda silly question.. I got 2 Govee H60A1 lights and so far the simple things I've used works with the Govee v2 Color Lights 3 Driver which are really just on/off and setting Effects (or Senes, this still confuses the snot out of me lol). Anyways, I just realized with the Govee v2 Color Lights 3 Driver I can only control the device as a whole, and the H60A1 has 2 different light (or light sets), there is one light that lights downward (or direct) from the fixture and one that is around the top that lights up the celing (or indirect). I haven't been able to find a way to control them independently through the Govee v2 Color Lights 3 Driver, and don't see a unique driver (though I know making unique drivers is sometimes a pain) for the H60A1. I was wondering if you have any thoughts on how i could accomplish controlling the lights independantly through the Govee v2 Color Lights 3 Driver, or if you need anything to create a custom driver for the light, just let me know i'm happy to provide anything you need. And fyi, the light is LAN capable (and I am currently using it).
Thanks for your fantastic work and upkeep on this integeration. It really is fantastic. Side thought, do you have anything where I could donate to your efforts monitarily?
That driver supports the segmented controls. Have you tried those to see what if anything they can do for you with that device? You will need to review the Device state values for Segemented Brightness and color to know what is valid options and then you will need to enter them in the command with the proper format ie [1,2,3]
The main app looks at the reported command and capabilities from the Govee Cloud API and then selects the best driver based on that information. It isn't possible something was added for multi endpoint control, but f so it hasn't been added to any documentation yet. You can send me those values from the "Device Info" table from the devices and I can review it.
If the segmented control options don't work you can also set some scenes for the basics of what you want and use them as well.
In the main app if you scroll to the bottom and click on the About button there should be a link to donate a few bucks for some a meal or something. Thank you for considering it
I was curious if anyone has successfully extracted diy's after the updates to the Govee APP and the changes that have gone into the Govee Integration app.
