"Already running" New automation bug?

OK so here’s an update for Z-Wave - we have what we think is a fix that will go into beta on Wednesday. Would appreciate any help testing the fix as I am not running into the problem myself.

If you’d like to learn more details about the problem we think we found, see here: Automations marked as "Still Running" After Upgrade to 2023.7 & 2023.8 · Issue #98073 · home-assistant/core · GitHub

3 Likes

Please let me know if you still experience issues with zwave after updating to 2023.9 which has the potential fix (but looking for confirmation!)

1 Like

Hi, sorry for hijacking.

I experience the same problem with a hanging automation. Its rather complex and involves several triggers based on state changes of a Phillips Hue motion sensor and Aqara contact devices (all of them being zigbee, not z-wave). It should activate my SonosOne when entering the bathroom which worked fine for more than one year now. According to the automation trace it stopps immediately after the trigger fires and will add the warning to the logs. The odd thing is that my lights (managed by the Hue bridge, not HA) turn one and off as usual. So motion is detected correctly.
Any idea?