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

Restarts node-red #2

Open
nomadbeni opened this issue Nov 9, 2017 · 17 comments
Open

Restarts node-red #2

nomadbeni opened this issue Nov 9, 2017 · 17 comments

Comments

@nomadbeni
Copy link

If the yeelight is offline and a command is sent to the device, it says: UnhandledPromiseRejection....... which is good, because the yeelight is offline.
But when the yeelight comes online, it restarts the node-red, which is not good.
I attached a screenshot of the message.
Once it continuously restarted node-red untill i stopped it and deleted the yeelight node in the command line.
yeelight

@HendrikRoth
Copy link
Contributor

+1
Same issue here.

@Gromina
Copy link
Owner

Gromina commented Nov 14, 2017

Thanks for report. Will try to fix it asap. But probably not earlier than on next week unless you make pull request.
Busy at work :(

@mane-wt
Copy link

mane-wt commented Nov 28, 2017

Hi,
I have a similiar problem. If the Yeelight is offline och the IP-adress have changed, Node-Red got stuck in a restart loop and even managed to crash the installation on my Raspberry Pi -> Reinstallation from scratch.
I got this from syslog:
image

HendrikRoth added a commit to HendrikRoth/node-red-contrib-yeelight that referenced this issue Dec 3, 2017
@HendrikRoth
Copy link
Contributor

Fixed the issue.

#3

@Gromina
Copy link
Owner

Gromina commented Dec 4, 2017

Could you please confirm that the latest version fixes the issue?

Thanks to @HendrikRoth who made the fix

@HendrikRoth
Copy link
Contributor

The main fix was to wrap the method in an try/catch block. i updated to the latest version only to be up to date.

@nomadbeni
Copy link
Author

Well
I tried it. This happened:

yeelight error.txt

@mane-wt
Copy link

mane-wt commented Dec 5, 2017

Hi, I have also tried the new version and as long as the Yeelight bulb is online, everything works well but if I cut the power to the bulb the same behavior occurs as before with approximately 2 restarts
syslog.txt
of Node-Red per minute.
I enclose a new syslog that covers 3 restarts

@glennss
Copy link

glennss commented Dec 7, 2017

Same issue for me :(

Dec 7 10:26:52 raspberrypi Node-RED[28092]: 7 Dec 10:26:52 - [red] Uncaught Exception: Dec 7 10:26:52 raspberrypi Node-RED[28092]: 7 Dec 10:26:52 - Error: connect EHOSTUNREACH 192.168.30.49:55443 Dec 7 10:26:52 raspberrypi Node-RED[28092]: at Object.exports._errnoException (util.js:1020:11) Dec 7 10:26:52 raspberrypi Node-RED[28092]: at exports._exceptionWithHostPort (util.js:1043:20) Dec 7 10:26:52 raspberrypi Node-RED[28092]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14) Dec 7 10:26:52 raspberrypi systemd[1]: nodered.service: main process exited, code=exited, status=1/FAILURE Dec 7 10:26:52 raspberrypi systemd[1]: Unit nodered.service entered failed state. Dec 7 10:26:52 raspberrypi systemd[1]: nodered.service holdoff time over, scheduling restart.

@Gromina
Copy link
Owner

Gromina commented Dec 13, 2017

Could you please test 1.0.4 version in several cases:

  • starting node-red when yeelight is offline
  • starting node-res when yeelight is online
  • turning yeelight offline when node-red is running

I can't test it on hardware tight now :(

@nomadbeni
Copy link
Author

I will test is on saturday and post the log.

@glennss
Copy link

glennss commented Dec 13, 2017

Timing out and crashing :(

syslog.txt

@mane-wt
Copy link

mane-wt commented Dec 14, 2017

image
image
image

Unfortunately the flow that worked with 1.03 won't work with 1.04 for me :-(
I have rebboted the RPi, but same result.
The good news is thas Node-red won't restart anymore if a turn off the power to Yeelight.

@GeeBee93
Copy link

Same issue here, updating from 1.03 to 1.04 completely broke all nodes for me :(

@nomadbeni
Copy link
Author

Same with me.
image

@LolCatPhd
Copy link

Getting the same error as well.
1.04 broke all nodes.

@mane-wt
Copy link

mane-wt commented Jan 11, 2018

Any clues whats wrong?

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

7 participants