There’s actually a new version under review by Athom that has a settings page with an overview of all timers and stopwatches currently running.
That version also includes tokens (tags/labels) with the duration of a timer or stopwatch, but those are only available after a trigger. I have yet to find a good way to include global tokens (those that exist all the time, in every card). It’s not trivial because it would most likely require me to update these tokens every xx milliseconds for it to be even slightly accurate, which would give too big of a load/stress on a Homey.
Nice, tested and one more comment. If I do a app restart, or Homey restart, timer information is lost. This is quite a problem for long term running timers (e.g. watering delay in case of rain).
Hi, I really want to use this app instead of countdown since this is much more promising. I was just wondering, is it possible to add a timer with a variable end time? (like somewhere between 600s and 1800s?)
That’s exactly one of the new functionalities I’m currently working on. To give you an idea, I’ve pushed this development branch to github, so you can take a look at the readme to see if it suits your needs. The new functionality is currently being tested by a select few alpha testers, and it will be offered as a beta to the Athom review team hopefully somewhere next week.
You are the man! This looks amazing!! The random setting is used to make it look like I’m present when I’m away or asleep at night, so that needs to be completely random between a min and max nr of seconds so I’ll only need that expression for that.
But, I also see great potential in all the other math expressions you will be adding, and even have som current flows that will be simplified by this, very nice!
I’m in stable release, because I read that switching from beta to stable would reset the entire application so I’ll have to wait a little longer! When do you think this wil hit stable release?
Version 1.0.5 (beta) is offered for review and fixes a major import bug that causes crashes for version1.0.4 (beta). Guess that’s why they’re called beta’s
Hello.
App 1.03 crashes when I use “start or replace timer X” while the timer X is already running.
I think it was working correctly (replacing running timer with newly provided value) in previous versions.
When I alternatively try “adjust timer X” also nothing happens to the value of running timer, but at least app does not crash.
It’s quite ambitious to have millisecond update of global tokens. I would appreciate the actual timer value as a global token even with seconds precision.
Good work, by the way!
There’s a technical challenge here. Having tokens available whenever something unrelated triggered a flow is unfeasible. That would require the app to update tokens every few milliseconds to be somewhat precise. I could implement a work-around though. What if you could pause the timer once your event triggers, and then have a separate flow react on the pausing of the timer. At that point you’d have the exact duration of the timer in a token that you can use however you want. You can also resume the timer in the same flow. Would that help your cause?
What i want realize, is a kind of “Operating hours counter”.
I want to determined how long a specific device was turned on during the day. This is already possible with the Chronograph App but I can not store the result in a variable.
The Stopwatch should run everytime if the device is turned on and will be paused when it was turned off. End of the day i want to save the value of the Stopwatch in a varaiable. In this way it would be possible to visualize the “Operating hours counter” through insights.
