List of states in an automation trigger? Is this valid syntax?

Ok, found what I was looking for. Version 0.112 introduced multiple states and entities for automations, but for conditions rather than triggers. Thus, the syntax above may not work as expected, if at all.

But I think it should be possible to achieve a similar result with a combination of a trigger omitting the to: clause and putting the list of states in a condition below…