I would like to make various automations back off when anything else overrides it, being manual change with a light switch, from web interface etc. Currently, my light automation remembers its last setpoint and compares changes to that, but it is not very good as some dimmers round to a different number, and sometimes they even report wrong level.
Are there other ways to find the source of the state change? I read something about “attribution” in a future version, maybe that could be a solution?
Awesome! Can you tell a bit more - how can HASS keep track when the reports are “asynchronous” (I think for Z-Wave, after I send a command, a seemingly unrelated report is given back with no sequence number or unique ID)?