@BodgeIT, my current installation is running at over 1100 entities.
Most of the time my automations run as I expect them to (they always work as written, it’s just that sometimes I don’t write them as I want them to work ).
I’d say my system is a ‘bit’ larger than average, but by no means the largest here, I think Marius runs with over 6,000 entities. Apart from a bit of debugging I’ve never seen the need for this and is but a matter of seconds to paste into any workstation I’m sitting at.
Well, from the amount of time I’ve spent on the forum.
I think I’ve only ever seen a request for something like this twice (including this thread)
I see you have read 1d, but that’s okay, put it forward as a PR and chance your luck.
Normally devs, concentrate their efforts on improved performance, enhanced functionality or something that will equally help ‘a lot’ of users.
I just don’t see the benefit, you will know (from this template) either what happened at 14:23 today, most recently or which happened the longest time ago, what else do you need ?
This is NOT a hack. This is a template
I should also point out that any automation that has never fired or has “
initial: true” set will not appear in any “last_triggered” list so that is worthy of consideration also.
Your adversarial approach may not gain you much traction with the devs however.