Oh, I see. It seems like the obvious solution to that, from a zwave protocol perspective, is multicast. I don’t think I’ve ever seen a device like a switch implement the ability to send multicast messages, but I don’t see why you couldn’t.
For clarification to a non-tech guy, there are two kinds of zwave messages: unicast and multicast.
A unicast message has one sender and one recipient.
A multicast message has one sender and multiple recipients.
So currently, if I set up my inovelli switch with node id 1 to be associated with nodes 2, 3, 4 and 5, when I do something on the switch, it has to send 4 separate zwave messages, one after the other. Each of the four other nodes “hears” all four messages, but doesn’t “listen” to 3 of them because they’re addressed to someone else.
Sending a single multicast message would allow the switch to send one message with all four nodes listed as recipients, so they’d all “listen” when they “hear” the message, and all turn on/off/whatever.
You’re in a room with your two children, Alice and Bob. You want them to clean up the toys.
Unicast is saying:
“Alice, go clean up the toys.”
“Bob, go clean up the toys.”
Multicast is saying:
“Alice and Bob, go clean up the toys.”
It seems like the bigger challenge to this sort of direct zwave control is availability of zwave smart bulbs. Yours is pretty much the only one I’m aware of on the market, while zigbee bulbs are widespread.