# \[Feature Request\] Configurable max wait time on "ALL" card

**URL:** <https://community.homey.app/t/feature-request-configurable-max-wait-time-on-all-card/94773>\
**Category:** Ideas & Suggestions\
**Tags:** featurerequest\
**Created:** [November 15, 2023, 10:47pm UTC](https://community.homey.app/t/feature-request-configurable-max-wait-time-on-all-card/94773 "2023-11-15T22:47:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jepke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jepke/32/80488_2.png) [@Jepke](https://community.homey.app/u/Jepke)\
**Post date:** [November 15, 2023, 10:47pm UTC](https://community.homey.app/t/feature-request-configurable-max-wait-time-on-all-card/94773/1 "2023-11-15T22:47:51Z")

</div>

Configurable max wait time on ALL card + true / false output.

Input 1 triggered + input 2 within allowed max time output true  
Input 1 triggered + input 2 exceeded allowed max time output false

When having multiple device actions + sensor states that have to wait on one or the other to do the next thing or even if the whole flow fails because of a sensor state restart the flow. Having a configurable “ALL” card would make rather complex flows with using a bunch of logic cards a whole lot easier.

eg. Driveway gates or garage doors. When closing these you roughly know the X seconds it takes to close.  
Example situation:  
Sensors that detects vehicle left is closed → command given to close door/gate → #input1 “ALL”  
then wait for #input2 door/gate closed sensor. If #2 is in closed state output true but it it isnt within the allowed time frame, do something else (send notification / retry to close)

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [November 16, 2023, 4:09am UTC](https://community.homey.app/t/feature-request-configurable-max-wait-time-on-all-card/94773/2 "2023-11-16T04:09:36Z")

</div>

You could use the chronograph app to start a count down timer from yout first input trigger. When the timer reaches zero, and input #2 state is true, then all is fine, else send a notification.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [November 16, 2023, 5:59am UTC](https://community.homey.app/t/feature-request-configurable-max-wait-time-on-all-card/94773/3 "2023-11-16T05:59:43Z")

</div>

> [@Jepke](#):
>
> on ALL card + true / false output.

Inputs and outputs are not true or false, it are events

> [@\[FAQ\]\[Advanced Flow\] Infinite canvas. Infinite creativity](https://community.homey.app/t/faq-advanced-flow-infinite-canvas-infinite-creativity/65145/1):
>
> **Two triggers to start an ALL**  
> Also applies to all other different **triggers** b̶e̶h̶i̶n̶d̶ before an ALL like “Someone came Home” AND “the door is opened” =\> That is NOT going to trigger NEVER!

> [@\[FAQ\]\[Advanced Flow\] Infinite canvas. Infinite creativity](https://community.homey.app/t/faq-advanced-flow-infinite-canvas-infinite-creativity/65145/119):
>
> Correct, Therefor it isn’t called an OR , they (Athom) created an ANY, that just triggers it output on the first incoming trigger of a pervious card. So maybe start “[Flip-Thinking](https://www.omdenken.nl/inspiratie-en-verhalen/nu-in-het-engels-huh-the-dutch-art-of-flip-thinking)” The evaluation of a condition can be True Or False, continuing a trigger in the upper or lower Niple wink (I L :heart:ve that one ) But Continuing al Lower Niple wink trigger isn’t True or False it is the result of an Evaluation that was False. Although it isn’t True or False on it’s own. Especially when i…