This is a very nice contrib node, thank you. I use it to control lights, heat, water heater etc... at our cottage. It has however (I believe) a serious issue that causes my entire node-red app to eventually lock up.
It works marvelously so long as it has exclusive and unfettered access to the eWelink account. When the eWelink account is logged into from another source (like a cell phone on the way to the cottage to turn the lights on) it starts to behave badly.
When this occurs the nodes turn to yellow (connecting) and stay that way. Eventually, the computer CPU usage goes up 15 or 20 times normal and RAM usage is maxed out, eventually causing node-red to lock up. Since it is remote I rely on access via VNC and that will not work so I have to go to the device and power cycle it.
I have caught node-red-log messages when the problem starts to escalate that indicate the errors causing problems have to do with ewelink and mentions things about unmet promises.
Would you please look at node-red-contrib-ewelink behavior when the eWelink account is accessed from an alternate source?
EDIT: It seems issue #84 is very similar to what I am experiencing.
EDIT: Otto I just noticed a reply you provided back in December about "Unfortunately multiple sessions are not supported. This was the reason of implementing a global connection. " I suspect this is part of (if not, the) problem. If this cannot be remedied (and I'm hoping it can be) then some work should be probably be done to prevent ewelink from driving node-red into a melt down due to the unmet promises issue. I'd really hate to have to remove the ewelink nodes.
Thanks
st
This is a very nice contrib node, thank you. I use it to control lights, heat, water heater etc... at our cottage. It has however (I believe) a serious issue that causes my entire node-red app to eventually lock up.
It works marvelously so long as it has exclusive and unfettered access to the eWelink account. When the eWelink account is logged into from another source (like a cell phone on the way to the cottage to turn the lights on) it starts to behave badly.
When this occurs the nodes turn to yellow (connecting) and stay that way. Eventually, the computer CPU usage goes up 15 or 20 times normal and RAM usage is maxed out, eventually causing node-red to lock up. Since it is remote I rely on access via VNC and that will not work so I have to go to the device and power cycle it.
I have caught node-red-log messages when the problem starts to escalate that indicate the errors causing problems have to do with ewelink and mentions things about unmet promises.
Would you please look at node-red-contrib-ewelink behavior when the eWelink account is accessed from an alternate source?
EDIT: It seems issue #84 is very similar to what I am experiencing. EDIT: Otto I just noticed a reply you provided back in December about "Unfortunately multiple sessions are not supported. This was the reason of implementing a global connection. " I suspect this is part of (if not, the) problem. If this cannot be remedied (and I'm hoping it can be) then some work should be probably be done to prevent ewelink from driving node-red into a melt down due to the unmet promises issue. I'd really hate to have to remove the ewelink nodes. Thanks st