that was really quick. seems to work as advertised.
Thanks @kjeet90 !!
@kjeet90 , Is it a way to differ when it will it accept MM and Decimal, seems like it is the same “when” card?

The cards now accepts both formats. If you hover the little
it says that you can use either HH:mm or HH.decimal
Thanks @kjeet90 , I saw that. Then I will just adopt my flows to give a error if it no leading zero, when needed. A couple of flow cards less for @Patrick_Van_Deursen , a couple of more for me.
No big deal
Why would you need to change anything? It still accepts the same as it did before. If you use : as a separator it requires two numbers after the : but if you use . you can use one or more
Good thinking @kjeet90 , did not think of the separator as a break.
So, the and card clearly works if I use the test from here feature in the advanced flows. I seems as though this does not trigger in the flows themselves? The when card clearly does not seem to trigger. I am using a number variable and not a text variable. not sure if that should be an issue though.
None of these trigger unfortunately:
and neither does this:
Yepp, I think I know what’s wrong. I won’t be able to fix until later today though ![]()
@Patrick_Van_Deursen Test version v1.1.1 out now which should hopefully resolve all your issues ![]()
Works like a charm!
Yes, it requires to have either a . or a :
Edit: I’ll add support for whole numbers like 9 without . or : and consider that to be 09:00. Don’t have time to do that today though
@Patrick_Van_Deursen Support for H format added to v1.2.0 which is in test now.
like a charm! Will do a last check this night, and then switch over to timey driving the respective flows!
I’ve published a new test version (1.3.0) with support for the BLL decoding. Can you give it a try for me?
Yes, will try.
And it seems to work! Will give it some more tests the coming days, but thanks for the implementation. Reduces the amount of variables and simplified the calculations ![]()
Great app. Thank you. I’ve never understood why the standard Date & Time flowcards aren’t supporting variables as an input (hh:mm would be ok for an out of the box feature).
Two questions, maybe feature requests:
- Have you thought about supporting a flow card that determines if a given time is before or after another given time. For example: I am calculating the time when a specific light mood is turned on based on the sunset. If the calculated time is later than a given time I want to apply a different schedule.
- Related to my use case above where I take the sunset as a basis to determine when to select a light mood: Have you thought about providing a flow card that adds or subtracts hours or minutes to a given time and returns it as a variable? Maybe it’s possible via a BLL expression, but I have no clue how…
I can probably add this ![]()
This should be possible with BLL I guess, just to post what you want to achieve in the BLL topic and I’m sure someone will help you out with that one ![]()
Awesome! Version 1.4.0 installed, flow updated, and it’s working like a charm. ![]()




