Are they all at the same time. There is nothing in the integration that would allow it to go across devices and trigger actions like on/off ect.
Have you checked the Govee Home to see if there is anything setup in Auto-Run's that would account for it.
I just don't see how this is related to the integration,
I don't think it's the integration myself. I set up the logs for "info", if that's wrong, let me know.
I uninstalled the Govee app and reinstalled it. There's no schedules set. There is absolutely no Alexa or Home integrations. I didn't even push the devices over to them. Strictly Hubitat and Govee App.
If it happens again, I should be able to see if it's the API calling or hubitat.
Would be weird because I used a new API key and it's still did it.
From the screen shot above It looks like you are using the Cloud API. So that means the devices are getting commands from the Govee Cloud. Even when you submit commands through hubitat, they get sent to the cloud and then come back to your device. Do you have any setup for Local Lan Control?
Pick one of the devices on hubitat and open up it's preferences page. Turn on Debug Logging and click on "Save and Close". If you have devices that have "Local LAN Control" turned on you may want to do the same for the "Govee Device Manager" device. If you set something to Info that was probably for the Govee Integragtion app. That probably won't give you anything. That logging would help for issues with Scene extraction or installing devices.
What you are looking for is basically a command submitted to change to that given state, or was a poll done to get the device status that had the new state without it being submitted from the Hub itself.
What i suspect is you will see a poll executed that recieves the new state and updates the device with a event to change it. At that point check for Auto-Runs in the Govee Home app and probably change your password.
They turned on again. Unfortunately didn't see this so didn't capture the logs.
Gonna change password as suggested.
Any chance the info logs might be in your past logs? Filtering them by the Govee device might provide you with what you’re looking for. Alternatively, you can check the devices’ events to get a clue to what triggered the « on » event.
Here's some of those logs for one device. The ON event happened at 3:41. I turned it off myself when I noticed them on.
Also seeing driver errors on another device
Unfortunately that doesn't help.
I need to be able to see the event that put in the on status which isn't there. I do see that after you updated the preference to enable debug logging the driver performed a getDeviceState() which gets the device current state and it did show it was on at that time. It didn't submit an event though because it was already in that state.
Now that debug logging is on we can get that information the next time it occurs
Just updating. Not going to jinx it, but I have nothing to report.
Download the Hubitat app
