# Lights on/off at once instead of one after another

**URL:** <https://community.homey.app/t/lights-on-off-at-once-instead-of-one-after-another/27143>\
**Category:** Flows\
**Tags:** zigbee, homeyscript\
**Created:** [March 14, 2020, 8:30pm UTC](https://community.homey.app/t/lights-on-off-at-once-instead-of-one-after-another/27143 "2020-03-14T20:30:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 15, 2020, 7:40am UTC](https://community.homey.app/t/lights-on-off-at-once-instead-of-one-after-another/27143/5 "2020-03-15T07:40:06Z")

</div>

> [@Shakesbeard](#):
>
> This is most likely caused by either the hue app or might be a limitation of the hue api.

Not really, because he states it also happens with the Hue Zigbee app, in which case there’s no Hue bridge/API at all.

The problem is two-fold:

- Homey has problems executing multiple action cards at once, especially when those cards involve switching Zigbee or Z-Wave devices (that’s why you’ll see people using workarounds like adding delays)
- Homey doesn’t support Zigbee grouping, where you can add multiple Zigbee devices to a single Zigbee group (which allows you to switch all of those devices using a single Zigbee command).

Because the Hue bridge _does_ support grouping, it works when you switch an entire group using the Hue bridge app.

---

_[View the full topic](https://community.homey.app/t/lights-on-off-at-once-instead-of-one-after-another/27143)._