Define automation … if-then-else-or … so thats an “automation” per definition , thats why i wrote/was thinking ( what ? where ?, in a card … why ?, because i’ve seen errors related to “missing/failing references” which was in a card … so i had to go through my cards to find where i didn’t “delete” this "reference … but yes im aware such “automations” don’t end up under “Automations” … so if this case is as your example, he could have " I found it in
I would never have though about (before now) in a !include ( guess many others the same ) … unless i wrote this include my self of-cause … So this ( your answer ) gave me a “hint”, taught me something … beside his “note” about ( Alias, ID ), good idea to never forget
PS: Obviously it also seems like, that the reason he couldn’t delete the “Automation” was because it was “loaded” … from somewhere , or ? ( which many don’t think of, when they can’t delete i.e an “entity” )
btw, the “punktations” was something i first started with when writing on computers, as in many “editors” they remove triple-spaces … Spaces i found necessary for people to be able to read my handwriting … ellipses and double quotes i use whenever i feel for it, and not necessarily in right context or meaning … so yes that leave “something” for the reader to think about … i.e. do i mean what(word) i write, or something else.
… And you don’t have to undestand, but do think about that many people don’t have the same experience(as you), and knowhow about HA … i guess that’s why they are here … to learn
Just to make things perfectly clear: I write everything in YAML, because I started with HA 4 years ago before there was any UI editing available. I have my configuration broken up using packages:
I have a folder structure based on function and areas, and one automation/sensor/whatever per file. This keeps things very clean and organized. The problem with the two automations was that I just did them quickly as a test and didn’t give them an alias or an id so they would be easy to find. Apparently automation.automation_<number> is how they get named when there is nothing provided to identify them. Now it is a month or so later and I’d forgotten exactly what I had been doing. So it took me searching through all my automation folders and files, one by one, to discover the “strange” automations in the automations/kitchen folder and the automations/outside folder. I have now deleted them and all is well.
… but yes im aware such “automations” don’t end up under “Automations” … so if this case is as your example, he could have " I found it in
