Multiple Conditions Influencing the Device that is Actioned

Configuration
1

Merry Christmas to those celebrating.

I have an automation that is triggered by the gas boiler running, it checks if the target temperature (input variable) is above or below the actual room temp (sensor). If below then it turns on the flow switch (TRV) to that radiator.

It’s working well, I could obviously replicate this for every room (15 rooms) but its seems like a lot of space to take up. Could I therefore have multiple conditions that then influence multiple triggers?

alias: Heating - Study On
description: ""
trigger:
  - platform: state
    to: "on"
    entity_id:
      - binary_sensor.vicare_circulation_pump_active_0
    from: "off"
condition:
  - condition: numeric_state
    entity_id: sensor.study_room_temperature
    below: input_number.gf_study_target_temp
action:
  - type: turn_on
    device_id: cb3bb7975793101ed37384b472acd285
    entity_id: switch.radiator_study
    domain: switch
mode: single

I.e. adding more conditions to say:
If sensor.living_room_temperature is below input_number.living_room_temp then it would turn on switch.radiator_living room
And continue this to add multiple switches, targets and rooms?

Or is the only way to have 15 different automations (living room, kitchen, bedroom1, bedroom2) etc.
I can change the naming to be more consistent if it would help to pass a variable name

Thanks guys

2

There are a number of stategies you can use to reduce multiple automations into just one.

Choose Actions

Templating

Trigger Variables

While not strictly necessary, a consistent naming convention makes designing concise and efficient templates easier.

3

Thanks Digeridrew, looks like I missed this when searching the docs.
I think Nesting in Choose Actions is exactly what I am looking for!

Thanks for the pointer.