Atleast the errors in the logging provided are related to the installed Google Home app and the Govee LAN Integration. Both of which are built in apps.
1 Like
For some reason I noticed all my Govee lights are really slow. Ex I have Govee RGB strip light come on when motion is detected. Before there was a 1 or 2 second delay. But now it’s like a 30 second delay. Just started happening a day or two ago. I’m also seeing a lot of errors in the logs. I didn’t change anything, did a hub reboot some thing. I do have 14 Govee light strips. Maybe I should make some of these lights lan only maybe it will take off the load.
1 Like
The timeout errors are related to not being able to establish a connection to the Govee Cloud API Server. As i suggested above i would suggest reaching out to Govee Support and explain you are seeing timeout errors. It looks like they started again just after 12pm.
Changing your devices to LAN API will just help the devices work reguardless of the state of the Cloud API. I run everything i can with the LAN API enabled.
2 Likes
Sounds like it’s something to do on Govee side. And not with HE or the software within HE. Maybe Govee is having server issues. Is there any cons with running Govee LAN only?
It started with me 12 hours ago my non-lan API TV lights are very slow and seeing the same timeout errors in my logs also. I hope Govee is only having a performance issue and not making breaking changes.
1 Like
It’s good to know I’m not the only user having issues. This seems to be a Govee server issue. Like you said hopefully they didn’t change anything to give us users a headache.
Went into the Govee app and a few of my lights had an update. I updated one of them to see if that fixes the issues. I only did one for now to just in case the new update has issues with HE. Using the Govee app on WiFi phone and lights on WiFi everything is super fast no delay. The delay is only with HE automations.
1 Like
Yes for my TV lights there was a minor firmware update I did about a month ago. I also tested in their app and very fast. I am seeing the same as you.
1 Like
Most of my light were updated to 3.00.14 however this could be an old update as I never actually go into the Govee app. I went from .13 to .14 but makes no difference. I can still control govee in HE but it’s super slow it’s like I’m on a 56k dail up modem lol
Unfortunately we know for a fact Govee made changes to their Developer API because of the change that broke the SetEffect command. Since that change we have seen sporadic instances of these timeout events. I have been tracking it in my log server showing when devices start to get timeouts. It has been coming and going almost daily since that change. Prior i would get an occasional timeout here and there over several months.
Hopefully they are looking into it.
1 Like
100% something with Govee API as others said hopefully they look into it and fix it. Tomorrow I’m going to set one of my light strips to LAN and see if that fixes the delay.
That really is a possibility. I have seen that before for apps. A new call or process is introduced and it induces a unexpected load and then the app can't respond fast enough and the connection is considered timed out. Since the call was actually recieved though it process just really slow. @Sodfather experience would tend to lean to that being the case.
2 Likes
Yes, interesting lag.
I just received my first Govee lights and set up the bulbs for testing moments ago.
I noticed that I would try a few options and nothing would happen.
Then, 30 seconds later the colour would change and then another stacked command .... as I didn't realize they were taking so long to process.
Love the fun of playing with something new.
There's only 1800+ replies, what to do. 
I read the docs link at the top. Too may Prefs! 
Searched but didn't find a list of Effects in either.
One bulb has very little States and it's identical twin goes on forever?
Govee v2 Color Lights Driver. Bulbs are H6008.
There are many driver ver to choose from but that was the automatic choice.
Some of those states are populated by the cloud API. So if it is timing out that may be why it is failing to populate those states.
I think I'll save the madness for tomorrow.
For instance, I set a colour and intensity (bulb changes) and moments later the widget sets it to a different value.
And the logs, Oy vey, the logs.
It looks like things have been better since a little after 9pm eastern or about 1 hour ago.
I am also going to look at the way the calls are made from Hubitat to extend the timeout. Right now I am not specifying it, I am going to see about setting it to 60 seconds.
It wouldn't exactly help folks wanting fast response but would prevent all out failures possibly.
I also have mixed feeling about extending it out. Yes it would possibly make it work, but it also seems like it is just hiding a problem on Govee's side.
2 Likes
Mine seem to be working fine now. I have RGB light strips on motion sensors and they all been working super fast.
About 8:00 PM CT things went back to normal. I wouldn't mess with timeouts for API's calls just to cover up the issue int he cloud. I need those messages to prove to the vendor that there is issues or have them admit that they had issues. I did the same when working with the Ecobee Thermostats in it's early days of the API. Had all the facts they couldn't deny that they where having service issues.
2 Likes
