Home Assistant Community Add-on: Node-RED

Frank3 · August 24, 2022, 10:02am

Hi, need some help.

I used Node Red in HA for years, with no issues

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

" Node-RED

Add-on is not running. Please start it first

OK"

then

What have i broken

Thanks

eposza · August 30, 2022, 10:19am

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?

martoq · September 1, 2022, 7:22pm

This has been an on going problem for awhile now with no resolution or even a culprit tbh. All I get is this in the logs:

martoq · September 8, 2022, 6:13pm

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.

sender · September 15, 2022, 5:30pm

Any help on what to fill in to connect to the addon using:

fribse · September 25, 2022, 9:39pm

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

I can see that the first one could be because I’m on a X86 platform: [solved] Update of node-red-contrib-modbus

But I’m not so sure about the ‘node-red-node-email’.
That seems to be a problem that it is changed from a core module to an external module?

So how do I fix these correctly?
Would it help to reinstall node-red addon?

MaxVonEvil · September 28, 2022, 9:01pm

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.

stevemann · October 5, 2022, 5:38pm

How did you get the colored backgrounds in the Node Red work area??

Nerdix · October 5, 2022, 9:00pm

When editing a group you can choose color etc.! Just double click a group and you will see the options

MaxVonEvil · October 16, 2022, 7:32am

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 ?

maxym · October 16, 2022, 10:26am

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)

MaxVonEvil · October 16, 2022, 6:52pm

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.

orangelizard · October 19, 2022, 5:26pm

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

Any help would be greatly appreciated.

orangelizard · October 19, 2022, 6:25pm

@Frank3 Same “Addon is not running” message when attempting to edit flows. Red dot and nothing special in the logs. Flows seemed slow today so wanted to check for errors. I could edit a couple of days ago. Did you find a solution?

MaxVonEvil · October 21, 2022, 5:33am

@frenck - if you’re reading this,
Since you’re one of the NR masterminds here, do you have any advice as to make palette manager once again be able to install nodes requiring Node v14?

Can you confirm that v14 is still included in NodeRed 13.x as @maxym mentioned?

Either way, I’m kinda grasping at straws here, as I’ve already tried re-installing NR and I’m unsure how to tackle this problem, preventing me from installing nodes I need to work with.

MaxVonEvil · October 24, 2022, 4:09am

So at the risk of sounding like the broken record, I’m starting to wonder here:

Anyone out there capable of installing other palette nodes requiring Node 14 after Node Red v13 ?
Did someone make a decision to ‘unsupport’ any palette nodes which does not support Node 16?
If that’s not the case and Node14 is still in the mix, what can cause it to remain invisible to the palette installer, even after a NR reinstall?
Other than downgrading to an old Node Red 12, which I don’t even know if and how can be done on a Supervised HA environment, what can be done here?
Is this a general problem, or am I being the global village idiot here? If it’s simple to solve and I’m overlooking it, please provide a push in the right direction.
If this is something nobody else than I is experiencing, I seriously need some advice how to get Node 14 enabled in NR 13.2

Thanks
/Max

lbedogni · November 16, 2022, 4:48pm

I upgraded node-red today and I can’t run my flows again. All HA nodes have disappeared, so I don’t really know how to proceed. I could try to delete all the HA nodes, but that would be quite a lot of work. Has anyone come up with a solution? I may also downgrade, but I do not have a backup for node red.

mr_home-assitant · December 13, 2022, 3:29pm

Hi, did you find a way to connect to HomeSeer using the add-on? I’m looking for the same solution. Since I have all my z-wave devices on HomeSeer and some events I still want to use. Over time I will port everything over to HA. But for now it seems to be a nice solution.

I assume that the HomeSeer module you arereferring to is the one in NoderRed?
I already have create a webhook in HomeAssistant but I’m not sure if that is ok. Which IP url should I use there the HomeSeer machine url or the HA url??

So hopefully you can point me out how to achieve the connection Or maybe even share some sample code you used for it? Thanks.

mr_home-assitant · December 14, 2022, 10:34am

Ok, managed to get this working myself. Using the right (HS4 user and admin will help to connect as well
Now I have the HS4 devices and events listed. Next I need to get familiar with creating flows and how to get t hat into the HA dashboard.

For others looking for a way to get this implemented. This info helped me out (select an add-on in the Node red settings) and follow the instructions:

mr_home-assitant · December 16, 2022, 8:47am

Now I have Node-red connected to HomeSeer I’m looking to build a simple first flow, to get the idea how this works. But most howto are about flows in HA and not in combination with HomeSeer. So anyone who has a simple to understand flow which helps me to build a first flow having a device status in HomeSeer set from Off to On. Using a switch (from the dashboard) or an inject as I tried in my example. since I have no idea how to get there. Any howto (youtube) or other samples are appreciated as well. Thanks.

[{"id":"6bc9179586104c63","type":"hs-device","z":"dc1404c404fe1bd4","name":"Beneden Bijkeuken Fibaro Switch Binary Node 18 Root Switch Binary 1","device":"24","server":"367ff7807724edc9","feature":"25","reportonstartup":true,"x":560,"y":460,"wires":[["f03e96688bdbd1ba"]]},{"id":"f03e96688bdbd1ba","type":"debug","z":"dc1404c404fe1bd4","name":"debug 1","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":920,"y":600,"wires":[]},{"id":"3fd5ad04e634e898","type":"inject","z":"dc1404c404fe1bd4","name":"On","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"On","payload":"control","payloadType":"str","x":170,"y":440,"wires":[["6bc9179586104c63"]]},{"id":"9c5b0ec41354855e","type":"inject","z":"dc1404c404fe1bd4","name":"Off","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"Off","payload":"control","payloadType":"str","x":170,"y":500,"wires":[["6bc9179586104c63"]]},{"id":"367ff7807724edc9","type":"hs-server","name":"HomeSeer Server","host":"192.168.0.30","port":"80"}]

Schermafbeelding 2022-12-16 om 09.44.56

Edit!
Got it working now. Both for devices and events it seems to work. Nice!

Schermafbeelding 2022-12-18 om 16.29.45