you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 6 months ago* (last edited 6 months ago) (4 children)

Here is the full script in case it's helpful. took a hot second of searching to set everything up, but now it's really easy to use. When you call the script inside an automation it has input fields just like if you're calling a built-in function like light.turn_on

For your specific use case though, it may be easier to just take advantage of the built-in Scenes function. You can use an "entity snapshot" with "Scene: Create" a scene of the current state of your "bad" lights when the power goes out, then "Activate" that scene, perhaps with a couple of seconds transition time to smooth things out as soon as power is restored.

I use a similar scene based function to create flashing colored light alerts based on certain conditions.

alias: Light conditional smart dimming (Kelvin)
sequence:
  - repeat:
      for_each: "{{ lights }}"
      sequence:
        - variables:
            light_state: "{{states(repeat.item)}}"
            timescale: "{{states('input_number.timescale')}}"
        - if:
            - condition: template
              value_template: "{{light_state == 'on'}}"
          then:
            - metadata: {}
              data:
                brightness_pct: "{{target_brightness}}"
                transition: "{{transition_rate * timescale}}"
                kelvin: "{{color_temperature}}"
              target:
                entity_id: "{{repeat.item}}"
              action: light.turn_on
fields:
  lights:
    selector:
      entity:
        multiple: true
        filter:
          - domain: light
    name: Light(s)
    required: true
  target_brightness:
    selector:
      number:
        min: 1
        max: 100
    name: Target brightness (%)
    default: 1
    required: true
  color_temperature:
    selector:
      color_temp:
        unit: kelvin
        min: 1500
        max: 7000
    name: Color temperature
    required: true
    default: 2200
  transition_rate:
    selector:
      number:
        min: 1
        max: 600
    name: Transition rate
    description: Transition rate, scaled by 'input_number.timescale'
    required: true
    default: 100
description: Dims the target light(s) if they are on - Kelvin setpoint.
icon: mdi:lightbulb-auto-outline
mode: parallel
max: 15
  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 6 months ago (2 children)

    Got a little help from CGPT so it might not be perfect, but this seems to work from my limited testing:

    triggers:
      - trigger: state
        entity_id:
          - input_boolean.ups_power
    conditions: []
    actions:
      - choose:
          - conditions:
              - condition: state
                entity_id: input_boolean.ups_power
                state:
                  - "on"
            sequence:
              - action: scene.create
                data:
                  scene_id: light_states_backup
                  snapshot_entities: |
                    {{ states.light | map(attribute='entity_id') | list }}
          - conditions:
              - condition: state
                entity_id: input_boolean.ups_power
                state:
                  - "off"
            sequence:
              - action: scene.turn_on
                target:
                  entity_id: scene.light_states_backup
                data: {}
              - delay:
                  hours: 0
                  minutes: 0
                  seconds: 10
                  milliseconds: 0
              - action: scene.delete
                data:
                  entity_id: scene.light_states_backup
    mode: single
    

    I've only tested it by toggling the UPS boolean manually and not actually cutting the power, so I'm probably going to need to add a delay, or a retry loop or something to make sure the scene applies consistently but so far so good! Thanks for the inspiration.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 6 months ago (1 child)

    snapshot_entities: | {{ states.light | map(attribute='entity_id') | list }}

    This is the only part I'm unsure about, seems like a clunky way to get all of the lights, but if only certain ones are causing problems, I'd just put the problem ones here as a list (or create a light group in HA and only call that group

    Also, input_boolean.ups_power feels like ChatGPT is assuming you have a helper for the current power status, but I would just call directly from the UPS entity. You should be able to clean this up in the GUI.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 6 months ago

    That first line is what CGPT helped me with. I wanted something that I don't need to modify when I add or remove lights, so this just gets everything. Ideally I'd just get the lights that don't have the power restore feature but most of my lights go via Hue and that doesn't expose the feature to HA at all.

    The input_boolean is a thing I already had setup. The UPS fires a webhook event when it goes in and out of battery mode and there's a separate automation that switches the helper based on those.

  • source
  • parent