I have a sensor that reports the last time a device_tracker’s location changed and I’m trying to calculate the time that has passed since then (eg: now - last_changed), but I’m not a Jinja Ninja. :sweat: This is essentially my starting point: [image] {{ now() }} - {{ states.sensor.husband_s_moto…

You should use params there. If your states change during the execution of the template, you’ll get odd results. The chances of this are low, but it can happen the way you are doing it. Lat and Lon are floats inside attributes, no need to convert. Rounding in the if statement to zero will remove …

try using the device_class: timestamp see: https://www.home-assistant.io/components/sensor/#device-class there’s also this: hassio_online: friendly_name: Hassio online value_template: > {{ relative_time(states.binary_sensor.hassio.last_changed) }}

Ah, formatting after-the-fact (outside of this template) hadn’t even crossed my mind. However (which I failed to clarify in the OP :pensive:), I’m planning to combine this template with other (non-timestamp) templates as attributes in a template_sensor. If I’m understanding correctly this would no…

not really sure what you are planning to do, but yes, both the device_class and the ‘relative’ work on date time objects only. If you show us what you want to add to the template, we can see how to help.

Take a look at this [image] The EPIC Time Conversion and Manipulation Thread! Configuration strptime(): - converts a string to a datetime object - strptime(date_string, format) – NOTE: I’ve tried to make all of these posts able to be copied as is into the template editor…

[image] Mariusthvdb: not really sure what you are planning to do… My initial goal was to incorporate states and attributes from several components into a single template_sensor, but after some fiddling I decided that was too limiting for my use-case – which is to display the data in a more-in…

[image] Tomahawk: Take a look at this Wow, LOTS of info there! Much of it over my head right now, but thanks for the resource.

Here’s an example of the weird behavior I’m seeing: template_sensor shows 3 miles: [image] Exact same code copied/pasted into Template Editor shows (correctly) less than 1 mile: [template_editor-wife_distance_from_home] Here’s the codeblock: - platform: template sensors: wifes_dis…

While posting I noticed a(nother?) mistake: I have if ... <= 1 folowed by elif ... == 1. :roll_eyes: I’ve corrected it now to if ... < 1 … elif ... == 1.

Ah, I think I just realized what was causing the strange behavior: I did not have an entity_id referenced to trigger updating the template_sensor. Per the docs . :persevere: I’ve now added: entity_id: device_tracker.zy225dsn4h_2

That’s only required if the sensor can’t determine an entity to update from. I’m pretty sure if that is the case then there will be a warning printed in the log. At least that used to be true. If there is no warning then I don’t think that is a problem. But it also can’t hurt to put it in either.

Need help calculating time in a template

Configuration

Tomahawk August 5, 2019, 7:39am 5

Take a look at this