[Feature Request] Automation UI list Entity States for Blueprints - we should not need to know / manually type them

Feature Requests
1

When creating Automations using Blueprints we are required to ‘know’ the state we want to trigger on. We must know all possible states (or try to find them, which can be difficult too), then manually type it in (prone to human error).

The system knows all possible states from the device/entity definitions… HA should simply provide them in a drop-down so the user can select the state… this would save a ton of time and avoid problems

2

Like this?

image
image998×877 20.7 KB

But no, it does not know all states an entity can be.

3

I’m not sure exactly how the UI provides the lists it does provide. Even providing some on-screen guidance during the automation/blueprint creation would help (this entity is expecting input like this, ‘XYZ’)

Blueprints seem the most challenging as the 20ish BPs I’d tried, none provide a drop-down list.

4

I have never used a blueprint. But perhaps that is different.
UI with automations and scripts present a dropdown when it knows the possible states

5

You get a dropdown if:

  • the entity is from a domain that has known states (like climate, binary_sensor, fan, etc)

or

  • the entity is a sensor that has device_class enum, and the list of known states are attached as attribute options

If a text-based sensor has a list of possible options, it’s ideally up to the integration to provide those as an enum so that the frontend can show the options (and even translate them).

1 Like
6

Does Blueprints leverage this, or just the Automations native UI?

7

When you say “blueprints”, what specific selector type are you referring to?

Like a state trigger or state condition should work like this in a blueprint.