Node Red issues

Third party integrations Node-RED
1

Hi have updated Node Red 13.3.0 to the latest version Node-RED 13.5.3 running on Home Assistant 2022.11.4,

Post upgrade of NodeRed to 13.5.3, I’m unable to access my configurations in Node-Red. It reports an error that Node-Red is not running. I restart the Node-Red service however it reports the same issue when trying the access the Node-Red configuration, the Node-Red service crashes.

All my automations are done by Node Red, so this is causing major problems to my home automation.

I restore a backup of Node-Red version 13.3.0 and all works correctly, however Node-Red autoupdates to the latest version after a few hours which initiates the same problem and all my automation stops working again.

I would appreciate any assistance regarding this matter.

Log extract:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh

Add-on: Node-RED

Flow-based programming for the Internet of Things

Add-on version: 13.5.3

You are running the latest version of this add-on.
System: Home Assistant OS 9.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.11.4
Home Assistant Supervisor: 2022.11.2

Please, share the above information when looking for help

or support in, e.g., GitHub, forums or the Discord chat.

cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/customizations.sh
cont-init: info: /etc/cont-init.d/customizations.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/node-red.sh
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
up to date, audited 9 packages in 1s
found 0 vulnerabilities
cont-init: info: /etc/cont-init.d/node-red.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun nodered (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:23:10] INFO: Starting Node-RED…

start
node $NODE_OPTIONS node_modules/node-red/red.js “–settings” “/etc/node-red/config.js”
30 Nov 15:23:14 - [info]
Welcome to Node-RED

30 Nov 15:23:14 - [info] Node-RED version: v3.0.2
30 Nov 15:23:14 - [info] Node.js version: v16.17.1
30 Nov 15:23:14 - [info] Linux 5.15.61-v8 arm64 LE
30 Nov 15:23:16 - [info] Loading palette nodes
30 Nov 15:23:21 - [info] Dashboard version 3.2.0 started at /endpoint/ui
30 Nov 15:23:22 - [info] Settings file : /etc/node-red/config.js
30 Nov 15:23:22 - [info] Context store : ‘default’ [module=memory]
30 Nov 15:23:22 - [info] User directory : /config/node-red/
30 Nov 15:23:22 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 Nov 15:23:22 - [info] Flows file : /config/node-red/flows.json
30 Nov 15:23:22 - [info] Server now running at http://127.0.0.1:46836/
30 Nov 15:23:22 - [info] Starting flows
[15:23:22] INFO: Starting NGinx…
30 Nov 15:23:23 - [error] [api-call-service:aeafaa54a5aad308] Error: Server config node not found
30 Nov 15:23:23 - [info] Started flows
30 Nov 15:23:23 - [info] [server:Home Assistant] Connecting to http://localhost:8123
30 Nov 15:23:23 - [info] [server:Home Assistant] Connecting to http://localhost:8123
30 Nov 15:23:23 - [red] Uncaught Exception:
30 Nov 15:23:23 - [error] Error: Invalid access token for websocket
at /opt/node_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:112:29
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Websocket.connect (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:82:23)
[15:23:23] WARNING: Node-RED crashed, halting add-on
[15:23:23] INFO: Node-RED stopped, restarting…
s6-rc: info: service legacy-services: stopping
[15:23:23] INFO: Node-RED stopped, restarting…
s6-svwait: fatal: supervisor died
s6-rc: info: service legacy-services 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 fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

2

I would try running ha supervisor repair from a terminal or SSH window.

If that doesn’t work, I would disable automatic updates for the Node red addon, restore your old version, and then open a github issue. Your logs show an invalid access token when connecting to Home Assistant, and all that should be configured automatically for you by the addon when it is installed or updated.

3

Hi Tim,

Thank you for your advice.
Much appreciated.

Regards
Harry

4

I do t have an issue with Node Red but have noticed while watching recent tutorials online I have noticed that I seem to be missing some nodes under the Home Assistant tab. I see that some people have a reddish/pink node called device and a while other section called home assistant entities which lists 5 or so nodes. I verified that I’m seem to be running the latest NodeRed addon ver 14.1 and NodeRed itself on ver3.0.2. Could it be that I’m running HA OS instead of docker or some other type of installation. Just something that I have been wondering abs if I could also have this update to node res might open up some new options for automations.