WTH expose options attribute as enum

Month of "What the heck?!"
,
1

When using jinja it would be useful for any ‘options’ within the options attribute to be pulled out in an enum like manner, e.g.: options(‘sensor.sensor_name’).option_name this could then autocomplete, making it easier to write templates and throw an error if the entity changes, making it easier to fix

2

Be sure to vote for your own post.

EDIT: ESPHome is pretty good at this. It could be used as a reference

3

HA used to do this and it confused people, I don’t see this coming back.