Countdown and virtual devices

The Countdown app and virtual devices are must have apps. They both work perfectly, and I use them in many flows. However I would also like a counter, which can trigger at different levels, an be shown with its value in the mobile app.
I do not see any other app doing that…

I use that for on/off States. With a normal counter which can be started, stopped and trigger I could not find. And showing values of counters in the app is the other which would give great opportunities.

Take a look at BetterLogic App: (https://apps.athom.com/app/net.i-dev.betterlogic).

In the Background/Backend of Homey in the App create a Number-Variable, on Frontend (Devices) a Slider-Device with the created Number-Variable.

So you can Count/Discount in the Background and see the last Value of your “Counter” in Front of the created Device.

With the Sliding-Device you also can change the Variable if you e.g. on the Road.

Using this for e.g. Blinds and works perfekt.

It looks like I want multiple things:

  1. Visible counters on the frontend to easily see values of the counters
  2. Instead of a countdown counter a simple counter which continues until I stop it.
  3. Trigger a counter at different levels (this should be easy if tags can be used)

For the first two I have not seen an option.

Hello Andre,

it’s not a perfect solution but you can try the following:

  1. Visualisation of a counter
    There are three variables you can set for a virtual device, e.g. measure_temperature. If you create a virtual thermostat or a virtual kettle you can create a flow, telling the device to write your counter to e.g. the temperature value of your virtual device. (If variable X changes/is set then “set a virtual sensor value” to X)

  2. Counter instead of countdown
    There is a time function in within Homey. You could us “Every…” second/minute/etc) to increment your counter variable by 1/2/etc.
    Keep an eye on your average load, could be possible that your Homey get some problems if there are to many processes each an every second.

  3. Trigger by counter
    As you already mentioned, now this should be easy. Either by a variable value or a change of your virtual device.

Other solution:
Use the countdown app. If a device does something start a countdown and create different flows to do different things.
E.g.:

  1. If something happens then start a 180 seconds countdown
  2. If countdown “timer value has changed” and countdown “is exact” X do something (there is no need to wait until 0)

You can also use the virtual device trick for this to visualise it: If timer value has changed and is exact X than “set a virtual sensor value”

Regards
Andreas

Is it a solution for point 2 if you use the following flow?

If counter changed AND Value = 1 THEN restart Counter

This way you create a loop and you can stop the counter in any flow you want

I would need another parameter then to keep track of the amount of times the counter is restarted.
Looking at the functionality the flow editor gives this should in my opinion be by default available.

With #1 (visualisation of a counter) I would neeed a configurable number then to make a value visible.
For #2 I am alss wurried that it takes to many flows and processes. This is one of the reasons I would like to make them vissible…

Late reply for those who read the above: have a look at Chronograph which allows to create a device with a timer/stopwatch/transition.