Skip to content
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

ECONNRESET when saving a scene with more than 8 lights #89

Open
bendavis78 opened this issue Feb 20, 2018 · 7 comments
Open

ECONNRESET when saving a scene with more than 8 lights #89

bendavis78 opened this issue Feb 20, 2018 · 7 comments

Comments

@bendavis78
Copy link

For some reason, when I try to save a scene with more than 8 lights using client.scenes.save(scene), I get the following error:

Error: Huejay: read ECONNRESET
    at getHttpClient.request.then.catch.error (/home/ben/hue-manager/node_modules/huejay/lib/Transport.js:106:15)
    at process._tickCallback (internal/process/next_tick.js:103:7)
@quistuipater
Copy link

quistuipater commented Mar 25, 2018

I'm seeing the same thing with 7 Hue lights. I'm using Node-RED with HueMagic and switching all of the lights on or off together results in a random light node or two displaying "input error" on the canvas and debug reports:

Error: Huejay: connect ECONNRESET 192.168.0.101:80 at getHttpClient.request.then.catch.error (/root/.node-red/node_modules/huejay/lib/Transport.js:106:15) at at process._tickCallback (internal/process/next_tick.js:188:7)

I think the problem lies in the Hue hub ... ask it to do too many operations at once and it borks. I've got a first generation hub which may be more prone to this problem.

@sqmk
Copy link
Owner

sqmk commented Mar 26, 2018

Yeah, this is most certainly a hub limitation in which it can't handle a high number of requests in a short period of time. There is a ticket to handle throttling the number of requests from Huejay to the bridge to help alleviate this issue.

@nikolovskimilos
Copy link

Any progress on this?

@RogierQ
Copy link

RogierQ commented Sep 14, 2018

ok same thing here. want to send an all off to all lights but dont know another way then send to every group individually, would be nice if there is a all lights node

@hollyhudson
Copy link

hollyhudson commented Oct 29, 2018

I am also having this problem, but I've found a (somewhat silly) workaround. I'm attaching an image of my "All Off" flow (triggered by clicking a switch in the iOS Home app, so the command comes from a homekit node). I'm happy to also post the json if anyone wants it. I just added trigger nodes that stagger the message going out to the lightbulbs, while also dividing the bulbs into groups, so only a few are ever sent commands at once, and that command is repeated four times to catch any lights that were missed. (The "only off" nodes are to send on: false commands only so my switches act like buttons.)

I also find it's necessary to set Deploy to deploy modified nodes only to keep the Hue hub from choking. Additionally, disabling all flows with Hue lights except the one you're editing also helps. So.. yeah.. it would probably be nice to have a better solution. I do have an LIFX bulb, and that one doesn't have a hub, it just hops right onto the wifi. And it is rock solid. It's pricier than the Hues (and the Ikea Tradfri bulbs that are also connected to my Hue hub), but I guess you get what you pay for.

screen shot 2018-10-28 at 22 04 31

@bausi2k
Copy link

bausi2k commented Jun 4, 2020

Any news on that?

@csmende
Copy link

csmende commented Jun 9, 2020

Would love to help test if someone has a solution. Number of devices is only going up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants