# Flows And Devices

**URL:** <https://community.homey.app/t/flows-and-devices/127808>\
**Category:** Questions & Help\
**Created:** [January 15, 2025, 9:36am UTC](https://community.homey.app/t/flows-and-devices/127808 "2025-01-15T09:36:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 15, 2025, 9:58pm UTC](https://community.homey.app/t/flows-and-devices/127808/2 "2025-01-15T21:58:05Z")

</div>

ln theory it can be done with one flow, BUT,  
Homey does a bad job switching over X devices all at once.  
It also depends on brands and protocols, and general signal interference at your location.

Homey sends all commands at once, asynchronously, which often results in one or more _random_ devices not responding.

Workarounds:

1. In standard flows, fire the maximum number of action cards at once, like 5 devices (_you’ll have to test what the safe maximum number should be_)  
The next 5 action cards should be fired delayed by 1 s  
The next 5 action cards should be fired delayed by 2 s  
… and so on…  
But, this is of course very ugly when you’d like 50 lights to turn on/off at once.

2. In advanced flows, you can daisy chain the action cards. This way, each card is fired in sequence with a very slight delay:  

3. Using additional apps:  
Group the devices, to have one device turn all group members on/off.  
The commands are fired sequentially automatically.  
You can use:  
A. An [advanced virtual device](https://community.homey.app/t/app-pro-advanced-virtual-device-device-capabilities-app-with-unique-text-status-indicator/68198) by the Device Capabilities app  
B. A [group device](https://community.homey.app/t/3168) by the \< Group \> app

---

_[View the full topic](https://community.homey.app/t/flows-and-devices/127808)._