Have I missed something?
There seems to have been a very good attempt to improve the docs but have they taken one big step forward followed by two or three small steps back?
I haven't needed to check the docs for a trigger for a long time but I wanted to check the syntax when using
for: <input_number>
but it all seems to have been compressed into guidance for creating an automation through the UI with very small and incomplete collapsed sections for using yaml
The trigger and condition docs are being overhauled to include the "Purpose specific" variations that should be part of the 2026.7 release next week. But, they've partially rewritten the existing trigger docs as well.
I noticed issues similar to what you have mentioned in the "Manual Event" trigger docs a couple weeks ago and submitted feedback. There are fewer YAML examples, zero examples showing template use, and all kinds of weird choices. Looking at the other "core" triggers that have been given their own pages.
It really looks like someone made a template and either just stuck to it even when it didn't make sense, or used AI to populate it. They all seem to have the same headings, two (and only two) YAML automation examples without templates, same two "Tips", same nonsense "Related Triggers" section...
Please go to the page(s) in question and use the "Provide Feedback" link at the bottom to provide constructive criticism where you think it is needed.
Don't get me wrong, I think the new triggers and conditions are a step forward, even for YAML users. A number of the new triggers include "behavior" options that reduce the need to use trigger-condition patterns that trip people up. They automatically handle "unavailable" and "unknown" in a more intuitive manner, so you don't have to tell every automation to ignore those states. And, a number of things that used to require the use of an Event trigger now have their own set of targeted triggers such as Timers and To-do's.
I just don't understand the logic of removing examples... some of which were added by the community to address deficits left by previous rewrites. The logic can't be that it was done to streamline the docs, because they're now filled with pointless "Tip" sections, other clutter, and some nonsense.
100% I'm just in no rush to move over to them. But they are the right step forward. I'll be using them for new automations.
I think they are just "changing the docs for the new triggers" and some of the old examples are getting left in the dust. When the dust settles, we should just add them back.
Unless I'm missing something spectacularly obvious, those old examples were still valid though. Why would they be removed & make someone go through the effort of rewriting them from scratch (or grabbing them from the wayback machine)?
At least to me, it's quite clear cut - don't remove any examples if the config is still valid. Hide it under a yaml tag if you have to, but leave it well alone.
That's a question for the guy who actually did the work. I have no idea why, and it's pointless to speculate. If you have feedback, provide feedback to github so the guy making the changes can see it.
I don't really consider it dumbing down, if you know what you're doing... you can still create the yaml without examples. It just makes it harder if you don't know what you're doing.
