Just when I thought all was okay I got the same issue again. I can’t figure out what exactly is causing the app to crash and when. My flow ran several times but when I changed the flow trigger condition from [When Flow is started] to trigger on [When a contact alarm is active] it crashed immediately when the trigger became active. Changing it back does not help.
Chronograph “stopped unexpected” a few times a day, since I use it after Homey’s factory reset with my restored backup…
It worked fine for about 18 months.
However, the flows luckily don’t get broken (because there’re no devices), and the running timers just keep on running!
I’m going to re-install Chronograph
Uninstall and then install will cripple my flows I think?
Thanks Joka, that caught my eye too. But I love this app.
I will do some ‘experiments’. I have indeed a backup
A re-install without uninstalling first, keeps the flows unaltered.
I don’t want to fiddle with restoring backups yet… so I don’t uninstall it for now.
I will keep an eye on things, f.i. what happens as the app has crashed. The timers seem to keep running anyway…
Probably only new flow cards cannot be added.
~Peter
As many users probably have noticed, I haven’t had the time to maintain this app properly. If there’s a developer who wants to take over, please DM me and if I have a good feeling about it, we can discuss transferring the app.
I tried setting this up today, and have some questions. Hopefully, I’m not completely lost…
Case: I have one recursive flow where I was hoping to use this app. I set a timer for x seconds unless a criteria is met. I also have a flow triggering when this timer (manually set name) stops. This last flow calls the first flow, which checks the criteria - and if it’s not met it will start the timer again.
I assume you mean “when the timer is finished”. B/c a timer can be paused(stopped) also.
Flow 1
When…
-this flow is started
And…
-condition 1
Or
-condition 2
Or…
-condition 3
Then…
-do someting
Else…
-start timer Timer1 with a duration of x s.
Flow 1
When…
-this flow is started
And…
-condition 1
Or
-condition 2
Or…
-condition 3
Then…
-do someting
Else…
-start flow “Flow 1” with a delay of x s.
Wow! I actually didn’t even see the “is finished” option, so I had the “stopped” card. Which I figured had to be wrong because things worked when I stopped the timer manually.
@Peter_Kawa Quite a while later after your message: I can confirm that uninstalling and then installing Chronograph will restore existing flows intact.
The reason for the need to uninstall is that app restarts could not keep Chronograph from crashing. No idea why, but we are quite a few releases further and I am in the process of setting up new advanced flows with Chronograph.
I love the app, it’s one of the apps I used most and is very easy to use.
One problem, since the introduction of Advanced flows, one of the trigger cards doens’t work as expected anymore. It’s the card with id ‘timer_split’ (not sure about the English title, I guess. ‘timer has reached a time of…’). I rebuilt some of my standard flows to advanced flows, I checked the logic and it has not changed, but these trigger cards almost never get triggered…
@DieJan Do you also having trouble with the card “timer x heeft een looptijd van x”?
This one is also not always staring in my flow.
Stopwatch is working with no problem.
I thought I did something wrong.
30 seems to decrease the timer by 30mins instead of adding time.
-30 does not work. When the timer is running it does not do anything.
the virtual device test in this instance has the doorbel function. So it acts as a pulse.