-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please make Rate Limiting configurable #234
Comments
The issue (also) seems to be, that although a client-library build on top of node-hue-api may be issuing custom RateLimits as a parameter of the createLocal function, but the RateLimits for Lights and Groups are additionally hard-coded in the Groups.js and Lights.js folder in the lib/api folder. Or maybe you could hint us towards the proper procedure on how to pass down custom RateLimit to the api-interface... |
The rate limits that are hard coded are those that Signify state in the documentation as to being the requirements to ensure access complies to their best practices. Whilst it might be possible to push the bridge harder and faster, it can and will eventually break the responsiveness for the end user or other integrations. It is would not particularly too difficult to bubble these up to being controllable via an instantiation of the API, I don't believe going against the recommendations of the manufacturer in this regard as it does not take much to overload these bridges. |
Hi @peter-murray, thank you for your response. |
Dear developer,
I have several groups and I know even with a smaller waiting time btw. group commands it is working for me and is much more performant (faster) when switching states of multiple lights.
To get this feature officially.. can you please make the Rate Limiting configurable?
Many many thanks for your support!
The text was updated successfully, but these errors were encountered: