Closed FredBlo closed 1 year ago
Thank you so much for doing this!
Thank you for your work! I tested it and it works like charme! @Foddy can you please merge this PR soon?
@Foddy this is really necessary ,please can you consider giving @FredBlo merging rights since he contributes a lot lately. It would help everybody
Context : HUEMagic becomes more often unusable
Based on what I read, it seems HUE has became more and more strict in what it accepts in terms of external API call rates. Where the bridge easily accepted many calls per second before, it now rejects them more frequently. Official HUE dev documentation now mentions a maximum of 4 calls per second (but even more strict for calls to groups which are limited to 1 call / second...) HUEMagic already handled a retry but :
Error requesting info from the bridge. Reconnect in some secs. undefined
. This was caused when HUEMagic polled the bridge to ensure connection was still OK at a moment when the bridge was overloaded (err=429)Because of this, most of us were not able to enjoy HUEMagic nodes :-(
What did I change ?
Additional info : merge of other
This pull request also merged #390 from @traverseda and #381 from @Travelbacon, which corrected -very successfully- bugs #375, #374, #377 and #378. Since then other group issues were reported which should also be solved since I think these are actually the same... (such as #400)
What you need to do / change ?
I strongly recommend to configure your HUEMagic bridge node using a single 'worker'. Setting more than 1 will always -logically- worsen the overload effect on the bridge. If you want to use it from now (not waiting for Foddy to merge & publish it), this is possible by installing it manually using command
npm install git+https://github.com/fredblo/node-red-contrib-huemagic.git