Trigger on duration issue #8782
Unanswered
Recte
asked this question in
Automations / scripts / scenes
Replies: 1 comment
-
Should have been an issue -> home-assistant/core#48584 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have this automation that triggers based on a device state duration, see image below.
It works like a charm as long as you don't edit and save any (other) automation while 'Ad Hoc 02' is turned on. If you do, it doesn't trigger until the next time it is turned on. I assume it is caused by the fact that all automations (that are turned on at the moment of the save) are reset (turn off and on again) at the save of an automation. This by it self is fine and probably has its reasons.
The current result however is that a device state duration is unreliable and thereby missing it value as a function from my point of view. Therefor I experience it as a bug/issue that I like to address.
I hope I gave a clear description of the issue I experience and of course hope anyone can/will fix it. The trigger by it self has great value (if it works reliable).
P.s. I worked around it by using a helper that is set at the time I want the automation to trigger. That works fine, but I'd prefer the device state duration.
Beta Was this translation helpful? Give feedback.
All reactions