# \[FeatureRequest\] Advanced flow delay by numeric variable **URL:** \ **Category:** Ideas & Suggestions\ **Tags:** featurerequest, advancedflow\ **Created:** [November 3, 2025, 4:58am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873 "2025-11-03T04:58:36Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![GrayV8](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grayv8/32/178444_2.png) [@GrayV8](https://community.homey.app/u/GrayV8)\ **Post date:** [November 3, 2025, 4:58am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/1 "2025-11-03T04:58:37Z")
Hello all, I have what really is a feature request for Athom I guess, as there has been quite a few requests similar and the normal response to those has been “use Chronograph”, start a timer, run a different flow when timer ends, etc., etc. However, I do not want to do that, and for ease of flow logic and simplicity it is not a valid or good solution for me. What I simply need is for the advanced flow “Delay” option to have a variable tag selection, rather than only a fixed numeric amount. To me this seems very obvious and sensible; however, I’m likely not understanding why this might be difficult to accomplish in the underlying code. Nevertheless, my request is that Delay would have: 1. current option where your type your specific delay amount number, and select sec or min. 2. tag selection to select a given numeric variable name, and also then select sec or min. Does anyone else agree that this would make things a lot cleaner and easier, at least in some circumstances? It really seems like something that should have been created from day 1 of “Delay”, but…maybe that’s just me. Cheers, Gray. ---
**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\ **Post date:** [November 3, 2025, 6:38am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/2 "2025-11-03T06:38:03Z")
The downside of a (long) wait card is: once started it can’t be interrupted. ---
**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:** [November 3, 2025, 7:19am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/3 "2025-11-03T07:19:06Z")
I have the same feeling as Wim, I hardly use “wait” and never use long “wait” because of this. Long wait wait is hardly impossoble to troubleshoot if it goes wrong. With a long timer, you are in control (you can stop it). ---
**Author:** ![GrayV8](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grayv8/32/178444_2.png) [@GrayV8](https://community.homey.app/u/GrayV8)\ **Post date:** [November 3, 2025, 7:23am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/4 "2025-11-03T07:23:07Z")
Maybe so but many situations call for a delay before retrying something, perhaps repeatedly or a set number of times - which is what my situation calls for. I don’t care that it can’t be interrupted as this is something that is happening from 2am in the morning onwards, fyi. ---
**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:** [November 3, 2025, 2:31pm UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/5 "2025-11-03T14:31:54Z")
> [@Wim\_Post](#): > > The downside of a (long) wait card is: once started it can’t be interrupted. Not 100% true, in case of malfunctions, Wim. @GrayV8 A crash/powerdown/restart doesn’t only interupt the countdown, it even resets it. Flows you’d expect to continue, don’t continue. For me a reason to never use those delays longer than a few seconds. It even shouldn’t provide for minutes as unit. Another downside of wait cards: when still counting down and triggered again, it can be started in parallels without any visual indicator. It’s a black box. I’d rather use Chronograph timers, because they can either get restarted or resumed after new triggers while counting up (Chronograph counts _towards_ a timestamp, which makes it survive restarts ánd still apply the duration correctly). And, as you know alr, it takes numeric variables or even tags as value. ---
**Author:** ![GrayV8](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grayv8/32/178444_2.png) [@GrayV8](https://community.homey.app/u/GrayV8)\ **Post date:** [November 4, 2025, 6:47am UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/6 "2025-11-04T06:47:37Z")
Thanks @Peter_Kawa and others for the helpful feedback; I certainly understand that using Chronograph or similar is a much better ‘bullet proof’ way to ensure flows or logic processes correctly in the event of outages or whatever. However, the reality of a lot of basic users like myself is that we simply don’t need to over-engineer flows and logic to manage once in a blue moon situations. I’ve literally had one power outage in the last year at my house. Probably my HPro has rebooted or gone off line a few other times as well, but it’s really not a big deal. Also, the flow / logic in question is not related to security or door access etc to my house; it’s just turning on some sprinklers at night, and doing that or not based on wind speed. If it fails outright, I really don’t care. It’s not controlling Grandma’s night light so she doesn’t fall down and break her hip, or whatever other more risky logic situations some people might have with their home automation 😉 I really still can’t understand why it wouldn’t be something offered by default. I would be interested to hear from anyone else who might like to see it (back me up, please!), otherwise I’ll resign myself to having to use multiple flows and a separate app like chronograph. ---
**Author:** ![Tjoloho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjoloho/32/16419_2.png) [@Tjoloho](https://community.homey.app/u/Tjoloho)\ **Post date:** [June 3, 2026, 5:59pm UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/7 "2026-06-03T17:59:02Z")
I had similar challenge last week, I want to steer the wait dynamic and the chronograph don’t work because I could ha several flow running simultaneously with some wait.. So I ended up with a possibly ugly solution but it definitely solved my case smooth.. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a2331c34832ca099cc6bb66e50920cd6ff6832df.jpeg) I basically loop through with the input value to the flow and use the regular wait feature.. and then I call this flow from other flows and send the amount of seconds I want to wait: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/0/a0d354922975a905607bbd0de2d9b96e6503422a.png) ---
**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\ **Post date:** [June 3, 2026, 6:45pm UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/8 "2026-06-03T18:45:07Z")
![IMG_2173](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/b/bb777fe10f26f82cd1aa98210019800a5b3ed0f5.jpeg) Inspired by @Tjoloho I created this little subroutine. ---
**Author:** ![Tjoloho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjoloho/32/16419_2.png) [@Tjoloho](https://community.homey.app/u/Tjoloho)\ **Post date:** [June 3, 2026, 8:53pm UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/9 "2026-06-03T20:53:18Z")
I guess this is almost perfect, but what if 2 flows call this flow at the same time? There is a possibility, small one but still, that the “Stap” variable will be overwritten by the other flow, right? It’s probably milliseconds​😇 ---
**Author:** ![Wim\_Post](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wim_post/32/56793_2.png) [@Wim\_Post](https://community.homey.app/u/Wim_Post)\ **Post date:** [June 4, 2026, 12:13pm UTC](https://community.homey.app/t/featurerequest-advanced-flow-delay-by-numeric-variable/144873/10 "2026-06-04T12:13:08Z")
![IMG_2174](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/1/11b764725b2fb999e453ab8d29dac4f2b9aaec4f.jpeg) This flow (test timer) is counting down out loud from 15 to 1 before blowing the trainwhistle. After 10 seconds the 20 seconds branche is started. My Homey is saying : 5, 19, 4, 18, 3, 17, 2 and so on. So the 2 timers don’t interfere. (Strange is that trainwhistle only sounded after 10 s)