Ability to hide configuration options in Blueprints

Feature Requests
, , ,
1

Some blueprints can get really complex because all options will always be presented to the user. This can become confusing and overwhelming as features are added.
I would imagine that some users get lost in what is and isnā€™t configured or even configurable.

It would be great to be able to hide parts of the automationā€™s configuration based on the options that are selected.

A simple example:
This would be the configuration of a blueprint that turns a light on.

Currently it would look something like this:

  • Target selector
  • Brightness selector
  • Color selector
  • Transition selector
  • ā€¦

It would be more practical and user friendly as follows:

  • Select target light
  • Tick option ā€˜Set brightnessā€™ > Brightness selector is shown
  • Tick option ā€˜Set colorā€™ > Color selector is shown
  • Tick option ā€˜Set transitionā€™ > Transition selector is shown
  • ā€¦
2

If you think itā€™s a good idea, you should vote for it. I didā€¦
Suggested Reading:
Feature Request Guidelines :notebook_with_decorative_cover: - Feature Requests - Home Assistant Community.

1 Like
3

Desperatedly needed feature. I have so many optional configuration options in my blueprinrs, which I would love to hide if eg a boolean selector is false.

1 Like
4

Either some kind of nesting on the !input statements would work or even just a hide checkbox mark that the user themselves could hide what they donā€™t want to see would be great. (forcing items that do not have a value to stay visible. Default ā€œā€ would still be a value).

1 Like
5

A simple collapsible section like in Markdown would already be great, but ideally I envision this to be developer manageable first, user manageable second.

For example:
My blueprint :bulb: The Everything Light - Trigger a light any way and turn it on in any way currently has 4 operating modes, each with their own settings.
As the developer, it would be great to let it only show the options of the mode itā€™s configured to run in.

In second order, a user should have the choice to collapse different option sections should they feel the need.

6

I have the same problem with mt Aqara Cube BPā€™s. I ended up using emojiā€™s in different sections to help guide the user, but itā€™s a mess for sure.

1 Like