Closed nytram-md closed 2 years ago
WLED is alive and well
I've seen this occasionally as well and unfortunately I think it's an issue with WLED's API. There's nothing special in my code: I just make a web call to the address shown in the error. That request is timing out, presumably because WLED's API isn't responding.
One thing to try next time you see this error: grab the URL shown in the error message and try dropping it into your browser and see if you get a response.
Hi
I will have a look.
If its not an actual error and works. Can you supress the error to stop it reporting ?
Thanks for quick response
Martyn
Regards
Martyn
From: danecreekphotography notifications@github.com Sent: Thursday, September 24, 2020 3:56:20 PM To: danecreekphotography/node-red-contrib-wled2 node-red-contrib-wled2@noreply.github.com Cc: nytram-md martyn_dickinson@hotmail.com; Author author@noreply.github.com Subject: Re: [danecreekphotography/node-red-contrib-wled2] Node Red Constant Errors (#70)
I've seen this occasionally as well and unfortunately I think it's an issue with WLED's API. There's nothing special in my code: I just make a web call to the address shown in the error. That request is timing out, presumably because WLED's API isn't responding.
One thing to try next time you see this error: grab the URL shown in the error message and try dropping it into your browser and see if you get a response.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/danecreekphotography/node-red-contrib-wled2/issues/70#issuecomment-698398364, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHZVQCCHNGIRK3FCZHLC6LSHNMZJANCNFSM4RYM457A.
Just checked and all is OK with the link
It is an actual error, not something I can/should suppress. When you see this error does it eventually just start working again by itself? If yes, does the node to back to showing a green state? Or does it start working but stay showing a red error?
Never seen all 4 say connected. Sometimes all say error or the top one is connected as per above.
Ill keep an eye and have a look later and let you know.
cheers
I had this error as well and it appears to happen when deploying the flow and the nodes try to connect all at once. If I change a node and only deploy changed nodes, it works.
Too many simultaneous requests to WLED instance can deplete free memory on ESP (even ESP32). They may even cause WLED to reboot. Try to sequence your requests.
Closing old issues.
Hi
In testing the node works well when running but I keep getting messages and error reporting on the node itself as per image.
This is what I get when I look at Node red after a few hours.
Cheers martyn