Understanding Command Processing Differences in Homey Pro

I’ve been experimenting with my Homey Pro 2023 setup, which currently manages 146 devices—mostly Z-Wave, with a mix of Zigbee and Wi-Fi. I recently created a flow for night mode, which turns off all interior lights except the exterior ones. This involves controlling 26 lights using Fibaro Dimmer 2 and Fibaro Double Switch 2 devices.

Initially, I tried sending all the commands simultaneously, but several lights would time out and fail to turn off. To resolve this, I grouped the lights by floor and added delays between each group. This approach worked perfectly! However, I noticed something puzzling when setting the “forced brightness” parameter for all 24 Fibaro Dimmer 2 devices. In this case, sending all commands in parallel worked flawlessly without any issues.

This made me wonder: why is there such a significant difference in how these commands are processed? Turning off the lights seems more complex than setting a brightness parameter, even though both involve multiple devices. I’m curious to understand the underlying mechanics of how Homey handles these commands and if there’s a way to optimize the process further.

It’s fascinating to see how different operations can have such varied outcomes, even when dealing with the same types of devices. I’d love to hear if others have encountered similar experiences or have insights into this behavior. Happy to share more details or discuss further!