Automation best performance - once large, or several smaller?

Configuration
1

I have a scenario with a bunch of temperature sensors where there is a potential for many of them to be triggered within a short time span.
Once triggered, the action is a simple notification call with some templating info to show which unit triggered the alarm.
Different sensors will be tied to different alarm recipients meaning that it won’t be a single one receiving all of them.

Which solution would be the most reliable solution and optimal from a performance perspective:

  1. One big automation with all the temp sensors in one go. In actions, I go with “choose” and then setup one flow for each recipient.

  2. Several smaller copies of the same automation but with sensors split according to the receipient. One automation per recipient.

Any thoughts?

2

Personally I’d find the 2nd option easier to maintain. Both would work well but you might find you have to run the first option in parallel mode.

3

Good point. I’ll run the second as parallel as well just to be on the safe side.

4

Can you elaborate on what each 'alarm recipient ’ receives? If you have already created the automation(s), please post it (them).

5

Sure. The code below would be for one recipient. (I’m experimenting a bit with HTML formatting but I’ve removed most of it for clarity). Now that I think about I agree more with @tom_l because using choose will make it too convoluted.

alias: high_temp_test
description: ""
trigger:
  - platform: numeric_state
    entity_id: sensor.t_1
    for:
      hours: 0
      minutes: 0
      seconds: 0
    above: -13
  - platform: numeric_state
    entity_id: sensor.t_2
    above: 8.5
    for:
      hours: 0
      minutes: 5
      seconds: 0
  - platform: numeric_state
    entity_id: sensor.t_3
    for:
      hours: 0
      minutes: 5
      seconds: 0
    above: 8.5
  - platform: numeric_state
    entity_id: sensor.t_4
    for:
      hours: 0
      minutes: 5
      seconds: 0
    above: 8.5
action:
  - service: notify.notify_test
    data:
      title: Temp alarm
      message: ""
      data:
        html: >-
          High temperature in: {{trigger.to_state.attributes.friendly_name }}
mode: single
6

How does it differ for another recipient?

7

You can add variables to each trigger for diferents messages / destinations.

8

Different entities for each different recipient.