Replies: 1 comment
-
|
The low performance of the ZigBee network is a known issue: this protocol was not designed for high-performance color streaming, and each color update requires two packets per lamp, which only makes things worse. That’s why the optimized Philips Hue communication really shines here. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have six Zigbee lights (from AliExpress) connected to a Philips Hue Bridge, so I cannot use the Entertainment API. I would like to control these lights using HyperHDR. Everything works well when controlling a single light, but as soon as I use more than one light, color updates become delayed — the more lights I add, the worse the delay gets.
I’m using the Hyperion Android grabber. If I reduce the update frequency, the delay becomes smaller. I suspect the problem is caused by using the REST API, where each request can control only one light. This results in many REST calls being sent to the bridge, which then becomes overloaded and stops responding smoothly.
I have tried various settings, but I haven’t been able to solve this issue.
Is there any way to limit the number of REST requests sent per second?
For example, I would like to enforce something like “maximum 1 update per light per second.”
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions