I agree that wording is important, but we can’t all be HA experts using the exact HA wording when this is essentially a on the side occupation.
I also agree that it is preferable that this kind of discussion can be avoided.
Personnaly, even while looking into these HA wordings, I did not find a single page defining these specific wordings clearly. It’s only by becoming an expert on HA that these specific working become apparent, and visitors of this forum can’t be expected to know all that.
A simple page where this is listed/explained can help. It could explain the wordings that are should be used when communicating in relation with HA. And it could be pointed to in case a forum user is seemingly not familiar with them. It could also be part of the documention, especially in the introduction.
Something like (not perfect, not optimised, without links):
- condition: a condition explicitally labeled as a condition or conditions in an automation, choose action, repeat action, … . The term “condition” does not refer to “state below 14” as part of a trigger specification, or anywhere else.
- event: refers to an event available on the HA event bus. It has a name on the event bus, and it does not refer to anything else such a the real time even of an expired delay, it does not refer to a trigger and not all triggers depend on Home Assistant events.
- trigger: refers to automation triggers (link) that can an item for the ‘trigger’ field of an automation, or the “wait_for_trigger” action step of an automation or script,
- automation: automation script consisting of triggers, conditions, and (a sequence of) actions .
- script: the script defining a sequence of actions
- state: a main state value, and a set of attributes generally representing an entity,
- entity:
- device:
- service:
- custom component:
- add on:
- … .
- … .