Thanks @adamoutler.
I’m using an HA Add-on
I forgot to include it with he original post
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 13.3.0
There is an update available for this add-on!
Latest add-on version: 13.3.1
Please consider upgrading as soon as possible.
System: Home Assistant OS 8.4 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2022.7.7
Home Assistant Supervisor: 2022.08.3
+1. Stuff that Node-Red used to cope with, is now crashing it, and the watchdog isn’t restarting it - logs look [nearly] exactly like yours @martoq. Might well be a NR3.X thing, but came here looking and found this post so thought I’d add a me-too in.
14 Aug 21:27:25 - [red] Uncaught Exception:
14 Aug 21:27:25 - [error] Error: connect ENETUNREACH 52.62.123.31:9090
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
[21:27:25] WARNING: Node-RED crashed, halting add-on
[21:27:25] INFO: Node-RED stoped, restarting...
s6-rc: info: service legacy-services: stopping
[21:27:25] INFO: Node-RED stoped, restarting...
s6-svwait: fatal: supervisor died
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
[21:27:25] INFO: nginx stoped, restarting...
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Hi! Maybe a simple question, but I have spent a good time googling without finding the answer.
I have a bunch of npm packages that I don’t use (or have ever used). Most likely they are/was included in the add-on. However, I can’t uninstall them. I only seem to be able to uninstall the packages that I have installed myself. Please advice on how I can get rid of them.
I worked on node red add on, and a slow connection might have stuff some flows. All good. I rolled back to an 11Aug backup, all good. Now when i restart HA, everything kick of, the flows start , error log is all good etc. The flows work because i use UPD listerner etc so the data get processed and send from the flows via mqtt to HA, happy days.
However i cant edit the flows, when i press on the Node Red “icon” on the side bare, its says the Add on is not running…strange. Any ideas
Hi Im on the latest nodered 3.0.2 but im giving up on it after 4 years of wonderful automations as a add on in hassio. It is stopping every night during the night and when i wake up no automations work because nodered add on has stopped and the watchdog is not staring it. This is only from the new release, can someone please tell me how to downgrade to the previous version? I have about 35 tabs worth of flows and it might take another 4 years to migrate back to yaml based automations I cant seems to find any more info in the logs about why it is stopping. Maybe anyone else have the same problems could give some advice?
Another question: is there a way to start nodered from hassio on a regular basis for the interim until a solution is found?
No sure what has changed but stability seems to have returned. Whether it was the api, core, node-red or the node-red integration, something resolved the crashing issue.
I’m using the Node-Red AddOn 13.4.0
If I open ‘Manage Palette’ it shows that I have two modules that are not updated.
node-red-contrib-modbus
and
node-red-node-email
Hi all
I’ve been running into a specific problem installing new nodes through Node red’s palette manager. It seems pretty much every node install fails with an engine err that the Node version is out of bounds, the majority of the nodes require Node 10, 12 or 14, but mine reports as 16.
To illustrate the problem I just now grabbed a random node, updated just a day ago, and arguably fairly popular: node-red-contrib-alexa-home
-----------------------------------------------------------
2022-09-28T20:53:42.937Z Install : node-red-contrib-alexa-home 2.0.1
2022-09-28T20:53:43.162Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-09-28T20:53:44.428Z [err] npm WARN config production Use `--omit=dev` instead.
2022-09-28T20:53:48.126Z [err] npm
2022-09-28T20:53:48.126Z [err]
2022-09-28T20:53:48.126Z [err] ERR!
2022-09-28T20:53:48.126Z [err]
2022-09-28T20:53:48.126Z [err] code
2022-09-28T20:53:48.127Z [err] EBADENGINE
2022-09-28T20:53:48.129Z [err] npm
2022-09-28T20:53:48.129Z [err]
2022-09-28T20:53:48.129Z [err] ERR!
2022-09-28T20:53:48.129Z [err]
2022-09-28T20:53:48.129Z [err] engine
2022-09-28T20:53:48.129Z [err] Unsupported engine
2022-09-28T20:53:48.129Z [err] npm
2022-09-28T20:53:48.129Z [err]
2022-09-28T20:53:48.130Z [err] ERR!
2022-09-28T20:53:48.130Z [err]
2022-09-28T20:53:48.130Z [err] engine
2022-09-28T20:53:48.130Z [err] Not compatible with your version of node/npm: @azure/[email protected]
2022-09-28T20:53:48.130Z [err] npm
2022-09-28T20:53:48.130Z [err]
2022-09-28T20:53:48.130Z [err] ERR!
2022-09-28T20:53:48.130Z [err]
2022-09-28T20:53:48.130Z [err] notsup
2022-09-28T20:53:48.130Z [err] Not compatible with your version of node/npm: **@azure/[email protected]**
2022-09-28T20:53:48.130Z [err] npm
2022-09-28T20:53:48.130Z [err]
2022-09-28T20:53:48.130Z [err] ERR!
2022-09-28T20:53:48.131Z [err]
2022-09-28T20:53:48.131Z [err] notsup
2022-09-28T20:53:48.131Z [err] **Required: {"node":"10 || 12 || 14"}**
2022-09-28T20:53:48.131Z [err] npm
2022-09-28T20:53:48.131Z [err]
2022-09-28T20:53:48.131Z [err] ERR!
2022-09-28T20:53:48.131Z [err]
2022-09-28T20:53:48.131Z [err] notsup
2022-09-28T20:53:48.131Z [err] Actual: {"npm":"8.10.0","node":**"v16.16.0"}**
2022-09-28T20:53:48.134Z [err]
2022-09-28T20:53:48.134Z [err] npm
2022-09-28T20:53:48.134Z [err]
2022-09-28T20:53:48.134Z [err] ERR!
2022-09-28T20:53:48.134Z [err] A complete log of this run can be found in:
2022-09-28T20:53:48.134Z [err] npm
2022-09-28T20:53:48.134Z [err]
2022-09-28T20:53:48.135Z [err] ERR!
2022-09-28T20:53:48.135Z [err] /root/.npm/_logs/2022-09-28T20_53_44_291Z-debug-0.log
2022-09-28T20:53:48.152Z rc=1
This is a supervised HA, so I can positively say that I never touched any of the underlying node components. Here’s the version info:
And Node Red:
While everything else node-red related seems to run fine as-is, this part seems to be broken. If anyone can offer any advice on how to fix this, I would be very thankful.
Bump. Anyone?
I’m kinda stuck on this one as the Node 16 engine is preventing me from installing any newer pallette items. I tried uninstalling and reinstalling the node add-on, yet it did not seem to have any effect. What gives? How do I get my supervised NodeRed/HA back running Node v14 ?
A changelog of the NodeRed shows that with the add-on v13.1 Frenck updated Node.js to v16.
Don’t know a motivation since NR docs advice v14 (confirming v16 is supported at the same time). Any way, Node.js 16 has LTS status today.
If you have real need to stick with Node14, I think the only way is to remove NodeRed add-on, then install selected version (v 3.0.0 I suppose).
Possibly downgrading can be done without uninstalling. Backup your flows before this operation.
How to install specific version: I’m not confident enough, but I guess it should be possible with Supervisor commands (the same way you can install specific ha version)
Thanks for clarifying,
Full disclosure, I’m not node savvy enough either to attempt a downgrade to a specific version to solve this, and honestly I would prefer avoiding that route as I would really like to stay on Node 13.x as there’s a lot of great enhancements (thanks @frenck !)
If indeed as you say Node14 is still supposed to be in there, perhaps something has gone wrong in the upgrade (or the deity of your choice forbid - a bug!)
Either way, ANY new node apps I try to install, do not seem to see said v14, they only see the latest v16 and throw the badengine error as per below
To clarify my ask, is there a way to (for lack of a better term) ‘re-register’ node14 in parallel with node16? (And how would I do that on a supervised install)
2022-10-16T18:34:58.191Z [err] notsup
2022-10-16T18:34:58.191Z [err] Not compatible with your version of node/npm: @azure/[email protected]
2022-10-16T18:34:58.191Z [err] npm
2022-10-16T18:34:58.192Z [err] Required: {"node":"10 || 12 || 14"}
2022-10-16T18:34:58.192Z [err] Actual: {"npm":"8.10.0","node":"v16.16.0"}
PS: For the good of the community, I don’t mind doing some drastic experimentation and changes, as I run HA in a Hyper-V virtual machine, i.e. I snapshot before every major upgrade, however rather than downgrading,I would really prefer to stay on NR 13.x and fix it here.
Hi I’m sure I’m being a complete idiot here but Node Red was running sluggish today so I went to look at the flows and I get “Node-RED Add-on is not running. Please start it first” It is still running and the flows are executing with delays in some instances. I have tried restoring to a previous snapshot also uninstalling and reinstalling but the same issue. The Addon screen shows the red dot when you press start nothing happens. The logs just show this and not other information.
19 Oct 18:16:51 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
19 Oct 18:16:56 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:01 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:06 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:11 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:16 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:21 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:31 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:36 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:42 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:47 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:52 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:17:57 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:07 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:12 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:17 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:22 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:28 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:33 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:38 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:40 - [error] [api-call-service:Galaxy Tablet Screen Off] Call-Service attempted without connection to server.
19 Oct 18:18:40 - [error] [api-call-service:Lounge Light One Off] Call-Service attempted without connection to server.
19 Oct 18:18:40 - [error] [api-call-service:Lounge Light Two Off] Call-Service attempted without connection to server.
19 Oct 18:18:40 - [error] [api-call-service:Lounge Cabinet Lower Off] Call-Service attempted without connection to server.
19 Oct 18:18:43 - [info] [server:Home Assistant] Connecting to http://supervisor/core
19 Oct 18:18:48 - [info] [server:Home Assistant] Connecting to http://supervisor/core
