Trigger template not working

Configuration
1

This was working when it was time triggered, see the hashed out section
running check config doesn’t show anything, but its getting ignored

  - alias: 'Hot water boost off'
    trigger:
      - platform: template 
#      at: '09:00:00'
#    condition:
#      - condition: template
        value_template: "{{ states('sensor.hot_water_temp') | float > 55 }}"
    action:
      service: switch.turn_off
      entity_id: switch.hot_water_boiler
## just in case above fails or temp not reached #########
  - alias: 'Hot water off1'
    trigger:
      platform: time 
      at: '09:55:00'
    action:
      service: switch.turn_off
      entity_id: switch.hot_water_boiler

I could simplify my automation by using the above to trigger on a time interval every 10mins
my automation is basically
Turn on hot water in morning
Turn off hot water at a time
turn on hot water afternoon
Turn off hot water at a time
Turn on hot water in evening
turn off hot water at time

My second question is when the automation file is read are the actions listed forced to run sequentially ?
or could I just use 2 scripts
ie.
turn on hot water at (time =0630 OR 1430 OR 2100) IF water temp is less than 54

Then a script as I’ve tried triigered on stae or time interval turn off if water temp greater than 56
sorta:-

  - alias: 'Hot water Boiler on'
    trigger:
      platform: time 
      at:'06:45:00'
      at '14:30:00'
      at '21:00:00'
    condition
      - condition: template
        value_template: "{{ states('sensor.hot_water_temp') | float < 54 }}
    action:
      service: switch.turn_on
      entity_id: switch.hot_water_boiler
#####  switch when hot water temp reached #########
  - alias: Hot water off
    trigger:
      platform: time_pattern
      minutes: '/5'
    condition:
        - condition: template
          value_template: "{{ states('sensor.hot_water_temp') | float > 56 }}"  
    action:
      service: switch.turn_off
      entity_id: switch.hot_water_boiler

Or would it be better on the OFF section to trigger on value template of > 56
thanks

2

the following checks OK, not sure if it could be tidier

  - alias: Hot water boost on
    trigger:
    - platform: time
      at: '06:50:00'
    - platform: time
      at: '14:30:00'
    - platform: time
      at: '21:00:00'    
    condition:
      condition: and
      conditions:
        - condition: template
          value_template: "{{ states('sensor.hot_water_temp') | float < 53 }}" 
        - condition: template
          value_template: "{{ states('sensor.solar_power') | float  < 1790 }}"
        - condition: state
          entity_id: input_boolean.notify_home
          state: 'off'
        - condition: state
          entity_id: input_boolean.notify_away
          state: 'off'  
    action:
      service: switch.turn_on
      entity_id: switch.hot_water_boiler

  - alias: Hot water boost off
    trigger:
      platform: time_pattern
      minutes: '/10'
    condition:
      condition: or
      conditions:                 
        - condition: template
          value_template: "{{ states('sensor.solar_power') | float  > 1800 }}"
        - condition: template
          value_template: "{{ states('sensor.hot_water_temp') | float > 56 }}"  
    action:
      service: switch.turn_off
      entity_id: switch.hot_water_boiler
3

You are using a lot of template conditions where you could just use numeric state conditions. And you are needlessly supplying the AND condition (it is the default behaviour). e.g. for the first automation:

    condition:
      - condition: numeric_state
        entity_id: sensor.hot_water_temp
        below: 53
      - condition: numeric_state
        entity_id: sensor.solar_power
        below: 1790
      - condition: state
        entity_id: input_boolean.notify_home
        state: 'off'
      - condition: state
        entity_id: input_boolean.notify_away
        state: 'off'

and for the other automation:

    condition:
      condition: or
      conditions:                 
        - condition: numeric_state
          entity_id: sensor.solar_power
          above: 1800
        - condition: numeric_state
          entity_id: sensor.hot_water_temp
          above: 56

They’re a lot easier to read and probably use less resources (though that is just a guess).

4

Many thanks Tom, that is a lot simpler