You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to turn on/of multiple lights simultaneously, but they only turn on/off one after one.
Is that a result of the preconfigured rate limits (maxConcurrent 1, wait 60 for lights)? If so, why don't you limit the rates per light (device)? or is there an other way to solve this?
Ty
The text was updated successfully, but these errors were encountered:
It is primarily a limitation of the hub, as it will transform that type of request from REST into Zigbee messages to each light, resulting in this behaviour. The concurrency controls are there to be compliant with the bridge limits.
If you want to do this with a number of lights, use a group or zone these are properly sent to all the target lights simultaneously.
There was an issue with the rate limits being swapped between groups and lights, which I have just resolved meaning the limit is now correctly set to once per 60ms instead of the group limits of once per second. This has been released in 5.0.0-beta.11.
That said still the above usage of groups/zones is the recommended way to target more than one light changing state simultaneously.
Hi!
I am trying to turn on/of multiple lights simultaneously, but they only turn on/off one after one.
Is that a result of the preconfigured rate limits (maxConcurrent 1, wait 60 for lights)? If so, why don't you limit the rates per light (device)? or is there an other way to solve this?
Ty
The text was updated successfully, but these errors were encountered: