Thank you, I see it, the same way is used for many other platforms.
But I was interested to define “entity_id” explicitly.
Seems there is no way to do it w/o UI.
Usually I define “id” equal (like slugified) to alias like here:
but in some cases like this one it creates “automation.tracker_traccar_check_alert_iphone_999s” which is undesired. Have to edit entity_id manually in UI then.
The automation’s entity_id remains unchanged. Its friendly_name is changed.
If you modify the an existing automation’s alias in YAML, it serves to modify its friendly_name (its original entity_id is preserved). Try it and see if you get the same result as I did.
I did not claim that “id” stands for “entity_id”, you misunderstood.
That was merely my initial thought which I refused even before posting the 1st post.
Overlooking that misinterpretation, everything else I wrote explains how an automation’s entity_id is derived from its alias for cases when id is defined and when it’s not.
I see your point, the “It is not said here that “id” becomes “entity_id”” was about:
“Guys, do not think that “id” stands for “entity_id”, it is just to allow changing in UI”.
Language))). (guess you do know Russian…)