Hi, Is it possible to determine the time difference between the two in a template? the first: {{ as_datetime(states('input_datetime.test')).strftime('%d %B %y - %H:%M') }} the second: {{ now().strftime('%d %B %y - %H:%M') }} so the first is based on a start time of an automation, when the aut…

All you ever wanted to know about time manipulation in templates (and more): [image] The EPIC Time Conversion and Manipulation Thread! Configuration After seeing many threads on the forum asking for help with time conversions and calculations using time and realizing I ge…

[image] Templating Instructions on how to use the templating feature of Home Assistant. {{ time_since(as_datetime(states('input_datetime.test'))) }}

input_datetimes do not store a timezone. So if your datetime is local, you need convert it to local time. {{ as_local(as_datetime(states('input_datetime.test'))).strftime('%d %B %y - %H:%M') }}

hm I’ve tested your example @Troon but I get an output like: 3 hours the test input datetime sensor is set on: 2024-06-10 13:00:00 so I would expect an output like 2.5 hours? Is it rounding the output? @koying I saw the page and I’m still testing. When I create another helper (datetime) for th…

[image] 1mfaasj: hm I’ve tested your example @Troon but I get an output like: 3 hours the test input datetime sensor is set on: 2024-06-10 13:00:00 so I would expect an output like 2.5 hours? Is it rounding the output? You seem to be allergic to reading the documentation that I linked. He…

[image] Troon: {{ time_since(as_datetime(states('input_datetime.test'))) }} yes you’re totally right, it’s a maze at times with all kinds of templates that do all kinds of things (on my side) to find the right one for this situation. but thanks for the reminder anyway.

If you need a difference between two times, it is easiest to convert them into epoch timestamps (number of seconds since 1970). For a helper, it is easy state_attr('input_datetime.xyz', 'timestamp')

That timestamp can get you into all sorts of trouble because the input_datetime is not datetime aware and the value could be UTC or your local timezone. That’s why it’s generally accepted to not use those attributes.

Well… timestamps do have certain specifics, but can be very realiable when observing those (I am a programmer, might be biased :grinning:). I have found out that input_datetime is not TZ aware, but the timestamp attribute it has “is always UTC”. As opposed to doing input_datetime | as_timestamp on …

Yes, but as a programmer you should understand that datetime aware objects are better than timestamps. I.e. using {{ states(input_datetime) | as_datetime | as_local }} provides exactly that and can be directly used with timedelta objects making it so you can completely avoid unit conversions. It t…

Time difference - based on an datetime helper and template

Configuration

koying (Chris B) June 10, 2024, 12:42pm 2

All you ever wanted to know about time manipulation in templates (and more):