Commenting in automations

[solemn halo]

I'm curious. Why the # comments in automations get removed? Puzzles me and makes my life more complicated.

[lunar cypress]

Pretty sure it's still because they're converted to JSON into the transition to the frontend

[solemn halo]

I'm not technical enough so maybe it's a good enough reason for the removal, but it's a pity.

[radiant crag]

even if they are written in YAML and stored in the file in YAML, the process in-between is the one that eliminates the comments.

If you write the automation only in Yaml (in automations.yaml file), then I guess you can keep it, but then forget the UI editing.

[ocean rapids]

Don’t forget you can use alias: to describe the steps too. And you can use comments in jinja.

[lunar cypress]

Indeed, and I think that would be the typical response from the dev folks

[ocean rapids]

Happened to see this just now:
https://community.home-assistant.io/t/editor-deletes-comments/940048/2?u=mekaneck

[lunar cypress]

Well, it could also be out of spite

For those who have chosen the non-YAML path

[solemn halo]

I swear it's not me who crossposted. 😉

[solemn halo]

ok, but only 1 alias: is possible by automation, right?
btw, I'm puzzled by this alias thing. it kinda supercedes the automation name in some places. will need to re-read the doc about this

[solemn halo]

jinja comments: duly noted. but they can appear between any lines, right?

[lunar cypress]

You can use it for any action:

All actions support an optional alias.

https://www.home-assistant.io/docs/scripts/#script-syntax

And conditions: https://www.home-assistant.io/docs/scripts/conditions/

[fluid acorn]

Every trigger, condition and action can have an alias

You can set it using the Rename open under the 3 dot menu in the GUI