Related: link
It is not possible to know which blueprint is used for an automation - there is no such an attribute:
But it is possible to see which automations are using some blueprint:
Seems there is an association between a blueprint & an automation already available…
But this association is not exposed to a user as an attribute.
It will be useful to have a “blueprint” column here:
It would definitely help your cause getting this implemented if you provide good use cases for this data.
What are things you could do with the data?
Same use-cases as for using this column:
Or for this:
To gain more control on automations.
To see what automations are NOT using some blueprint instead of using it (assume someone created 1000 similar automations and then discovers a “blueprint” term in docs, or finds a fitted blueprint in HACS - then the user is starting “unifying” his/her automations).
To see what automations are based on some particular blueprint (which is already is possible as I shown on a screenshot above - but having this data in a common table is more useful).
Actually, an answer to this question is obvious.
Changes in 2024.4, 2024.5 made the job a bit easier - but still insufficient.
You can filter automations by a particular blueprint(s) - but cannot filter out automations NOT based on a blueprint.
Related discussion - Labels: add filtering by "no labels" (similarly - for "area" & "blueprint") · home-assistant/frontend · Discussion #20418 · GitHub
But having a blueprint in a separate column is still desired.
