Connection Reset interacting with Hue about homebridge HOT 5 CLOSED

OK - I tracked this one down. It's rate-limiting on the hub. I've got a lot of bulbs (~40 on each hub). After returning the status for the first 16 bulbs, the hub kills the connection - which causes the error above.

IIRC you can return the state for all bulbs in a single call, and then iterate.... will look to changing that, and doing a PR.

from homebridge.

I have a PR in progress for this if you can wait a day. Nevermind my PR is for rate limiting the requests not the status updates. I might not have time today but I can work on that too if someone else doesn't beat me to it.

from homebridge.

IIRC you can return the state for all bulbs in a single call, and then iterate.... will look to changing that, and doing a PR.

I'd love to see how we can implement this in an Async world and one in which HomeKit asks individually. Wink also can fetch everything at once. In fact, the lib being used doesn't even use an individual endpoint, it just grabs everything and cherry picks the device, lol.

While API limits aren't an issue, it just feels gross.

I just wasn't sure about how to really mange this outside of just cacheing and ACCIDENTALLY returning from the cache because of latent requests, lol.

from homebridge.

I have a plan for grouping requests for changing scenes but it will take a while to do it right. For getting the state of all bulbs node-hue-api has a fullState() call that is expensive but less expensive than getting the state of all 40 bulbs individually.

from homebridge.

Also for the rate limiting I am using the excellent bottleneck module if someone else is working an a PR for this.

from homebridge.