I fixed a error when fade was issued with a CT change. This was introduced with the prior release when a data type was manipulated to work with RM's fade over time.
Added a validation and additional logging in the Scene Extract process pointed out by @zigman76 above. Now the event will be captured and handled instead of throwing a error if a third rule is not present.
Added preloaded scenes for the H70C1 and H70C2 Govee Christmas tree devices.
FYI: The H7061 and H70C2 support b̶o̶t̶h̶ G̶o̶v̶e̶e̶ C̶l̶o̶u̶d̶ a̶n̶d̶ LAN API's per Govee support. I am still having issues with them right now as it took a day or so for them to activate the LAN option and the Cloud ability doesn't seem to be accessible yet. The lack of Cloud API means these won't be able to add yet via this integration, but as soon as the cloud is enabled they should start work. I am looking at possibly adding a manual device add for LAN devices to help in these conditions.
I don't know if everyone got this, but Govee has a survey open right now in the app regarding their API and what changes to make. I mentioned Hubitat, and a few other abilities I would like to see from their API.
I would encourage everyone to fill out this survey.
*** TLDR *** Once setup you can set the Polling interval on the device to 0 and it will be 100% local
The longer answer is kind of.
There are two things that the current integration can't do with the LAN API
The first is retrieve device status or get updates from the device. This is not a issue with the LAN Api but with Hubitat not allowing custom developed apps a way to access UDP Multicast Groups. I would love to be able to enable this, but unfortunately I am limited by what my options are to create listeners on the Hub.
The second thing and something I am strongly considering creating a work around for is the setup of the device. From the beginning of this integration I was trying to minimize setup the end user has to do. To do this we use the Cloud api to get most of the information for the devices and it is loaded as part of the device setup. For that reason all LAN API devices are initially setup with the cloud. I am considering creating a driver that can be setup without the Cloud API being configured. This is also something that could be easily remedied if we had the ability to listen to UDP Multicast group ports.
If you have something like Node-Red you can create flows to do the device status updates as well. I dabbled with that early on.
As @neonturbo points out this is the time for us to be heard by Govee. They have a survey going for questions about their API and based on a few things they are clearly moving it forward, so please log in and voice your needs to them. I have done so already myself.
This goes along with the above post. Simply put this change adds a new driver based on the full featured standard driver but stripped to be used with LAN API devices only and to be setup through the manual process in the Smartapp. This means there were some updates to the main app to facilitate this.
Going forward it will suggest you obtain and put a Cloud API Key in, but won't require it. If you don't have one entered you will not have the option to setup Cloud based devices of either Light, or appliance types. You also won't see configuration items that are used for or depend on the cloud. Once the Cloud API Key is entered and saved you will get access to setup those devices as before. This should be a non issue for most as you would already have that API Key Entered.
So now if you have a device that only support LAN API or you just don't want to interact with the cloud at all you can use it without needing a API Key. The only draw back at this point will be you won't get status updates from the cloud if you change it there.
You also get the option to do a manual setup of LAN only devices as well. This may help if a device is released and not available in the cloud for some reason but the LAN API is enabled
Several navigation changes in the app were made as well. It should now move you through certain process more naturally.
These changes also facilitated a need to do a bit more validation on certain tasks. If all of the information needed is not provided to complete a task you will be asked to try again.
As usual if you experience any issues at all let me know.
Love the app, I can’t find one feature and i think it’s cause Im using a dreamview T1 hardware H6199 and im looking to automate the video mode when my entertainment is switch on/off.. Am i totally missing it somewhere in the settings on your govee integration or is it a feature that’s not there?
I recently acquired the Govee RGBIC LED Permanent Outdoor Lights H705A, but I have not been able to successfully connected it to Hubitat. I have been the using te Govee Hubitat integration for some time with another light, but although I can select the new one and go through the add process, it does not show up in the device list. Am I doing something wrong? Thanks.
That error shouldn't happen as code was added a few versions back to prevent it.
That looks like you are running old code based on what line of code that error is complaining about. Please verify you are running the latest version of the code via HPM or by going to the Github repo and importing the app and drivers again.
Interesting as the package was installed via HPM, and showed as up to date (no update available). Anyway, I used the HPM repair function to reinstall and push the latest version, and everything work ad expected.
Thanks for a great app and awesome support!
A fix for a issue with the formating of preloaded scenes for the Permeant outdoor Lights.
Initial release of support for extracting commands associated with Snapshots. The goal is to allow a user to create a snapshot in the Govee Home app and then extract that to Hubitat if needed. This only pulls the special commands that are not related to on/off, Brightness, specific full device color or CT. This feature was asked for by @thinkfire . Hopefully others will find this useful as well.
I'm new to Hubitat and just set up my C-8 on Friday and the first thing I did was integrate my Govee bulbs I use for holiday decoration. Everything worked fine at first but now I'm getting an error that seems to happen when the device is updating or running backups or something in the middle of the night which causes the entire Hubitat unit to go unresponsive until I reboot it. The errors are:
dev:22023-10-22 01:15:55.679 AMerrorjava.net.UnknownHostException: developer-api.govee.com: Temporary failure in name resolution on line 413 (method poll)
dev:12023-10-22 01:15:55.679 AMerrorjava.net.UnknownHostException: developer-api.govee.com on line 413 (method poll)
I've got both the latest version of the Govee integration and the C-8 firmware installed. I can dig into the code when I have time but just wanted to report it as I'm new to the whole home automation thing in general.
Also is it normal for errors like this to hose the entire Hubitat system? The Govee integration is otherwise working just fine until this fires off. Ideally I'd like the Hubitat to report and ignore it or at least reboot if needed but I guess that's another thing entirely.
That error is showing that your hub is having a problem resolving the host name where the GoveeAPI resides. It isn't exactly reporting a Govee Integration smartapp problem, as much as it is saying your hub can't get to the Govee API to do a device status lookup.
This really shouldn't be hosing up the entire system. I suspect this error is more then likely a result of whatever is causing your issue. That said it is also not impossible that DNS has periodic issues for any host name.
I would suggest opening up a dedicated thread to troubleshoot this. I will look for it and try to help you get to the bottom of it. Make sure you include as much info about your setup as possible. You may also want to do a Soft Reset to make sure you don't have any DB Corruption causing the issue.
Off topic question for govee users in this thread. If anyone has the 100ft PRO permanent lights up and have them on an energy monitoring plug for energy data. Can you tell me how many watts it pulls at 100% and 50% brightness?
