It would be great to be able to just select an attribute to add to an entity card / history chart etc, rather than having to make a new template sensor
I hope you don’t mind that I’ve removed the term “Lovelace” from the title, as that term isn’t used anymore 
Haha apologies - I don’t mind at all 
I’m conditioned…
1 Like
Maybe the answer is for all attributes to become ‘virtual’ entities, so that whatever API calls allow lists of entities to be returned would also allow the attribute to be requested instead of the state
So a motion sensor with a luminance entity might be
sensor.bedroom_motion%luminance.
Or something similar.
I agree… more easy access to attribute values in dashboards, automations etc would be very nice!
Related:
This WTH are attributes such a pain to work with
And this New Helper: Entity from attribute