Force Zigbee2Mqtt to include delay between commands

Hi, I have a Switch that apparently has an firmware limitation that some of the packages received are acked to the Z2M but not executed on the firmware level.

Example: light.turn_on 6 switches at a time, one or two switches will fail to turn on, but the state will go to ON since the switch actually responded/ack the command

If I have an script that sets each channel with a delay of 100ms between them, it works fine. But having all the light logic to include this delay would be a lot of work.
Is there a way to force Z2M to buffer the outgoing packages with a specific time between them so that the device would not be flooder?

If these are separate switches, why not create a group in Z2M and see if this fixes the problem?

Sending multiple commands at once & having some of them be dropped is a relatively common issue, even with groups created in HA.
Using a Z2M group mitigates against this because only a single command is sent from HA to Z2M.

In this case all commanda are acked by the device, so it wasnt dropped, but I agree thats possible in a bad network.

Z2M Groups would totally work, unfortunately most tuya-based switches doesnt support. Which is the case ( Only the first channel can be added to a group )