[Potential bug?] Blueprint trigger variable woes

Configuration
1

Hi there! I'm working on my first blueprint, but I'm running into an issue that I can't seem to resolve. I believe this to be either a bug in home assistant or an error in the official documentation, but before filing a bug report I want to sanity check first.

Consider the following blueprint:

blueprint:
  name: Dummy
  description: Dummy
  domain: automation
  input:
    time_dummy:
      name: Time dummy
      description: Time dummy
      selector:
        time:
    enabled_dummy:
      name: Enabled dummy
      description: Enabled dummy
      selector:
        boolean:

trigger_variables:
  time_dummy_trig: !input time_dummy
  enabled_dummy_trig: !input enabled_dummy

triggers:
  - trigger: time
    at: "{{ time_dummy_trig }}"
    enabled: "{{ enabled_dummy_trig }}"

As documented in Time - Home Assistant, "(...) You can use a time string, an input_datetime entity, a timestamp sensor, a mapping with entity_id and offset, a limited template, or a list."

Furthermore, Automation triggers - Home Assistant documents the option to disable triggers without removing them and specifically mentions that this can be done based on blueprint inputs.

However, even in my very simple example, neither feature seems to work. Is this a bug/error in the documentation, or am I losing my marbles?

2

I didn't think Time triggers supported templating for at... you can just use the inputs directly.

triggers:
  - trigger: time
    at: !input time_dummy
    enabled: !input enabled_dummy
3

Thanks! That does indeed solve my issue! Just to check, should I still leave feedback for the documentation? Because the documentation specifically mentions limited template support for "at".

I suppose I will also try the example in the documentation for disabling triggers to see if that feature works as documented.

Edit: noticed the edit in your post. I will leave feedback so that the documentation can be updated to correct this issue.

4

That whole page appears to be only a couple weeks old. If you do leave feedback, I would include a comment about it lacking examples for the different options. In the past, the docs have usually tried to have at least one example of template use wherever they are supported.

The enable config variable has supported templates for a while, so you should be fine with that one. I'm just not sure on at...

5

I just tried a little experiment with a super simple automation

description: ""
mode: single
triggers:
  - trigger: time
    at: "{{ 17+ 1 }}:06:00"
conditions: []
actions: []

And despite looking broken in the editor, it did trigger, so the documentation is correct and it's probably just the UI showing things incorrectly. I'm going to do some more experiments and based on the results I'll file a bug report so that this can hopefully be resolved in a later update, though IMO it's not high priority if the feature does work, but it's just the presentation that is broken.

Thanks for your help!

EDIT: experiments confirmed that both features work as documented, but are presented incorrectly in the UI.