Make !input selection in variables depnding on another value?

Configuration Blueprints
1

I have a switch and depending on the time of the day I want to switch on and control different lights. To make my life easier, I want to define a target_lights variable that is filled by only one of three inputs. The idea so far I came up with looks like this:

blueprint:
  name: my automation
  domain: automation
  input:
    target_lights_day_mode_on:
      name: Lights ON Day
      description: The lights to turn on.
      selector:
        target:
          entity:
            domain: light
    target_lights_night_mode_on:
      name: Lights ON Night
      description: The lights to turn on.
      selector:
        target:
          entity:
            domain: light
    target_lights_evening_mode_on:
      name: Lights ON Evening
      description: The lights to turn on.
      selector:
        target:
          entity:
            domain: light

defining the variables, this is the tricky part I don’t understand if even possible:

action:
  - variables:
      target_lights: >-
        {% if states('input_text.day_mode')== 'day' %} !input target_lights_day_mode_on
        {% elif states('input_text.day_mode')== 'night' %} !input target_lights_night_mode_on
        {% elif states('input_text.day_mode')== 'evening' %} !input target_lights_evening_mode_on
        {% endif %}

this goes then into different sequences that look like this:

        sequence:
          - service: light.turn_on
            data:
              brightness_pct: 80
              color_temp_kelvin: 2700
            target: "{{target_lights}}"

but as you can see it would be super handy if I could concentrat the three different inputs into 1 variable because that would spare me of writing the same seqeunce 3 times each for the different times of a day

2

You are writing a blueprint, so think like a blueprint, not like an automation.
If you were writing an automation you would want it to do everything and mash it all together complicated as hell.
If you are building a BP you are designing for re-use, so make it work logically for one of the data sets, and just spool up 3 of them that can each run a different dataset at a different time each day. Don’t repeat your code in your code, write it once and use the Blueprint 3 times…

3

Thanks, yeah good input! I just tried to minimize the amount of automations that I have to keep track off. There seems to be a tradeoff either way. Anyway, I kind of found a way around if someone is interested.
Instead of dynamical defining the Variables, I dynamically set which variable to use just to give you some snippets:

action:
  - variables:
      current_mode: "{{states('input_text.day_mode')}}"
      control_lights_day_mode_var: !input control_lights_day_mode
      control_lights_evening_mode_var: input control_lights_evening_mode
      control_lights_night_mode_var: !input control_lights_night_mode

[..... some more code in between .....]

        sequence:
          - service: light.turn_on
            target: >-
              {% if current_mode == 'day' %} {{control_lights_day_mode_var}}
              {% elif current_mode == 'evening' %} {{control_lights_evening_mode_var}}
              {% elif current_mode == 'night' %} {{control_lights_night_mode_var}}
              {% else %} {{control_lights_day_mode_var}}
              {% endif %}