Two time trigger, same cpu load ?!

have this two triggers the same cpu load?!

trigger:
  - platform: time
    at: '10:00'
trigger:
  - platform: template
    value_template: "{{ is_state( 'sensor.time', '10:00' ) }}"

i’m studying HA and i know that using now() or a sensor.time will force the template to be evaluated every minute…

thanks

Both of them have such a low impact on CPU load that you don’t need to care about it.

Anyway I suggest the first one as it’s easier to read and will not be evaluated every minute as far as I know.

sorry, another doubt… i can’t use a template with at conditions of time triggers, so…

is it possible that HA can miss something like this

- wait_for_trigger:

    - platform: template

      value_template: "{{ is_state( 'sensor.time', '10:00' ) }}"

or

- wait_for_trigger:

    - platform: template

      value_template: "{{ now().strftime('%H:%M') == '10:00' }}"

?!

thanks again

Sorry, but no
pnbruckner elucidated that time triggers (as the first) have to be evaluated ever second (as you could also set a time as ‘10:13:03’ so the second just does it 1/second

Acid test : - put it in the template editor and see what it says
Edit: I’m an idiot, you can’t test that