Basic Rule trigger condition "has become and stayed above" stops working

I have created Basic Rule to monitor power consumption and to toggle power supply when power becomes above threshold 50 watts and stays there for 1 minute.

Newly created rule (or "reinitialized" with Done button) works normally in cases when power rises above threshold and stays there for 1 minute.
But it stops working in cases when power does not stay above threshold for 1 minute and falls below the threshold.

Basic Rule definition

Working case log

Faulty case log 1
In this case the power has become above 50 watts for less than 1 minute - something becomes broken in the rule/trigger and it stops working - until being "re-initialized" with Done button in Basic Rule definition screen.
Please note the messages "wait until [device] stays > null for ..." in response to power change events that start to appear after the rule becomes "broken"... For newly created or "re-initialized" rule such messages are not shown.

Faulty case log 2
All subsequent power change events that hit the threshold lead to some "continute waiting" messages but that do not hit the threshold lead to those "wait until [device] stays > null for ..." messages which are missing in "re-initialized" rule.

Is it some kind of bug with "has become and stayed above" trigger condition or I did something wrong with this rule?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.