Above and below are strict comparison operators (> or <, not >= or <=).
The version before was ambiguous about that by explaining that values like 17 or above will trigger the automation.
* Expand doc for webhook triggers
Edit webhook trigger doc for clarity and grammar.
Add explanation that using a webhook in a trigger automatically creates the webhook.
* Add fenced code language hint
* correct note about trigger
Don't think the existing way of testing automations with trigger in templates makes sense.
I tried to show how to debug such automations.
* add missing bracket
to fix the build
There is no need in using as_timestamp as we can subtract datetimes and then use the resulting timedelta's total_seconds()
I believe it's more intuitive and elegant
* Adding a note about states
It's a regular thing on Discord to have to point this out to folks, so it's long past time we highlighted this somewhere IMO.
* ✏️ Tweak
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
A common question in the support channels involves the `UndefinedError` returned when an automation that references a trigger state object in the action is manually triggered. Hopefully this note will reduce those questions in the future. I also tweaked the example automations.
Looks like a similar change was made to `automation_sun.markdown` in #10532, attributed to #10315.
As someone trying to add an automation for the sun's elevation, the inconsistency was confusing. I don't know if other parts of this page should be updated in a similar way.
* automation troubleshooting.markdown
Add explanation of making check config visible
* withings.markdown
Add explanation of how to make the check config tool visible
* configuration.markdown
Add explanation to display the check config tool
* Clarified the behavior of conditions.
The current reading of the documentation indicates that if a condition evaluates to true it stops executing. Added additional context to the first line to describe the actual behavior.
* Updated docs to clarify conditions behavior
The current reading of the documentation indicates that if a condition evaluates to true it stops executing. Added additional context to the first line to describe the actual behavior.
* Renamed script to automation
* Changed to script or automation for consistency.
