Just FYI: as far as i know, this is not correct: @ralfvd plans to update to SDK3, but he has a lott of apps that need to be updated and he just needs time, like most dev’s.
@Peter_Kawa do you know (out of head) how this can be accomplished?
because i don’t see anything wrong (i assume @Twan_Veugelers that you only use one of the Then cards and not both at the same time?
The upper right cards should be just enough.
And i don’t see any reasons that it should stop, execpt: if you execute the Start time AND the Update time card, it might be that generates an error, depending on which fires first.
When I ‘test from here’ on one of the When cards, and I have the Chronograph App config open (I see the timer nicely running), as soon as the flow hits the highlighted step, the whole timer is removed.
It is not exactly similar, but I think the issue is Twan wants to extend a timer which is not running. Timers don’t disappear from the app settings page though, only if you start an other timer with an equal name (it gets overwritten), or when it is not running.
So it is normal behaviour the timer disappears from the running timers overview.
Here in the thread is a script which shows all your ever started timers, stopwatches and transitions:
Altho i ofc didn’t have the telegram app installed, but after removing it, the flow runs.
@Emile Advanced Flows can surely be copied between devices, since i can copy them between users even
This works excellent for support, i don’t need to rebuild the flow (and possible fix the issue by creating it differently). You should have the support employee’s ask for TEF’s Easy way to find bugs that image do not show you, see below!
But back to the by you @Twan_Veugelers reported issue, you are right, i also get the same issue. But that is because, you also have something else in the flow that you didn’t show in the picture:
You are stopping it yourself, because of a bug that the trigger is triggered when you adjust the time
The solution i’ll place in a different post, one sec.
BTW, Adjusting it by 4 hours means ADDING it to the current time. I think you actually simple want the Start Card, this one sets it to 4 hours exactly when you use it and the timer was already running.
Okay, i think this is a bug, but i would need to knwo from users:
Right now, when you adjust a timer/countdown/transition, it actually doesn’t work as i think it should: it sets the adjusted time plus the current duration: which makes it “finished”?
I find it weird.
But, I think you want to “reset” the active time to 4 hours again?
I don’t see currently how that can be done with a signle card, or you need to stop the timer first (straings):
Arie, about the ‘extend timer duration cards’,
The card description is using a reversed explanation.
(With timer cards I also mean the stopwatch and transition cards.)
It should read imho: Use this card to adjust the duration of the timer with the provided name.
Positive value: shortens the duration;
Negative value: extends the duration.
Exmpl: adjust a running 5 minutes timer which has 60s left
with 50: remaining duration = 60 - 50=10s
with -50: remaining duration =60 - -50=110s
Wasn’t finished yet
Yes I meant to edit the card’s hint!
I expect the same goes for stopwatches and transitions, but I’d better test it 1st
Also, useful info:
One can’t extend the duration, when the new duration will be longer than the timer’s original duration
One can’t shorten the duration, when the new duration will be lower than zero.
Seems logical but it isn’t always clear what the limitations are.
These limits are also nice to have: imagine you extend a 15 sec oven or heater timer by accident with one day instead of 1 sec
For stopwatches, it’s already correct (it extends the duration).
It seems this function was build for stopwatches and sub-supported for transitions and timers.
Hey Twan, I felt free to edit your flow so it works like you describe.
Note the use of “start and replace timer Netatmo”. This resets the timer to its programmed duration value (4 hours) again, when it was still running while a temperature trigger occured.
When the time’s up, and the Netatmo app has been restarted, the timer is started again.
Also, use exact the same timer name in your timer cards. Not “Netatmo” and “Netatmo Active”.
Maybe some day @Arie_J_Godschalk can create a dropdown with existing timer names to choose from.
But there’s a catch: a new timer must run at least one time to get ‘known’. So this idea might be impossible
No, that is not really needed, take a look at Advanced Triggers where it is also just read from the given/selected arguments.
If you have a flow and you save it, the apps gets a noticifation with the arguments you picked.
And in the dropdownlist that some arguments have; i can return your query/what-you-typed.
This is how Advanced Triggers works, i hope to add it to CountDown (if i may), and now it may look that BetterLogic is gonne get it too…
There is just one other catch about this: i cannot just change a text-field-argument to a dropdownlist-argument. It will break current flows.
What i could do tho, is the exact same thing as Advanced Triggers: Show a optional dropdownlist AND a optional textfield. This would keep existing flows intact and also gives the options of a dropdown.
Trying to start a stopwatch, then stop it and create a message “Jeroen came home after 1 hour and 20 minutes” but i see that there is no card available that has the stopwatch time is that correct?