# \[APP\]\[Pro\] Chronograph - Adds precise timer, stopwatch and transition functionality to Homey **URL:** \ **Category:** Apps\ **Tags:** app, official, tools, homey-pro\ **Created:** [September 17, 2019, 5:55am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214 "2019-09-17T05:55:42Z")\ **Posts on this page:** 20\ **Page:** 33
**Author:** ![Matthaus\_Artmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthaus_artmann/32/80156_2.png) [@Matthaus\_Artmann](https://community.homey.app/u/Matthaus_Artmann)\ **Post date:** [August 15, 2024, 12:05pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/663 "2024-08-15T12:05:55Z")
Hi there! I started to use Chronograph app a while ago only using Timers. Very handy, but recently I ran into a problem. In short, _is it possible that a running stopwatch affects the execution of a in parallel running timer?_ **Explanation** : I have some flows which are triggered upon the end of a timer. But recently the execution of those flows stopped working, I.e. the end of a timer does not trigger the flow. I did a lot of trial and errors but ended up realizing that a running stopwatch refuses to let the trigger be executed. The stopwatch is used for something different I tried. Once I stop the stopwatch, the affected flow triggered by „timer has ended“ flow card immediately starts to run. It‘s like the flow card is waiting for the stopwatch to end. Anyone else had that problem? Thanks in advance! ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [August 15, 2024, 2:29pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/664 "2024-08-15T14:29:30Z")
@Matthaus_Artmann Well, obviously this should not be the case. But on the other hand, the execution, handling and firing of effects/cards of chronographs (timers, transitions, stopwatches) are linked together. In the sense that, every second (and upon completion of a chronograph it increases, but ill refrain from going into the technical details), the chronographs are ittirated and checked if (flowcard) executions are needed. Afaik, “crashing” handlers should not effect any other executions, there are quite some error handlers in place for that. But on the other hand, based on your post, thats all i can think about. Unfortunately (and yeah, for me right now very fortunately) i am baking in the sun of Lanzarote, without a laptop, pc, or Homey, so, (sorry for you 😉), i cannot do anything about it atm or check it. Can you create a supportticket? Than i can pick it up in about 2 weeks, when i am either very brown (or red) 🤣. ---
**Author:** ![Matthaus\_Artmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthaus_artmann/32/80156_2.png) [@Matthaus\_Artmann](https://community.homey.app/u/Matthaus_Artmann)\ **Post date:** [August 16, 2024, 5:53pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/665 "2024-08-16T17:53:57Z")
Hello @Arie_J_Godschalk Thanks for the quick reply and first insights. I think I get what you’re saying. For now, I found an alternative way for my use case without using stopwatches and timer at the same time. I will have a look at how to make a ticket. Enjoy your summer vacation and don’t forget about the sun protection! 🕶 ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [September 14, 2024, 6:07am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/666 "2024-09-14T06:07:59Z")
Hi @Arie_J_Godschalk ! I have a transition configured to run for 18 days, from 0 to 18 in 19 steps. So expecting it to trigger the “Transition has reached a step” every day. It worked the first (start day, first step) and second day, but after that no more triggering. Day three I upgraded the Homey, could this have caused any problem? I do not think that because before I had the same flow but with another name on the Transition. It also stopped to trigger “Reach step” card so I changed the name just for test. ![Kombucha-transition-issue](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/2/12f042c745d63b555c2b5a5d4f4cc43533b4813b.png) ![Kombucha-transition-issue-chronograph](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bc25d0cd460d551ea49e1e1b52ea00eeb60fcc87.png) I have added a card that sends a message to me at every “Reach a step” for test purpose. I am not having any issues with that part as I use it for many other notifications daily. ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [September 15, 2024, 8:20am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/667 "2024-09-15T08:20:22Z")
One more thing. Every hour I retrieve the duration/elapsed time, maybe this has any affect? In my flow above “Kombucha-start-new” = 18. ---
**Author:** ![Mike1233](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike1233/32/20991_2.png) [@Mike1233](https://community.homey.app/u/Mike1233)\ **Post date:** [September 15, 2024, 12:46pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/668 "2024-09-15T12:46:21Z")
@Anders_Gregow Did you reset the Homey after the opdate? Sometimes that will help. Or did you try to reset the app? ---
**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\ **Post date:** [September 15, 2024, 1:00pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/669 "2024-09-15T13:00:38Z")
Why does a card gives an error instead of a false when a countdown is not running anymore? ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/3/a3e73f86d8e66170146320749af394d9f7838940.png) ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [September 15, 2024, 5:21pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/670 "2024-09-15T17:21:09Z")
None of them. I had this problem before the Homey upgrade, using another name for the transition. During that test there was no upgrade of neither Homey nor the Chronograph app. I have started a test with two different transitions with the same settings (but the name). At every step I am sending a push notification using Homeys built in push. Every hour a call is made to get the duration of one of the transitions, but not the other. Maybe this will give a clue. I have had transitions running without problems before, but never called the get-duration card. ---
**Author:** ![MasterFu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/masterfu/32/81238_2.png) [@MasterFu](https://community.homey.app/u/MasterFu)\ **Post date:** [September 16, 2024, 7:11pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/671 "2024-09-16T19:11:42Z")
Hi Arie, thanks for this great app. I have been using it for quite some time. Since today, I get an error “invalid time” when starting / replacing some of my stop watches in specific flows. If I change the name of the stop watch it might work for a short time, but then the error comes back. Restarting the app, restarting homey did not solve the problem. ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/9/b9ac37416cf5d2763b3edde7a80e39bb5a99ac35.png) Any ideas? ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 26, 2024, 5:26am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/672 "2024-09-26T05:26:08Z")
Im not sure why this was build this way. But it does make that you can know the difference in flows if its not running. ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 26, 2024, 5:27am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/673 "2024-09-26T05:27:36Z")
> [@MasterFu](#): > > Any ideas Nope. But why does that flowcard not show a timefield to enter time? ---
**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:** [September 26, 2024, 2:20pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/674 "2024-09-26T14:20:10Z")
Stopwatch != Timer, Arie 😉 > ![1000034671](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/6/96acd04ac86b1dbe3f0868f5629a06cb33a3f5f9.jpeg) ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [September 30, 2024, 5:23am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/675 "2024-09-30T05:23:33Z")
> [@Peter\_Kawa](#): > > Stopwatch != Timer, Arie Hahha oeps ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [October 9, 2024, 8:46pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/676 "2024-10-09T20:46:46Z")
Is there a way to find out why a Transition stops trigger the “Transition reached a step” card? I have added a pushnotis card to the trigger card for test and it never fire anymore. The first 10 days or so it did (it runs for 18 days, 19 steps from 0 to 18) but then suddenly stopped to trigger. I see that the Transition is still running towards 18 days in the settings page for Chronograph. @Arie_J_Godschalk ---
**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\ **Post date:** [October 11, 2024, 6:13am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/677 "2024-10-11T06:13:26Z")
> [@Anders\_Gregow](#): > > Is there a way to find out why a Transition stops trigger the “Transition reached a step” card? Send me a diagnostic? ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [October 11, 2024, 7:06am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/678 "2024-10-11T07:06:52Z")
I was just thinking when to capture the diagnostics. 🙂 I will do it right after the failing reached-a-step next time the missing-trigger occurs (just restarted the transition-timer). How long is the execution history in the diagnostics? If it is days back I probably have captured the problem. ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [October 11, 2024, 10:21am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/679 "2024-10-11T10:21:45Z")
44140e09-b043-4ab3-baf6-d199e846054e The reached-a-step should have triggered around 9 o’clock. ---
**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\ **Post date:** [October 13, 2024, 6:59am UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/680 "2024-10-13T06:59:02Z")
Sent you some more diagnostic reports. 43 min before trigg ec8ce561-2738-44b6-84d9-27bb2188cb5a About a min before 1d4fa233-0a47-4688-a94d-2c1235a4b8ee Directly after the trigger of reach-a-step should have occurred but didn’t 26032d29-770e-46bb-8c03-380ee29cf921 Hope they will give you a clue. ---
**Author:** ![Joep\_van\_Andel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep_van_andel/32/71049_2.png) [@Joep\_van\_Andel](https://community.homey.app/u/Joep_van_Andel)\ **Post date:** [October 16, 2024, 2:51pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/681 "2024-10-16T14:51:41Z")
Is it possible to determine in which flow(s) a certain timer- or stopwatch-name is used ? ---
**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:** [October 16, 2024, 5:25pm UTC](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214/682 "2024-10-16T17:25:01Z")
Hi Joep I"ve this script to extract the used Chronograph device names from (standard) flows, but I can’t get the flownames into the output 😬. Maybe someone can help out. ```auto const flowsDic = await Homey.flow.getFlows(); const flows = Object.values(flowsDic) const actions = flows.map(f => f.actions.filter(a => a.uri === 'homey:app:nl.fellownet.chronograph')).flat() log(actions.reduce((a,x,y,z) => ({...a, [x.args.name]:x.id.split('_')[0] }), {})) //log(actions); //log(flows); ``` [Previous page](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214.md?page=32) [Next page](https://community.homey.app/t/app-pro-chronograph-adds-precise-timer-stopwatch-and-transition-functionality-to-homey/18214.md?page=34)