a yes, thanks.
trying to find where the secondary_info options are configured (would love to have the extra possibility for last-triggered…) but it isn’t in this source I am afraid
or would that be set in a helper card of sorts?
Yeah… that’s not where last_triggered is located. Also, it’s not on all state objects, only automations. That PR probably won’t make it.
EDIT: Just to clarify, last_triggered is inside attributes. Some major changes would be required to display attributes in the secondary info location. It’s not a bad idea, but it should be implemented to accept any generic attribute. Not just a hardcoded single attribute. Even then, with the generic attribute a new field would probably be needed to identify the type of attribute so that the UI formats it properly. Your best option is to make a sensor template with the device_class: timestamp. Then use a custom card to display that attribute as a secondary-info.
My point is that it won’t make it because it’s not generic. If you put a light entity in that field with last-triggered, it will error because the attribute doesn’t exist. I understand you want this, but you gotta make it work for ALL entities.