# Stop Condition When It's Not Valid Any Longer **URL:** \ **Category:** Flows\ **Created:** [May 20, 2025, 9:43pm UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824 "2025-05-20T21:43:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Henric\_Waller](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henric_waller/32/80422_2.png) [@Henric\_Waller](https://community.homey.app/u/Henric_Waller)\ **Post date:** [May 20, 2025, 9:43pm UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/1 "2025-05-20T21:43:32Z")
I’m rather new in making flows, but have experience of PLC-programming. A difference that I have noticed is that a condition have to have a trigger(become a value or change). Rather often I want to have a condition that for example is _IF ? is larger than ? then…_, but instead I have use _When ? is larger than ? then…_. The difference will be that if the condition has already been met, then the condition will not go through. Is there any way to make such conditions? I have also noticed that if I have an AND-condition which will be fulfilled, but after a while looses the condition(the AND-condition is no longer fulfilled), the condition still continues to work. For example I have a condition for a maximum time. If the condition is valid for 60 minutes it will stop the controlled device. _IF temperature is larger than 30 degrees the FAN will start_ _IF the FAN is ON AND the Temperature is less than 20 degrees the FAN will stop_ _IF the Fan is ON AND the Temperature is more than 20 degrees it starts an DELAY for 60 minutes_ _IF the DELAY reaches 60 minutes the FAN will stop, regardless what the temperature is_ but I have noticed that even if the Temperature becomes less than 20 degrees before the DELAY reaches 60 minutes, the DELAY continues to count. The FAN will stop, but if the temperature reaches more than 30 degrees and starts the FAN again within the 60 minutes the FAN will be stopped when the DELAY reaches 60 minutes and it could be after 5 minutes after the FAN has been started again, depending how long it takes to reach 30 degrees again during the DELAY is counting. I hope you understand what I mean. If the Flow loses its condition, I want the Flow/Condition to be interrupted. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [May 20, 2025, 10:15pm UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/2 "2025-05-20T22:15:22Z")
> [@Henric\_Waller](#): > > DELAY Don’t use the built in delay for delays of more than a few seconds. Another ~~flaw~~ BUG when you use it for delays of (an) hour(s): it _does not survive a Homey reboot:_ you then can end up with unfinished flows without warnings whatsoever; And, as you’ve discovered: the delay isn’t interactive. My preferred timer app is [Chronograph](https://community.homey.app/t/18214); It can start & continue a timer, start and replace a timer (reset & start again), pause and stop a timer. And it survives a Homey reboot. This trigger card by [Device Capabilities](https://community.homey.app/t/43287) is way more flexible compared to the built-in ones: ![1000043063](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/5/a59d464257f9b9826c9b70e392f53c6d3397c988.jpeg) ![1000049036](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/3/0394a020d82552e413636586e18d6bfe7fd084fc.jpeg) ---
**Author:** ![Henric\_Waller](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henric_waller/32/80422_2.png) [@Henric\_Waller](https://community.homey.app/u/Henric_Waller)\ **Post date:** [May 21, 2025, 5:42am UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/3 "2025-05-21T05:42:33Z")
Thank you very much! I will test the Chronograph app. It sounds like the right funktion for my ”problem”. ---
**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\ **Post date:** [May 21, 2025, 7:29am UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/4 "2025-05-21T07:29:53Z")
> [@Henric\_Waller](#): > > The difference will be that if the condition has already been met, then the condition will not go through. This is indeed different when working with flows. You have to turn in around. > [@Henric\_Waller](#): > > _IF temperature is larger than 30 degrees the FAN will start_ IF temperature changed AND TEMP IS LARGER THAN 30 > [@Henric\_Waller](#): > > _IF the FAN is ON AND the Temperature is less than 20 degrees the FAN will stop_ IF temperature changed AND fan is on AND temperature is less than 20 ---
**Author:** ![Henric\_Waller](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henric_waller/32/80422_2.png) [@Henric\_Waller](https://community.homey.app/u/Henric_Waller)\ **Post date:** [May 21, 2025, 7:54am UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/5 "2025-05-21T07:54:49Z")
Yes, of course. That’s the way to solve it, working with changes. Thank you! ---
**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\ **Post date:** [May 21, 2025, 8:25am UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/6 "2025-05-21T08:25:22Z")
> [@Henric\_Waller](#): > > A difference that I have noticed is that a condition have to have a trigger A WHEN is not a condition. In general one has to start a computer program. By a user interaction as in starting MS-Word or with a scedular like a Cronjob for a backup. So also a flow should be started too, it does not run all the time in a loop😉. That is the reason why a flow is started with a WHEN card. A condition is statical, as an event in a WHEN card is dynamically. It could be a condition which state has **changed**. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [May 21, 2025, 11:18am UTC](https://community.homey.app/t/stop-condition-when-its-not-valid-any-longer/136824/7 "2025-05-21T11:18:37Z")
> [@Henric\_Waller](#): > > IF temperature is larger than 30 degrees the FAN will start This should work, but only if the _ **previous** _ reported value _ **was below** _ 30 degrees. It doesn’t trigger when the temperature changes from 31 to 32 degrees. It’s just a regular thermostat functionality. Same goes for “IF temperature is less than 30 degrees the FAN will stop”