The LAN API uses UDP protocol to talk to the device. UDP is kind of a fire and forget it protocol without packet verification like TCP. Or simply put with UDP just because the hub sent the command, there is nothing making sure the device actually recieved the command. If the command get lost by the wifi gods then this could happen. You could do some kind of validation were you submit the command twice, or validate it after a time.
I suppose but the controllers are less than 20ft from the hub and they have never failed to turn the devices on. That may just be coincidence though. I'll add some type of verification to the rule. Thanks for taking a look at it.
I meant router, not hub, Sorry about that. So used to ZigBee and z-wave when dealing with hubitat that "hub" just automatically comes to mind. I have added checking to try and overcome what may be UDP shortcomings.
The best way yo check would be go into the settings for the device and see if the option to turn on LAN Control appears. It can take up to 15 seconds. If it does then the decice supports it. If you have some devices already that support the LAN API the. You can do the same and click on the documentation link next to that option to get the latest list.
If it does not then you would be limited to the Cloud API. It is extremely likely it supports the Cloud API.
As of right now i dont see any notice of any new devices being added to LAN control.
@DenverTech99 probably 3-4 months out, but Govee just announced some feature updates for Govee Home 5.6. It appears more devices will get Lan support and two of them are the two different lenths for the Perm outdoor lights. So it looks like you will be getting what you wanted.
Hello, I am brand new to the Hubitat community Ultra Newbie (Coming from someone exclusive to Apple HK via Home+ App).
I want to start by thanking you for offering GoVee support for HE. I am looking forward to learning how to go about this process with the overarching goal of integrating GoVee into HK via Virtual Switches.
At this time I am beyond lost, I have successfully downloaded the Drivers and App Code you have graciously created. I have also checked LAN Support within the GoVee App and requested an API Key (Pending). Once this API Key is received, I am lost at how one would go about now physically adding a GoVee product to HE. I have looked through the coding and noticed several areas where it says add API Key and requests numbers.
I know this is not a logical ask, however, is there a guide or image that can show a step-by-step walkthrough on how one achieves this? or perhaps if something like this even exists. I know this is not a small ask and I am likely far over my head, but I truly want to understand this powerful hub.
I want to thank anyone in advance who could possibly provide direction and how to tackle such a mountain for someone as green as myself.
Once you have the Govee API Key you will simply cut and past it into the field in the first screen on the Govee integration app. To install a new app you need to click on the apps section of the Hubitat Ui and then click on the button to user add apps in the upper right corner. Once that is done a new box will appear and you should be able to scrolld down and find the "Govee Integration" app. Click on it to install the smart app. It will now appear in the installed apps list. Now you should be able to open up the app and put in your API Key and such as shown in the first post in this thread to setup your devices.
Once that is done and your devices are added to HE, then you will need to install the built in app for Homekit Integration. Follow it's directions to get setup and connected to home kit. Lastly you will need to go through the exercise of creating the virtual switches and rules to create the translation between HE and Homekit, Keep in mind this is getting into not exactly advanced setup, but certainly not the easiest thing either. I don't have HK so I will help as far as I can.
I would say start with getting your API Key and getting your devices integrated with HE using the Govee Cloud. Once we have all of your devices added we can then get HE setup to communicate with them via LAN Connectivity to help with Rate limits. After we have all of your Govee devices working right with HE then we can start to tackle HK integration and how the rules will probably need to look.
Also unless something has changed it shouldn't take very long at all for you to get the API Key in your email. If you don't already have it check your junk mail in such.
Thank you, for the extremely fast and easy to learn reply. well I am off to an embarrassing start :).
I have received my API Key and went through the App process of adding the device to HE. I was able to choose my device, click done and it stated 1 item was added.
Is the Cloud or LAN auto setup? I turned on Hub Mesh in HE.
The integration by default uses cloud and the API key is all you need with this method to setup access for a device using the Cloud.
Lan has additional steps because of a few things. Probably the most important is that the device has to keep the same IP address so Hubitat always knows how to communicate with it. If you want to use the LAN api then you will need to setup a DHCP reservation on your router so the Govee device keeps the same IP. Once that is done you will want to go into the device on HE, scroll down and change the switch to say you want to use Lan Control. When you click on save you will have a few new options appear. 1 is to set the IP Address so Hubitat knows who to talk to and the other is to set the fade change rate(Don't worry about this for now). Click on save again and it should now use the Lan API to communicate with the Govee Device.
Because of a limitation of HE and how the Govee Lan API works we always use the Govee Cloud to get device Status though so the cloud is always involved to some extent.
Sticking with the cloud is certainly the easiest and unless you run into rate limit issues there is no reason to have to use the LAN API.
There are 2 reasons to use the LAN API:
You are hitting rate limits. This gets easier the more devices you have, and depending on your habits can be a problem.
You want to use the option to fade up or down over time. The Cloud api doesn't support this option and if you used the Lan Control method it would quickly kill the rate limits.
The Govee drivers I have won't make it through the HK integration so you will need Hubitat native Virtual drivers to act as the middle man. You can name them however you like though so they make sense. You have the idea above though correct. Depending on how much control you want from HK you may want to try a more advanced virtual driver that can also control colors and brightness to.. But start small and work you way there..
I think there is also a built in mirror app you may want to try as well. I haven't used it myself, but it may be helpful for this.
One more thing to mention is make sure you have your hub at the latest firmware. There has been some growing pains with the Homekit integration so being on the most recent version of firmware is important.
Thank you, yes I have upgraded the firmware to the latest version.
I can imagine the challenges with getting Color options to be displayed in HK with virtual dimmers. I do not believe there are any available options as of yet. I have been searching but coming up with no resolve at this time.
Your integration works excellent in HK regardless!
@mavrrick58 The occasional dropped "off" commands do appear to be caused by the device missing the command on the WiFi network. Sending the command a second time seems to have fixed it. I have never seen it with the half dozen or so Kasa switches but they not be using UDP either, IDK. Again, thanks for your guidance and all of the work on the integration. I almost have it working exactly as I want.