Presets or intermediate states in cover integration

Feature Requests
1

Most cover devices (window blinds, shutters, curtains) daily used between the physical end positions (closed: 0, opened: 100), for example: daytime: 80, night: 3
Would be good, if this 2 states (or any number of presets) will be implemented in the cover entity itself and called like:

cover.to_daytime
data:
  entity_id: all

or

cover.set_preset
data:
  entity_id: all
  preset: daytime

If using states, they can be read back, and used for dynamic icons, etc., but the number fixed to 2. Presets can by more, but much difficult to report back the actual one from the physical shutter position.

Now, I can achieve this usecase with a dosen of scenes, scripts, automations, templates and UI buttons and keep they config parameters in sync. Using presets should be much easier.

2

Dozens?

You can do it with two scenes, one for day, one for night,

3

2 scenes for each shutters on the house, and some others to group them in the same combination as the covers grouped. It is possible, but harder to maintain when something changes.

4

You said:

That’s two scenes to set all shutters.

5

That was an example. If I wrote entity_id: some_shutter then I can simply use cover.set_cover_position. But what if it’s a group of some or all shutters, and the required position is different on each (because of physical differences)?

6

Just want to nudge this thread… the OP has a point. Many shutters/rollers support presets. Don’t know how hard it would be but if this passed through to the card it would be extremely useful. Even if the preset was set and labeled in HA as a % but could be addressed globally for a group of shades, either by name (ideally) or by sequence number. ie set all skylight to vent or set all shutters to closed but venting (usually between 10-15% open depending on the height of the shutter)