Sanity check and questions about my contact closed automations

[drakefs]

I have a gate with a contact sensor installed on it. When the gate is open, it triggers a smart bulb to turn on red. When the gate is closed it checks if the bulb is supposed to be on, it changes to color to the normal color and if the bulb is supposed to be off, it turns the bulb off. The bulb is scheduled to turn on at 6pm and turn off at midnight.

I had to make two separate automations for when the gate is closed to account for whether the bulb is supposed to be on or off.

alias: Gate Closed while Lamp is Scheduled Off
description: ''
triggers:
  - trigger: door.closed
    target:
      area_id: back_yard
    options:
      behavior: each
conditions:
  - condition: schedule.is_off
    target:
      entity_id: schedule.living_room_lamp_schedule
    options:
      for: '00:00:00'
actions:
  - action: light.turn_off
    metadata: {}
    target:
      area_id: living_room
    data: {}
mode: single

alias: Gate Closed while Lamp is Scheduled On
description: ''
triggers:
  - trigger: door.closed
    target:
      area_id: back_yard
    options:
      behavior: each
conditions:
  - condition: schedule.is_on
    target:
      entity_id: schedule.living_room_lamp_schedule
    options:
      for: '00:00:00'
actions:
  - action: light.turn_on
    metadata: {}
    target:
      area_id: living_room
    data:
      rgb_color:
        - 255
        - 255
        - 255
      color_temp_kelvin: 5500
mode: single

First question is can I consolidate these two automations into one automation (if/then + elseif/then)?
If yes, should I consolidate the automations (best practice)?

[Didgeridrew]

@drakefs

First question is can I consolidate these two automations into one automation

Yes, these would be reasonable candidates for combining.

@drakefs

If yes, should I consolidate the automations (best practice)?

The best practice is to build automations that you understand. Beyond that it’s mostly personal preference.

---

There are a number of previous threads that cover this topic with a variety of examples of how different users approach combining automations:

Combining automations to simplify admin

I’m trying to learn how to make automations more efficient. I currently have an automation for each door for when its opened and when its closed. I have 6 doors that I am monitoring making 12 automations. Each automation is watching a door sensor. When triggered, the sensor will light up an LED when the door is open. Then another automation to turn off the LED when closed. I made a status indicator panel on my desk with several LEDs and ESPHome so I can quickly see the status of each door…

Several automation in one

Good morning I would like to create several automations in 1 to avoid having too many for the same thing -I would like when my switch is turned on it turns on the light -I would like that when my switch turns off it turns off the light -I would like that when my light is turned on it turns on the switch -I would like that when my light turns off it turns off the switch I managed to do it with 4 automations which takes up space Sincerely

Cannot figure out how to combine 2 automations

I have the following pair of automations that I would love to combine to streamline and eliminate an automation. For the life of me, I cannot figure out how to trigger the process. The conditions to decide actions could stay the same. The first automation boots my Unraid backup server at a set time on a set day of the week and turns on a helper switch. Once booted unraid fires up a script to trigger the backup process. Start automation: alias: Unraid Backup trigger Start backup description…

[drakefs]

Thanks for answer and the additional info.

[drakefs]

An update for anyone trying to use the yaml, rgb_colorand color_temp_kelvin cannot be used at the same time (the gui currently allows both to be set but the automation still error out). Apparently color_temp_kelvin does set the bulb to “white” at that color temp.