Open parautenbach opened 1 month ago
Was this introduced in the latest release?
HA or Multiscrape release?
I upgraded HA from 2024.9.1 (or was it 2024.9.3) to 2024.10.1.
I don't remember the previous multiscrape version I upgraded from, but I generally update all my integrations when I upgrade HA.
I didn't notice this issue before, as in, I didn't previously have my pollen automation run soon after an HA restart. Perhaps this always happened, but something in the start-up order or order of async events is causing this. I cannot really say.
I have the exact same issue which started happening from the latest release v8.0.2. On startup of HA a change of state is triggered while the state is identical to before restarting. The sensor has no attributes. Happens for all sensors, seems related to https://github.com/danieldotnl/ha-multiscrape/pull/417/commits/06cdc8a7ad3a1ee9fa9f5e911b3cea9c8bd87330
Version of the custom_component
8.0.2
Configuration
Automation:
Describe the bug
When I (res)start HA, I get a false positive notification from my automation. Given my automation config, it must be triggering on an attribute change, not the state.
Debug log
Automation trace info for the trigger: