When sending an action through an automation - you target the group entity rather than the individuals. So for instance you want to turn off the group of lights, you just select that as your target. It generates a new entity to send commands to. I even nest groups in groups - for example here is my all lights group:
== 4 days later ==
EDIT:
I misread the title of this thread. As davinci pointed out below, his question was about z-wave / zwavejs2mqtt, not zigbee / zigbee2mqtt.
So what I said here was 100% off-topic.
=== original post === @BlackCatPeanut - While you could group lights in HA, and manage them together, the commands in the background, via zigbee mesh, would still be individual.
Back to the topic, @davinci , I believe the “groups” setup is right there in the top menu bar… would this help?
Maybe @davinci could help us test both… There should be no conflict if you have both… Just to be sure we are not missing anything.
It’ll be 10 turn on events. I use multicast for this. The group association is limited and based on your hardware in zwave. Some hardware can’t handle it. Mutlicast works regardless.
Here’s a script I wrote. Probably could be turned into a blueprint but I haven’t done it.
If you have all ‘normal’ switches and lights. The script ends up making 2 calls, 1 for lights, 1 for switches. It’s a broadcast, so all lights will turn on at the same time and all switches will turn on at the same time. Sometimes you’ll get errors, but you can ignore them. Either way, they all turn on and off at the same time. No lag or ‘waterfall’ effect.
I run the switches second because the lights take time to ramp up and it makes them look like they all turn on or off at the same time.