Feature Request: cleaner @state_trigger('True or ... ')

This syntax is a bit hacky looking and hard for new users to follow:

@state_trigger('True or binary_sensor.dark')

There’s no reason to make the above syntax NOT work, but think a convenience decorator for this use pattern might be beneficial. Something like this:

@state_change_trigger('binary_sensor.dark')

@state_change_trigger([
  'binary_sensor.dark',
  'binary_sensor.motion'
])

Though, naming things is hard. There’s probably something better than state_change_trigger.

[craigbarratt]

Ok, that’s two votes for

@state_trigger(my_list_of_entities)

so let me look at doing that. I was also thinking about using a list of strings for multiple expressions, that are ored together (ie, anyone being true will trigger the function).

It would be possible to make both forms work. A single string argument state variable (ie, no expression and no list) could be detected and treated as trigger on any change. And a list of strings, each of which could be an expression or a state variable name meaning any change, would be logically ored together.

[dlashua]

I tested @state_trigger() and task.wait_until() with lists, strings, combinations of lists and strings, as well as the old “True or …” functionality. Everything worked as expected.

THANKS!