Or not bother calling scripts. The scripts are light.turn_(on|off), which can be a single action.
Push a button and turn a light on or off. As things go, you add a few more triggers – like motion or day/night change and now you have an automation for each. Do that for a few rooms and things multiply – which was what the original post was about.
The scripts are not really making things simpler. As the OP pointed out, combine triggers and use trigger ID, and then use groups, labels (or config) to avoid duplicating for each room.
Is there a reason why passing a list of device id should not be possible using trigger variables? That would help a lot.
Then those pesky devices:
variables:
config:
# Bedroom Hallway
- motions:
- binary_sensor.bedroom_hallway_occupancy_sensors
devices:
- 359bc5a5f510d587696d3042b560c8b7
I have many automations that use a config like that, but I’ve been moving those to labels or groups. It’s unfortunate that (apparently) the Zigbee integration doesn’t create the event.* entities because you could use those w/o having to deal with excluding and including a device.
Anyway, in this case I’d still prefer labeling the devices instead of hard-coding device IDs.