hey all, I was wondering: is there a way to create a “sensor” from the secondary info “last-changed”? i know how to “show” it in lovelace, but i want that information to be sent out as notification to my phone. there is an automation i would like to integrate it in, so when my phone is detected a…

You don’t need to create a sensor. Just use this template in your message: data: message: "Your message here {{ states.sensor.your_sensor_here.last_changed }} more message if needed"

Tom, my man… when you r right, you’re soooooooo right… i couldn’t figure out the syntax, but yours - magically works. thanks man! :innocent:

You can use the relative time function if you want it in a more human readable format too: {{ relative_time( states.sensor.your_sensor_here.last_changed ) }}

hey! that nice too! but maybe a little to simplistic… anything in between? maybe, just the “time” in a hh:mm:ss \ hh:mm presentation ?

Have a read of this and see how you go: [image] The EPIC Time Conversion and Manipulation Thread! Configuration NOTE: I’ve tried to make all of these posts able to be copied as is into the template editor and work. Due to some of the examples I’ve included you will get e…

nnnooooooooiiiiiceeeee! never new it existed… i’d still would need some syntax pointers… like… where do i put the: “%H:%M” argue? (sorry for my zero programing background) :+1:

{{ as_timestamp( states.sensor.your_sensor_here.last_changed ) | timestamp_custom('%H:%M') }}

i got the “| timestamp_custom(’%H:%M’) }}” part right, but the first part wrong… all works now, thank you guys

Is it possible to do this with a recommended style like this? {{ state_attr('sensor.my_sensor', 'last_changed') }} Unfortunately that gives just None in Templates DevTools section (while using {{ states.sensor.my_sensor.last_changed }} gives expected 2023-03-29 23:55:32.819148+00:00.

No. Last changed is a property not an attribute. See Petro’s excellent explanation here: [image] Last_updated State and last-changed in Lovelace Configuration Ok, so this is where things get funky. You should familiarize yourself with home assistant state objects. This …

Creating a sensor from secondary info: last-changed

Configuration

tom_l June 8, 2021, 4:23pm 6

Have a read of this and see how you go: