search

Foddy / node-red-contrib-huemagic

Philips Hue node to control bridges, lights, groups, motion sensors, temperature sensors and Lux sensors using Node-RED.
https://flows.nodered.org/node/node-red-contrib-huemagic
Apache License 2.0
201 stars 67 forks source link

Error when sending multiple messages to bulb in short period of time #404

Open hazymat opened 1 year ago

hazymat commented 1 year ago

Describe the bug When sending messages at the rate of more than 2 or 3 per second to a bulb, the node returns an error. This is since updating to latest version.

If I insert a delay node to limit to approx 2 messages per second, the error goes away, however it takes a long time to turn lights on sometimes, and I find it takes longer when there are multiple bulbs turned on all at the same time. The bulbs no longer come on at the same time, and it looks very strange when triggering a scene which turns 3-4 different bulbs to different settings. This was not an issue previously.

Screenshots image

Please complete the following information:

FredBlo commented 1 year ago

Fyi, I published a pull request #409 which improves the way the bridge overload is handled (following +/- recent changes made to the HUE bridge at this level, aka Error 429)... So if you want to give a try, you can using this one too (installable form FredBlo fork npm install git+https://github.com/fredblo/node-red-contrib-huemagic.git :-) )

J-T-W commented 1 year ago

I'm new to HueMagic and started with the -fork 4.2.3 version. My goal was to have a series of 8 lights run a custom set of steps via the Magic node, and as it looks like you have to pair a single Magic/Light node to get randomization across the lights, I did that. I have a 5 second delay on each step with up to a 3 second transition, but I do see a lot of the 429 errors returned.