Untangle conditions

Configuration
,
21

I see, yes, thanks for explaining so clearly.

Am I right concluding this (my original automation) would be an equal burden then:

  - alias: Alarm Clock
    id: 'Alarm Clock'
    initial_state: 'on'
    trigger:
      platform: time
      minutes: '/1'
      seconds: 00
    condition:
      condition: or
      conditions:
        - condition: and
          conditions:
          - condition: template
            value_template: >
              {{ now().time().strftime("%H:%M") == 
                states('sensor.alarmclock_wd_time_template')}}
          - condition: template
            value_template: >
              {{ is_state('input_boolean.alarmclock_wd_enabled','on')}}
          - condition: template
            value_template: >
              {{ is_state('binary_sensor.workday_sensor','on')}}
        - condition: and
          conditions:
          - condition: template
            value_template: >
              {{ now().time().strftime("%H:%M") == 
                 states('sensor.alarmclock_we_time_template')}}
          - condition: template
            value_template: >
              {{ is_state('input_boolean.alarmclock_we_enabled','on')}}
          - condition: template
            value_template: >
              {{ is_state('binary_sensor.workday_sensor','off')}}
    action:
      service: script.alarmclock_ring
22

Yep, anything that fires a lot is a burden. Even then, its not really a burden unless you have a lot of them on a low power device.

23

Not a lot no. Would there be a better way to have an alarm trigger?

24

Not really, unless you move to appdaemon.

25

Since I havent done that yet (Appdeamon): if that would still be a good idea now Lovelace is maturing, I might try and do so. Have a good pointer for that, related to this challenge? A time frequent automation for an alarm clock being lighter on the processor?