Not quite sure where this is coming from but it's new on this build.
From Room Lighting app and Govee Integration. @mavrrick58
I'll investigate more or roll back if it continues; not much time to fiddle right now.
I rebooted and have this so far:
Before reboot, pages of errors:
This evening i started to notice several cloud API calls taking to long. It is possible that is related. It certainly looks like something with the Govee integration though. I will start to take a deeper look.
If you are experiencing long calls please open a support ticket with Govee.
If the API is this jacked up and timing is so far out there, there isn't much i can do about that. We just need Govee to fix the problem. That said i am not liking how the integration is failing. I need to look at some things to see if i can make it fail more gracefully on the hub.
So far my log errors stopped at 20:17.
I think a nice little, Disable/Enable Integration switch would be enough.
What time zone?
PST, -7 UTC
Forum software hates small replies, so blah, blah, blah. 
Very interesting.
I was using the LAN API stuff, but it was not working well at all at 22;49 CT (UTC -5).
But when I tried again at 22:54 CT (UTC -5), it worked like a champ.
That's why I wondered about your time zone-I wanted to correlate the two!
Thx
Here is a snippit from my Syslog Dashboard that just shows the sendCommand message from my hubs. Any time a Cloud API Call goes over 10 seconds it generates one of these messages. Some of them in the worst time last night were over 1 min. I also had many Timeout failures as well around those 1 min calls. Those are similar to what @dnickel had above.
There is no doubt Govee had some major issues last night, They are better today, but it is still not perfect. This also highlights I need to do better with handling these failures. i guess i know what my next update will be.
Here you can see the worst times were the calls were around or over 1 min or just outright failing.
Things are getting a bit weird again. @mavrrick58
