Enhance Blueprint input sections with conditions

[chrismanivong]

It would be nice to have sections either collapsing or even hiding, if a specific condition - mainly by other inputs - is met.

For e.g.:
So there could be an input for a "working" mode. Based on the user's decision to use mode "abc" or "xyz", some sections may appear or being hidden, or collapsed or uncollapsed.

This would be very helpful on top of @karwosts contributions, to make the usage of blueprints more convienent.

[mmoulton]

For me, this basically comes down to allowing the input: section to support templates as values. Though I'm sure this is much more complex than it might seem.

If this was possible, you could collapse a nested input with something like: collapse: "{{ input.some_input_id == 'some value' }}"

Beyond that, it would enable highly dynamic blueprint interfaces to be created. I have several advanced lighting / area automation blueprints that work great if you configure them precisely. With dynamic values in blueprint inputs, I could do something like this:

  input:

    area:
      name: Select Area
      selector:
        area: {}

    light_entity:
      name: Select Light
      default: ""
      selector:
        entity:
          include_entities: "{{ GET LIST OF LIGHT ENTITIES WITHIN SELECTED input.area }}"
          domain: light

    scene_entity:
      name: Scene Selector Entity
      default: ""
      selector:
        entity:
          include_entities: "{{ GET LIST OF INPUT SELECT ENTITIES WITHIN SELECTED input.area }}"
          domain: input_select

    selected_scene:
      name: Scene
      default: ""
      selector:
        attribute:
          entity_id: "{{ input.scene_entity }}"

As HA is looking to really cleanup the overall UX, I think a feature like this would really make it far easier for Blueprint developers to make complex interfaces that are very user friendly, and robust.

[rumblefishi]

I would love to see this feature implemented!

As a frequent user of blueprints from the Home Assistant exchange, I regularly encounter complex blueprints with numerous input fields. Many of these fields include descriptions like "Only relevant if Option A was selected above" or "Only applicable when Option B is enabled."

From a user experience perspective, this makes the configuration interface unnecessarily cluttered and confusing, as I'm presented with many fields that aren't actually relevant to my specific use case.

The ideal solution would be to dynamically hide irrelevant fields based on previous selections. This would make complex blueprints much more approachable and user-friendly, especially for users who aren't deeply familiar with YAML or automation logic.

This feature would significantly improve the usability of advanced blueprints while maintaining their powerful flexibility.