[APP][Pro] Chronograph - Adds precise timer, stopwatch and transition functionality to Homey

[Joep_van_Andel]

@Peter_Kawa

const flowsDic = await Homey.flow.getFlows();
const flows = Object.values(flowsDic)
const actions = flows.map(f => f.actions.filter(a => a.uri === 'homey:app:nl.fellownet.chronograph')).flat()
log(actions.reduce((a,x,y,z) => ({...a, [x.args.name]:x.id.split('_')[0] }), {}))

//log(actions);
//log(flows);

Thank You Peter,

Can You explain how I can use this script?

Kind regards Joep

[Anders_Gregow]

Hi @Arie_J_Godschalk !
When will you have time to investigate this?

Best regards Anders

[Joep_van_Andel]

@Arie_J_Godschalk , if it would possible then it would be great.

I’m currently revising and reorganizing all my flows. As part of this, I want to rename all my timers and stopwatches to a standard format. To avoid causing issues and disrupting my existing flows, I need to tackle them one by one. Given the large number of timers, stopwatches, and flows I have, I want to avoid opening each flow individually and risking missing a single instance.

A list of existing timers and stopwatches, along with the flows in which they are used, would be a great help.

[Anders_Gregow]

If you download the flows from the developer page I have a script that might help you.
It shows all flows containing a supplied text.

On this page: http://developer.athom.com/
Run the following commands one by one (all is not needed):
Homey.flow.getAdvancedFlows();
Homey.flow.getFlows();
Homey.devices.getDevices();
Homey.zones.getZones();
Homey.logic.getVariables();
Homey.flow.getFlowFolders();
Homey.alarms.getAlarms();
Homey.apps.getApps();

Tell me where to send you the script (Python3).

[Eko_taas]

Started to use this great App, but after some testing got strange issue (seems to be outside of this App, but asking here anyhow )…

Simple flow (don’t ask why )

Then (as I had very strange flow-starting issue) made also this for :

When got alarm, and finally at laptop/web, checked with:

=> 75+min had passed…

As seems to me that “every 5 sec” Flow-card stopped firing, but was not able to find any App as “crashed”. Restart resolved issue, butwould be better (if possible) to restart effected App only

Q (Finally ): anyone know which App to restart / fix possible w/o HP2023 restart?

[Peter_Kawa]

@Eko_taas

As seems to me that “every 5 sec” Flow-card stopped firing, but was not able to find any App as “crashed”

1. It’s an onboard card, so there’s no app
2. Add a Simple Log log card and you’ll know
3. Flows can be silently disabled by Homey, because of an unknown condition ‘too many triggers in x seconds’
   AFAIK only by looking at the flow status, you can find out:
   
   

[Ron_Gibb]

I am getting an error when I try and start/replace a stopwatch. The last time I had this issue I just changed the name of the stopwatch and that fixed the problem. Here is a screen shot.

What is the best solutions to prevent this from happening and how do I fix this issue in this flow?

[Theo_de_Koning]

Some extra information is handy.

Part of the flow.
Is “Heat on stopwatch” coming out of the list.

[Arie_J_Godschalk]

@Ron_Gibb

What is the best solutions to prevent this from happening and how do I fix this issue in this flow?

What is the value of the stopwatch in the app settings?

[Ron_Gibb]

I just tried it again and before throwing the error the app reports no active stopwatches. After the error the stopwatch show 00.00

[Peter_Kawa]

When it’s a new stopwatch, you’ll have to enter the name in the field “Pick” instead, and select the entered name afterwards. After you saved the flow, the stopwatch has been created and should be functional.

[Ron_Gibb]

I just tried that several times and there is no difference. It still throws an error.

[Ron_Gibb]

This is what I see in the app.

If I click resume the stopwatch starts right up.

[Peter_Kawa]

Odd… it works fine in Test mode here.
I think it might be a browser cache issue…
Clear cache, and force refresh the web page. And / or try running the web app in a private tab, to start ‘clean’.

Does it run in normal mode (non-test mode)?
Like this:

[Ron_Gibb]

I created a new private window in Firefox. This stopwatch starts when a relay turns on so I turned on the relay and it generates the same error, no change. I tried it again starting it from the flow and it also fails.

I restarted my Homey Pro and it still generates the same error.

[Peter_Kawa]

You can install the app again, without removing it prior to that.
I can’t think of anything else atm.

[Ron_Gibb]

Thank you for your assistance. Reinstalling didn’t change anything. sorry Your app is fabulous, except for this crazy issue. So much better than anything else I could find for Homey Pro and especially much better than anything on Hubitat!

[Peter_Kawa]

YW! @Arie_J_Godschalk is the app wizard maybe there’s a pointer in the app logs.

[Anders_Gregow]

@Peter_Kawa

When it’s a new stopwatch, you’ll have to enter the name in the field “Pick” instead, and select the entered name afterwards. After you saved the flow, the stopwatch has been created and should be functional.

No, you do not need to do that.
You could either use the pick filed and then you need to save before use it, or just use the name field. Using the name field has the “disadvantage” that you need to remember the exact name of the timer/stopwatch/transition, as the pick field will do that for you.

This looks a bit like my issue with transistion.
But my transition is running (seen in app settings) but the transistion step card never fires.
I think it might have something to do with that another flow is using the get-duration-for-transition card. Maybe a conflict?

[Joep_van_Andel]

@Arie_J_Godschalk , Is there an easy way to rename a Timer all at once, or do I have to open each advanced flow individually and manually change the name? (with the unfortunate consequence that a flow might be forgotten.