Automation state: on - how often will it be checked?

Configuration
1

Problem is that you write off some rule and forget how things work over time.
Want to write a simple automation. I will flip an input boolean switch - coming home and HA should check the google drive time to me. So wheni am in proximity of 15 minutes - it will switch on the airconds and bring the temperature down. Below is the rule i came up - but now i’m in confusion. With the trigger input_boolean state to on - will HA check and fire only once when the switch is off from on or it will fire up several time until conditions are met? If the first option than the trigger shoul’d be driving time - state?

- alias: "Presence Coming home"
  trigger:
    - platform: state
      entity_id: input_boolean.rules_cominghome
      to: 'on'
  condition:       
  - condition: numeric_state
    entity_id: sensor.house_temp
    above: 23
  - condition: numeric_state
    entity_id: sensor.dark_sky_temperature
    above: 18
  - condition: numeric_state
    entity_id: input_boolean.time_to_travel
    below: 15
  action:
  - service: climate.set_operation_mode
    data:
      entity_id: climate.mys_zal_31_0
      operation_mode: "Cool"
  - service: switch.turn_on
    entity_id: switch.kitchen_ac
2

It checks when it goes from any state to “on”. After that it does not trigger again until it goes again from another state to “on”.
Perhaps what you want is use a time trigger that fires every X minutes, seconds or what have you and use a condition to check whether your switch is on in order to only do something when necessary.

3

Well i coul use the driving_time like i stated. So everytime it updates - it checks on the condition if input boolean is on. But that sounds like more unnecessary load. So actually woul be wiser that after input boolean is on - something fires up that checks every 5 minutes for other conditions and fires up when they are satisfied. But for this - no idea on the coding

4

Check the driving time (action) every 5 minutes (time trigger) only if the switch is on (condition).
Are you worried about the load of the time trigger? I wouldn’t be.

5

Ok then. Than what will induce the minimum load (out of curiousity)?

  trigger:
    platform: time
    minutes: '/5'

or

  trigger:
    - platform: state
      entity_id: driving_time

Both can be used as trigger in this case. But later is preferable as it is more precise (no lag)

6

How often are you calling the calculation of driving time?

7

Hmm thanks for the heads up. https://home-assistant.io/components/sensor.google_travel_time/

Stes it’s one in 5 minutes. So guess just put that into trigger and that’s it

So then a finalized version will look like this

- alias: "Presence Coming home"
  trigger:
    - platform: state
      entity_id: sensor.time_to_home
  condition:
  - condition: state
    entity_id: input_boolean.rules_cominghome
    state: 'on'
  - condition: numeric_state
    entity_id: sensor.mys_zal_41_3
    above: 23
  - condition: numeric_state
    entity_id: sensor.dark_sky_temperature
    above: 18
  - condition: numeric_state
    entity_id: sensor.time_to_home
    below: 15
  action:
  - service: climate.set_operation_mode
    data:
      entity_id: climate.mys_zal_31_0
      operation_mode: "Cool"
  - service: switch.turn_on
    entity_id: switch.kitchen_ac
  - service: input_select.select_option
    data:
      entity_id: input_select.ventilation
      option: "Low"
8

Curious what energy/money savings you have seen with this Automation?