[APP][Pro] Timey - Make your time flows dynamic with variables

Apps
, ,
1

Timey

Use text variables in time flow cards with a 24-hour format: ‘H:mm’, ‘H.decimal’ or ‘H’

00:00 is the earliest, 23:59 is the latest.

Current version

Why a own app for time flow cards?

I wanted to set the time in one place and have it reflect in all my flows. The built in time flow cards does not support to set the time through variables, and the alarms did not have all the flow cards I needed. So I made a app which behaves like the built in time flow cards, just with the option to set the time with text variables. Maybe you’ll find it useful too?

Tip: Add the time to the variable name to make it more readable in the flows.
variable-name
flow-with-variable

You can of course also use a normal text input directly as a timestamp.
flow-with-text

Formats

Three formats are accepted.

1. Exact time (HH:mm)

  • 00:00

  • 01:05

  • 12:30

  • 23:59

Notes: Minutes must be two digits (strict). Hours may be 1 or 2 digits (0–23).

This format also accepts wildcards

2. Decimal hours (H.decimal)

  • 7.5 → 07:30

  • 12.25 → 12:15

3. Single hours (H)

  • 2 → 02:00

  • 14 → 14:00

Invalid formats

Single-digit minutes

  • 23:3

  • 0:5

  • 12:7

Notes: Minutes must be two digits unless a wildcard is used.

Invalid hour or minute numbers

  • 24:00 → hour too high

  • 12:60 → minute too high

  • -1:00 → negative hour

  • 12:-5 → negative minute

Invalid wildcard usage

  • *:*1* → :cross_mark: mixed wildcard in one field

  • **:* → :cross_mark: double * in a field

  • 20:4** → :cross_mark: double * in minutes

Wildcards

Wildcards can only be used in the Exact time HH:mm format

Full wildcard (:)

  • *:* → every hour and every minute

Notes: Colon is mandatory; both hour and minute are required.

Hour wildcard (*) only

  • *:00 → every hour at minute 00

  • *:30 → every hour at minute 30

  • *:45 → every hour at minute 45

Minute wildcard (*) only

  • 12:* → hour 12, every minute

  • 1*:* → hours 10–19, every minute

  • 2*:* → hours 20–23, every minute

Prefix wildcard (n*)

  • 1*:00 → hours 10–19, minute 00

  • 2*:30 → hours 20–23, minute 30

  • 20:4* → hour 20, minutes 40–49

Suffix wildcard (*n)

  • *1:30 → hour ends with 1 (1, 11, 21), minute 30

  • 2*:*0 → hours 20–23, minutes ending with 0 → 20:00, 20:10 … 23:50

  • *:*5 → every hour, minutes ending in 5 → 00:05, 01:05 … 23:55

Notes: Both hour and minute can have prefix or suffix wildcards, but a single field cannot have both (e.g., *1* is invalid).

Expressions

You can use expressions to set the timestamp. You have two options, BLL or Homeys built in logic, but the result of the expressions needs to match the valid timestamps as mentioned above.

Better Logic Library

You need to first have the Better Logic Library (BLL) installed: Homey App Store

Then wrap your expressions with brackets like this: {[ expression ]} and the result must match one of the valid formats mentioned above

Read more about BLL here: Community Topic

Homeys built in logic

Use Homeys built in expression brackets: {{ expression }}

Changelog

1.5.0

  • Added wildcard support

1.4.1

Bugfix

  • Fixed issue where decimal to timestamp would sometimes be incorrect

1.4.0

Feature

  • Added time1 is earlier/later than time2 flow cards.

Bugfix

  • Fixed wording in existing earlier/later flow cards

1.3.0

Feature

  • Added support for BetterLogicLibrary

1.2.0

Feature

  • Added support ‘H’ format

1.1.1

  • Bugfixes

1.1.0

Feature

  • Added support for ‘H.decimal’ format

1.0.1

  • Updated app description

1.0.0

  • Initial version

Issues and bugs :bug:

Bugs should be reported here

Donations :moneybag:

If you like this app, please consider donating through paypal

6 Likes
Alarm <alarm> goes of in <minutes> minutes with tags
Homey push notifications
[LIST] NEW published App in Homey App store :rocket: - Get 'em while they're hot
Gradual Light Alarm with iPhone
2

Cool, did have a need for this already a couple of times, so interested to see it approved and hopefully useful in my cases

3

there is no flow cart to set a tag to a alarm, could this do the job?

with the shortcut app from apple I set a alarm on my phone and set a tag within a webhook to homey 15 minutes before the alarm goes off. so I set alarm to 07:00 the webhook will send 06:45. with this tag I want to set the alarm in homey, and with this alarm I start al wakeup flow.

only the thing is. there is no flow card with set alarm to (tag).

4

You’ll get the option to use a flow trigger with “The time is” which could use your variable from the webhook, as long as it’s in the format HH:mm. Then that trigger will be executed at the time set to the variable. So if I understand you correct, this could solve that, yes :slight_smile:

5

Aah i think you understand me correct😁 will try this when it can. Thank you!

6

@Robin_De_Lange @Patrick_Van_Deursen

It’s now live. Link to app in App store can now be found in the first post :slight_smile:

1 Like
7

@kjeet90 it works, thank you very much!

1 Like
8

This works like a charm!! have added links in different discussions already, as this was a recurring feature request from others as well!

Question, does this work with BLL:

Within all flowcards that supports BLL coding, you can add any BLL expression within the next codeblock: {[ expression ]} .

1 Like
9

There are currently no support for this, but it is something I could look into adding. Do you have some usecase examples, as I’m not very familiar with the use of BLL.

10

@kjeet90 , thanks for the reply.

My usecase is that I want to have the radiators turn on at a specific time, which I calculate based on the current temperature, the to be achieved temperature, the heating speed and the time it needs to be warm. Based on those variables, I want the heater to start at a specific moment.

I would used BLL for that to calculate and then use that tag in the rest of the flow. However, as for this one, I start the flow with timey, there is no way to have BLL first do the calculations, so would need to embed that in the time variable of Timey.

Is that clear?

11

I won’t be able to do anything about it until next week at earliest :face_with_diagonal_mouth: But I will take a look into it if it’s something that I should add

Possible workaround?: Do the calculations with BLL and write the result to a normal string variable and use that variable in the trigger card of Timey?

12

Yes indeed possible, and will take that route otherwise.

thanks for looking into it, no rush though!

13

@kjeet90 , This app is very good, thanks for developing! I had a post a time a go " How to start a flow at a spesific time stored in variabel, with built in functions (Solution - Check every 60 minutes or use the app "Timey") " , and your app can do actually what I was searching for, a way to start a flow at a given time from a variabel. Thanks again, much appreciated!

2 Likes
14

Hi @kjeet90 ,

I have a little challenge. I use a calculation to set the HH and MM for timey. however, if I do the calculation and it ends up being 5 min (as in 5 min past 9 f.i) Timey errors out, as it needs HH:MM. if it get 8:5 (5 minutes past 8) it doesnt work (neither for the 8 nor the 5… they both need the leading 0). Anything you can do in that case?

Or maybe different/better/easier for me, could we also get it to work with just decimal numbers, i.e. f.i. 9.752346 would be 09:45

15

It’s only required with a leading zero on the minute part, you can actually do 9:50. The minutes part will continue to require leading zero because I don’t know if the user wants 9:5 to be 9:05 or 9:50.

The 9.752346 format is something I could look into adding :thinking:

1 Like
16

Understand that 05 or 5 or 50 would indeed be confusing. in the decimal version that would solve itself, as 9.5 would clearly be 09:30

Would really help remove a number of calculations on my part (with removing the need of adding the leading 0 when needed), so :crossed_fingers:t2::crossed_fingers:t2:. The point is that you can immediately use the result from a calculation and would not need to add a step in formatting. would make timey more universally useable. Now I need to do:

image
image913×192 54.3 KB

And this also does not work, due to the leading 0. I thus need to check if the mm part is lower than 10, and then in a text box add a 0 to that number, make that a text (as in a number string, the leading 0 gets dropped again), and then add it to Timey…

and indeed the leading 0 is only needed on the MM part not the HH

17

@Patrick_Van_Deursen , as you are calculating time, why would it help that you have to convert .5 to .30, besides adding a leading 0? As times must be given with 05 and 50. There must be something i misunderstand.

18

I need to convert my decimal calculation to a hh:mm standard. I thus need to extract the decimals, convert those to minutes, check that there is not a need to add a leading zero. And then pass that together with the hour to timely in a hh:mm format

Unless I am doing something overleg complex

Why not immediately take the result (in decimals) is what my question is here.

1 Like
19

I do understand the question. If the app can calculate from decimals, then you do not need to do it. The usecase is clear, thank you :slight_smile:

1 Like
20

@Patrick_Van_Deursen I’ve published a test version with decimal support. Can you check if this works for you?

3 Likes