I noticed something interesting in the logbook for some of my light entities. The logbook entry is showing that the light is being turned on by an unrelated automation.turn_off service call that precedes the light.turn_on service call in the automation that turns on the light.
action:
- service: automation.turn_off
target:
entity_id: automation.light_dining_room_light_in_use
- service: light.turn_on
target:
entity_id: light.dining_room_rgb_light
data:
brightness_pct: "{{ state_attr('switch.adaptive_lighting_rgb_lights','brightness_pct')|int(60) }}"
rgb_color: >
{% set rgb = state_attr('switch.adaptive_lighting_rgb_lights','rgb_color') %}
{% if rgb != none %} {{ rgb }}
{% else %} {{ [255, 214, 170] }}
{% endif %}
- wait_template: "{{ is_state('light.dining_room_rgb_light','off') }}"
timeout: 30
- service: automation.turn_on
target:
entity_id: automation.light_dining_room_light_in_use
In another similar automation that turns the light off, the light.turn_off call is the first step in the action block and the log book entry shows it was triggered by light.turn_off
action:
- service: light.turn_off
target:
entity_id: light.dining_room_rgb_light
Does the log book entry take it’s entry description from the first action step of the automation instead of the actual service call that turns on the light? Is that by design?