To add the credential_secret, click on Node-RED in Addons. At the top you'll see Info Documentation Configuration Log. Click on Configuration and enter your credential_secret. Make sure you to Save.
The autocomplete UI for Nodered HA nodes has gotton worse and worse and itās now barely useable for me.
This entity exists, just the UI is unable to match it, and lists it at the bottom of the list:
Iām not sure where to raise this issue, could someone point me to the correct place?
2 Likes
Updating to 2023.10 seems to have broke the add on for me. It now fails to startup.
I tried updating to 2023.10.1 and manually restarting but the issue persists.
Anyone else run into this same issue?
I havenāt tried that update yet. It looks like I need 3. Did you have the same? In what order did you run them?
Iām in the same boat.
Image ghcr.io/hassio-addons/node-red/amd64:14.6.1 does not exist for addon_a0d7b954_nodered
I updated core before node-red
In the same boat hereā¦
Someone said on reddit:
āNode-Red Companion 3.0 was made available as a non-beta release in HACS, but it until recently required a beta version of the Home Assistant nodes in Node-Red. If youāve not updated to the latest nodes, then the 3.0 update for Companion would break your automations.ā
Two options: 1. Downgrade to an earlier version of Node-Red by restoring from an earlier backup of Home Assistant. 2. Update your Home Assistant nodes in Node-Red to the 0.57+ version, which came out of beta 4 days ago.
Just tried to restore a full backup from 10/4. Node Red is back to 14.5.0, but it also does not start and i got the same error as you.
Just restored a 10/4 backup with v2.2.0 of Node-RED Companion. Add-on is still failing to start
1 Like
Iām holding off on the latest updates until I can figure out all these versions and whatās happening. Not even sure why I have Node Red Companion. I installed Node Red just to try it out. I have a few flows and not sure itās giving me any advantages, although a couple flows are pretty cool.
After upgrading to NodeRed 14.5.0 it no longer started successfully in HA.
I restored NodeRed back to the 14.4.5 version and was able to start and run it again.
It appears that the Node-RED addin 14.6.1 was just released, installing this version also seems to work.
I still have problems with 14.6.1
The image does not exist error answer/information, can be found in this issue:
https://github.com/hassio-addons/addon-node-red/issues/1701#issuecomment-1751649557
@MaxVonEvil Seeing the same exact issue, no longer able to install any packages through the palette manager. Iāve reached my limits in trying to figure out how to make it work.
My (silly) workaround has been to revert to a backed up version (13.3), install packages via palette manager, then upgrade again to 14.6 version since Iād already built using new nodes. Note that for me, the npm installer in the add-on also did not work to install packages (worked once, then node red didnāt recognize the new nodes, and didnāt work for other packages).
@frenck, can you revert to previous working version? Or is there something else that is driving this?
My Node-Red addon is acting up this week all of a sudden. At some point my entire Home Assistant crashes and reboots itself and after this, the Node-Red addon is not starting anymore. The log of the addon says:
[20:41:58] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
27 Oct 20:42:03 - [info]
Welcome to Node-RED
===================
27 Oct 20:42:03 - [info] Node-RED version: v3.1.0
27 Oct 20:42:03 - [info] Node.js version: v18.18.2
27 Oct 20:42:03 - [info] Linux 6.1.21-v8 arm64 LE
27 Oct 20:42:04 - [info] Loading palette nodes
27 Oct 20:42:13 - [info] Dashboard version 3.6.1 started at /endpoint/ui
27 Oct 20:42:14 - [warn] ------------------------------------------------------
27 Oct 20:42:14 - [warn] [node-red-contrib-home-assistant-websocket/all] SyntaxError: Malformed JSON in file: /config/node-red//node-red-contrib-home-assistant-websocket.json
Unexpected token in JSON at position 0
27 Oct 20:42:14 - [warn] ------------------------------------------------------
27 Oct 20:42:14 - [info] Settings file : /etc/node-red/config.js
27 Oct 20:42:15 - [info] Context store : 'default' [module=localfilesystem]
27 Oct 20:42:15 - [error] Failed to start server:
27 Oct 20:42:15 - [error] Error: Error loading context store: Error: Invalid JSON in context file '/config/node-red/context/04bede65d5e346c4/0652c8ec913711cc.json'
at /opt/node_modules/@node-red/runtime/lib/nodes/context/index.js:180:15
[20:42:15] INFO: Service Node-RED exited with code 0 (by signal 0)
[20:42:17] INFO: Starting Node-RED...
Iāve had this problem as well a couple of days ago and in the end I decided to wipe my Home-Assistant and load a backup on a new SD-card. 3 days later, the problem is now back and I have no idea how to solve it. Does anyone have an idea what this problem might be and what I need to do to solve this?
Edit:
I was able to temporarily solve this by copying the data from the corrupt context file .tmp file to the corrupt context file. After this I kept getting errors on other context files so I kept doing this until the log stopped throwing errors.
Dears,
Some days ago NODE red started to crash continuously. I tried to restore some backups but not result. I have a lot of automations with node red, and we canāt use now becausse the node red addemdum not starts. The error is:
Welcome to Node-RED
===================
5 Nov 16:02:12 - [info] Node-RED version: v3.1.0
5 Nov 16:02:12 - [info] Node.js version: v18.18.2
5 Nov 16:02:12 - [info] Linux 6.1.59 x64 LE
5 Nov 16:02:12 - [info] Loading palette nodes
5 Nov 16:02:15 - [info] Dashboard version 3.6.1 started at /endpoint/ui
5 Nov 16:02:15 - [red] Uncaught Exception:
5 Nov 16:02:15 - [error] Error: bind EADDRINUSE 192.168.1.120:4002
at node:dgram:364:20
at processTicksAndRejections (node:internal/process/task_queues:83:21)
[16:02:15] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[16:02:15] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
And my addendum configuration is:
Please I need your help, we have all the automations not working nowā¦
Thanks in advance,
Jose
Hi there
Not sure where to begin, but recently Node-RED seems to be causing my Home Assistant to crash any time it tries to make a call or interact with things in Home Assistant.
Home Assistant Core: 2023.11.1
Home Assistant Supervisor: 2023.10.1
Home Assistant OS: 11.1
Node-RED versions: 15.0.0 and 14.6.3
I updated Node-RED to 15, and at some point after (canāt tell when), I noticed that Home Assistant was unresponsive.
Iāve tried rolling back changes, to no avail (I may not be doing this right), however I have through testing narrowed it down to Node-RED calling into Home Assistant.
Firstly, I turned off start-on-boot for Node-RED to avoid being in an endless crashing loop!
I deleted all the flows I have, including the server. I then re-add the server and add a CallService Node, with a simple Inject wired up. I deploy that and then the whole system goes unresponsive (Home Assistant app, web front end) and I have to cycle the power on my Raspberry Pi 4.
Iāve added logging to Home Assistant, however that just seems to be entity updates.
I am reasonably new to Home Assistant (Jan this year), but am a tech professional, so feel I know my way around docker etc.
Does anyone have anything suggestions on what I should do to diagnose this further? How can an AddOn completely crash Home Assistant?!
Ok well now I am embarrassed - after posting this, I went back and reviewed my setup and wondered if it was a custom service that was causing the problem (I have some Python that interacts with a simple lighting controller over UDP).
Turns out, my Python was causing the issue 
Back to loving NodeRed again, and now looking at improving my Python scripts!
1 Like
Hi Everyone. I use HA with Supervisor. I installed the addon. And want work with some devices uses UDP protocol. But i cantāt see that the UDP packeges donāt come out from HA host. I used network packet sniffer on my router (i canāt see them on the router).