Correct, it doesn’t. You need flows.
But it is a very good app, do try it.
1 Like
Yes it does, you can create devices that bind to a chronograph.
You can??? How?
Add device
select Chronograph
pick timer, stopwatch or transition
pick name
I think I might have misunderstood you.
I think @Sharkys was thinking about a timer controlling a device (e.g lamp) without needing any flow, correct?
Not creating a timer and use it to trigger flows?!
1 Like
Ah, that’s a good idea, but it would need the homey-api, making the app use way more resources.
So perhaps i can combine this with the Device Capabilities app (which already uses the homey-api).
Please create a feature ticket?
1 Like
With a pleasure 
Done. Thank you !
(but created it in Chronograph - not sure how much the difference in resources would be, it would be nice to have both replaced - Timer and Countdown, maybe there is a way ?).
Hi, im sorry for the apparently simple question, but im just getting started with homey and flows / advanced flows, and cant seem to get this working.
Im trying to setup my outdoor lights so that ->when motion is detected - and is 5 min before sundown → they can be turned on → for the next 10 hours ->and not after that
I have it setup with time - from 20:00 to 07:00 but that will only work in the summer, and dont know exectly how to do it with sundown and chronograph.
Best regards and thank you in advance for any answer.
Can you think of any changes which occurred around the time that card started to error, like firmware, app update?
In standard flows a stopwatch starts and runs fine here.
@ your Homey, does it start from a standard flow?
Edit: sorry, I didn’t realize this topic is in English.
I’m experimenting a bit with this app. In this example, I want to know how many seconds it takes for the motion sensor to indicate that no motion has been detected. I have this working when I remove the “Stop stopwatch Overflow test” block. However, in that case, I get a value of 0.02 seconds. Not exactly what I intended…
The error occurs in the “Get elapsed duration of stopwatch Overflow test” block.
Dutch
Ik ben een beetje aan het uitproberen met deze app. In dit voorbeeld wil ik weten hoeveel seconden het duurt voordat de bewegingsmelder aangeeft dat er geen beweging is gedetecteerd. Dit krijg ik werkend wanneer ik het blok “ Stop stopwatch Overloop test” eruit haal. Echter dan krijg ik een waarde van 0.02 seconden. Niet helemaal de bedoeling…
De foutmelding ontstaat in het blok “ Krijg de verlopen duur van de stopwatch Overloop test”
Wat gaat er hier fout?
The [Bewegingsalarm] tag you entered is useless. When you create timers/stopwatches, just ignore that field after the /
2 Likes
@Arie_J_Godschalk
What’s the matter with my favorite stopwatch? I can’t get a single stopwatch started, for a while. Even a simple test gives exactly the same error message. Bug? Please help!
Wat is er met mijn favoriete stopwatch aan de hand? Al een tijdje krijg ik geen enkele stopwatch meer gestart. Zelfs een simpele test geeft exact dezelfde foutmelding. Bugje? Of tijd voor een nieuwe Homey?
Hi, which HOMEY, firmware & app version are you using?
Works fine here with Pro2019 v8.1.6 - Chronograph v2.1.2
Can you send a diagnostic and after that, restart the app?
1 Like
ee1f5b3a-fa78-4938-ad80-0741c608058f
1 Like
Ill have a look tomorrow.
Hey @DvStarrenburg,
I have put a version in the TEST to debug this issue.
Would you install the test version, and if the Start Stopwatch-card fails again, please send me a diagnostic again, it contains some more information to debug this.
