I have seen errors like that when your hub is busy and HPM has a problem installing the code because it can't get a lock. Did you try the upgrade a second time?
Yup, just ran it again (had to take drop the wife off for tennis) and it ran fine the second time! Thanks!
I just updated some drivers to 2.2.1. Please load this update if you already went to 2.2.0 as it would be highly recomended once upgraded beyond 2.1.x.
I found a fix that was placed on the drivers in the retry bundle got dropped at some point somehow. I assume it is related to all the back and forth i was doing. Fortunately something @FTimpani pointed out triggered me to go verify it was in place. It is a single line of code that was added to all of the Light driver devices. It also requires a specific condition to occur so it is unlikely you will trigger it as long as you are not making change to devices.
This code fix essentially just triggers a reset of all API State tracking values used by the retry logic.
I'm upated to 2.2.1 from HPM.
I had a net light not turn off last night, my other three devices all turned off. The net light showed online in the Govee app, and it turned off when I turned it off from its device page.
I've set logging to debug for tonight's 5pm start and will try to remember to re-enable debug if it turns off before 10:30pm when things turn off.
Everything turned on normally at 5pm...
I just posted new beta code.
- This code simply removes the Govee Space Heaters from the install flow so going forward they are not supported. Since they were all recalled this shouldn't be a issue
- In testing I found that the Humidifier devices were not installing properly with the correct driver. This has been resolved.
If you do not have a Govee Life Humidifier you do not need to worry about this beta release.
And everything turned off normally last night. Looking good!
Did the error just start after the most recent updates?
That seems to indicate the Govee Cloud API is being slow to respond to you.
Hello,
I was wondering how your Govee H60A1 ceiling light is working with Hubitat for you. I recently purchased one and I’m unable to get the scenes to work on the light.
No, it's been around for a bit.
I just thought it might be a product of WiFI and cloud inexactness.
Nothing turned off last night, all four devices were on all night. I missed it, so no logs. Turning on debug logging to try to catch anything tonight ... 
Things were back to normal again two nights ago, 2 strip lights and 2 net lights on/off as expected. Turned on and off again last night normally as well. Stable.
@mavrrick58 , I added the Govee ambient TV backlight kit H605A to Hubitat. It turns on fine with the TV, but reverts to a set color temp when turned on via the Hubitat device. How would I turn this device on so that it goes back into video mode where ambient effect reflects the TV image? This is not a LAN capable device so I don’t have an option to import a snapshot via the tap to run method.
Suggestions? I just want it to revert to the last used mode when turned on via Hubitat.
Actually, disregard. I was using a Room Lighting automation which defaulted to “CT” for the device type. Changed that to “Switch” and all good now as it no longer tries to load a color temperature and just turns the Govee backlight on.
Anyone getting their LED lights to come on unexpectedly?
All of my Govee stuff turns on at weird times and I can't get to the bottom of it.
I don't have any schedules on the app, in fact I haven't even touched the app itself when all this stuff started happening the last few days.
I requested a new API key just in case the other one was compromised. That hasn't helped. I have one device off wifi and it hasn't happened on it, so it's definitely cloud related.
I uninstalled and started fresh with the Govee Integration, it's still happening.
Do you use Echos/Alexa? There is a "Hunches" feature in Alexa that results in ligths turning on/off "randomly." Search for "Hunches" here and you'll find a bunch of posts about it. Not an Alexa user so don't remember how to turn Hunches off.
Maybe turn on debug logging for the Govee devices and see if you can get actual logs (not the Events page) from when the lights are turning on unexpectedly.
Considering you are using the Cloud API it would be interesting to see if the change for the state was captured from the device status call to the Cloud API, or submited on the hub.
The live logging would tell you that. I am a little heavy handed with debug logging so it would probably be pretty obvious which it was if you have live logging turned on.
In theory if a app on the hub was triggering it, You would see the app listed in the "Triggered Apps" column. Do you have the Govee devices integrated with other Home automation systems like Amazon Echo as @danabw mentions.
They are not linked. Nothing to do with Alexa or Google.
They were linked at one point. Looked at Alexa logs under hunches, nothing. Looked at the Google activity logs, nothing. I unlinked them. Still happened. Uninstalled Govee Integration and requested a new API key. Reinstalled Govee with the new API. Started happening again.
It's crazy, but they all turn on all at once, no rhyme or reason when. I went to bed early that evening so didn't notice them on until that morning.
It's been driving me insane.
Gonna turn the wifi on again for them along with the logs and I'll report back.