Jan Bouwhuis

If I read https://www.home-assistant.io/docs/automation/trigger/#trigger-variables it seems that trigger variables should be supported. So let's reopen the issue and see if we can get this to work, as it it clearly...

This should make it possible to use templating for `discovery_id`, `type` and `sub_type`. using the `trigger_variables`: https://github.com/home-assistant/core/pull/107830

> the `device_attr` isn't supported in limited templates, so I guess this won't work in trigger_variables. Did you try it? It is just that the template is rendered once, at...

`device_attr` might not be available in the trigger_variables, but with the PR it can be used directly in a template on `discovery_id`.

Trigger variables will be inserted for use inside the template, further all template features are available including the state of the device automation as `this`

This alternative PR removes the need to add `discovery_id`. So that makes it even easier that way to use blueprints: https://github.com/home-assistant/core/pull/108309

Superseded by https://github.com/home-assistant/core/pull/106425https://github.com/home-assistant/core/pull/106425

I have been testing with this, but I cannot reproduce this on dev. I see you have an old version of HA Core. How does this work on the latest...

For an. Matt event to trigger writing the state, the event message must contain the `event_type` set in the JSON message.

Only if event_type is the message or when the message or self has changed attributes, it should update the state.