Hue lights misbehaving

[cweitkamp (Christoph Weitkamp)]

Hi all,

@Dim

One possible root-cause for some of the lights not going ON would be that you are “saturating” the communications in step (5) above (14 commands executed simultaneously). Maybe the Binding and/or the Bridge are having trouble handling this.

Yes, that is exactly the root-cause.

Hue binding - mass update not always working

Hi Dennis, A quote from the Hue API documentation: We can’t send commands to the lights too fast. If you stick to around 10 commands per second to the /lights resource as maximum you should be fine. We have to wait for the group feature to be implemented in the binding or use a workaround till then.

As a general guideline we always recommend to our developers to stay at roughly 10 commands per second to the /lights resource with a 100ms gap between each API call. For /groups commands you should keep to a maximum of 1 per second.

Table 1: Average latency for various hue API messages

zigbee messages per hue API command	parameters used in body of hue API command (example)	average latency
1	brightness	55 ms
2	brightness + color	95 ms
3	brightness + color + on	125 ms

See Hue System Performance (login required).