When I was reading through the offset documentation I noticed what I think is a mistake in the comment. Could someone validate that this change is correct? Thank you.
* state trigger - entity_id details
I think it would be beneficial to underline in text that it is possible to use multiple entities in entity_id.
Not sure if it is applicable to any other triggers that accept entity_id (like numeric_state)
* ✏️ Tweak
* Sets front matter defaults
* Removes default front matter from section templates/pages
* Removes default front matter from addon pages
* Removes default front matter from integration pages
* Removes default front matter from posts
* Removes default front matter from docs pages
* Removes default front matter from other pages
* Fixes blog category pages
* Automatically create linkable headers
* Visually improve position of linkable header chain icon
* Do not auto link headers on homepage
* Remove linkable_title everywhere
* 🚑 Re-instante linkable_title plugin as NOOP
This makes more clear that: 1) https may be needed rather than http, 2) data is not needed for a webhook trigger to function, and 3) "curl" is a good way to test it. Hoping to save other people some of the time I spent figuring out how to get it to work.
The `for:` piece can be confusing for folks, providing the examples as human readable time, and mentioning that days and milliseconds are also supported.
Removed the out of context block about the sun, under the time pattern. It doesn't appear to fit anywhere, and appeared in the RC merge.
Added warning about `00` and so on
* Add encoding parameter to mqtt automation #20292
This is needed to trigger on received images/other byte payloads via mqtt because otherwise the decode fails. See also
#16004
* Update trigger.markdown
clarify
* Update trigger markdown to expand twilight discussion and sunrise timing
These changes expand on the sun angle for addition darkness by including detail on the three twilight definitions. A brief discussion has also been added to the time trigger section to explain why many automations that are relative to sunrise often fail. Since sunrise is a different day than any time before midnight, using timestamps is a reasonable option.
* Minor changes
* ✏️ Tweaks
* Split interval triggers from time trigger
* Default smaller interval units to zero
* Rename interval to schedule
* Rename schedule trigger to time_pattern
It's often been noted in the forums that Template Triggers are sometimes overload and that you want to use them sparingly. I haven't stress tested my system with this idea, but if the template triggers are tested every time any state changes, then that is the clarification that I've proposed in the documentation.
