For-statement for automation with numeric state

[123 (Taras)]

@Youpimatin

I use a periodic trigger instead

Given that you can’t template for in a State Condition and elapsed-time calculation based on last_changed can be unreliable, can you explain how you are using the Time Pattern Trigger as a way of getting around those two limitations? I’m not seeing how a Time Pattern Trigger can do that …

---

EDIT

Here you go:

What the heck is with the 'latest state change' not being kept after restart?

Every reboot I loose so much data about entities that I would like to keep on. Last time guest visited my house? Last time heating unit went on (to be checked in summer)? Last time never-used light changed? The answer is always the same: x hours/days ago, where x = date of restart. I know I can use automation and store that data in input_date or whatever… But it’s not easily visible in UI, i.e. as a secondary-info. [image] That light was on last time 3 months ago, not 18 hours.

225 votes in favor of the proposal to allow last_changed to survive a restart.