I would swear that the event used to be posted after the Template integration finished reloading (not before).
In fact, way back in 2021, I created an FR asking for such an event (signal when Template integration finished reloading) and then discovered it already existed in the form of event_template_reloaded
. I used it successfully in several Trigger-based Template Sensors.
Back then, a Trigger-based Template entity’s state did not survive a restart. So I wanted an event, to trigger a Trigger-based Template Sensor, whenever the Template integration was finished reloading (like on startup and whenever the Template integration was reloaded to add a new Template entity). The Event Trigger became unnecessary after the Template integration was enhanced to store the state of a Trigger-based Template entity.
If the event now occurs during the reload phase, then that’s a Breaking/Backwards Incompatible change I don’t recall seeing in the release notes.
Maybe it was never documented in Breaking Changes and is the side-effect of some other PR. For example like when a PR sought to improve performance and expand
ceased to sort its output. That seemingly innocuous change, buried in “All Changes”, quietly broke templates that relied on expand
’s previous behavior.