Why not allow a list of states in an automation trigger?

Archive Month of "What the heck?!" (2020)
1

Just realized, that while automation conditions allow multiple states and entities for automations since version 0.112, this doesn’t seem to be the case for triggers.

But where’s the difference? Couldn’t triggers allow lists of entities and/or lists of states as well as conditions? Something like this?

  - trigger:
    - entity_id:
        - sensor.window_1_state
        - sensor.window_2_state
      platform: state
      to:
        - open
        - tilted

Am I missing some logical or technical caveat or is this just not implemented yet?

2

This is already possible and implemented. Multiple entities are accepted on both for triggers, conditions and the to state can contain a list of possible items to match (so does the from statement).

The exact example you wrote works.