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?
@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) .
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!
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.
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.
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.
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.
Any ideas?
), i cannot do anything about it atm or check it.
.
