Kept noticing things were in the wrong state and no reason why. I been checking the device events and just seen it happen right now.
Getting some that are turning off and some that turning on, it's only been since last few builds.
@bobbyD getting lots of errors from GH as well. Is there any known issues?
Is your screenshot and topic title supposed to suggest that Google Home is responsible for turning on the lights? If so, the screenshot isn't doing that: while cut off, "Google Home" is under the "Triggered" column for the event, meaning only that the app was woken up for whatever reason in response to the event (not that it was the cause). In the case of Google Home, it would be so that Google Home knows the updated device state.
To figure out what caused it, you need to look at the "Produced by" column and restrict your items of interest to only those with "command" in the "Type" column. For everything in your screenshot, it looks like that's just the name of the device itself, which either means it was done from the device detail page (manually) or, if you have any events without a preceding command, something in the device itself did it (built-in timer, malfunction, maybe Z-Wave assocation or Zigbee binding).
Yeah i thought this after i posted but there is nothing, so then it coming from the device.
Yeah that's what I thought at first, then realised that the devices were Zigbee, Konnected and matter thread, all basic ON/OFF devices using generic drivers. The only other link was google home.
Maybe there was a change in the generic drivers? Going to try and catch some more data.
Download the Hubitat app
