Add multiple entities as trigger

[N1c093]

Hello,

first of all I really like the new blueprint feature. It’s a great way to exchange new ideas/automation to each other.

Currently I try to create my first blueprint and share it with you.

I like to use this trigger in an blueprint. The user should be able to select multiple entities in the selector. In this example “media_player.badezimmer” and “media_player.wohnzimmer”

  trigger:
  - platform: numeric_state
    entity_id:
    - media_player.badezimmer
    - media_player.wohnzimmer
    attribute: volume_level
    above: '0.37'

In general it seems to be impossible to add multiple entities via one entity-selector in a blueprint.
Is there currently an solution to add an selector which allow the user to add multiple entities? For the target this is possible via the target-selector.

Thanks in advance

Nico

[Noblewolf (Josh)]

I’m looking for the same thing. Found out you can’t use target in the trigger.

Blueprint is not valid if there are options in the trigger

Just published my blueprint with this in the user instructions

Set light(s) to default color temperature and brightness when they turn on

Purpose This Blueprint allows you to select 1+ lights/light groups and their default brightness and color temperature. It also work for bulbs that only have brightness and do not have a color temperature option. Why This is useful for lights that do not have a default brightness/color temperature for when they turn on (like Sengled zigbee bulbs) and instead turn on to the state they were when they were turned off. So, if you set your lights at 10% in the evening then turned them off, they wil…

[N1c093]

Thank you for your reply.

I found a workaround for my problem. You can use a comma separated list for multiple entities as a trigger. As you can see here: Media Player - Volume limit

The only downside is, that you can’t use a selector for it.

[Noblewolf (Josh)]

Thank you! I’ll note the comma suggestion when I publish the blueprint.

[N1c093]

I hope this workaround will work for your blueprint as well, but it looks pretty simular.

Hopefully they will add an selector for multiple entities soon.

[123 (Taras)]

@N1c093

workaround … use a comma separated list

I’ve seen this used elsewhere and it’s a very ‘user-unfriendly’ workaround.

The user must type the entities from memory. They can peek at the selector’s menu for reference but must type the entities without introducing spelling errors. If they make the mistake of selecting an entity from the menu, it overwrites everything they may have already typed. Everything about this workaround is opposite to the intended convenience of using a selector.

A multi-select Entity Selector is sorely needed.

[cloak]

See my reply here. May be of use or may be able to be modified.