Node-Red suddenly stopped working

Third party integrations Node-RED
1

Hi all,
I have had node-red up and running for ages with no issues. All of sudden it has stopped working for me.
Hoping someone can help out.

Many Thanks.

Here are the node red logs.
e[34m or support in, e.g., GitHub, forums or the Discord chat.e[0m
e[34m-----------------------------------------------------------e[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

up to date, audited 655 packages in 7s

52 packages are looking for funding
run npm fund for details

45 vulnerabilities (2 low, 17 moderate, 18 high, 8 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues possible (including breaking changes), run:
npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
npm notice
npm notice New minor version of npm available! 10.7.0 → 10.8.3
npm notice Changelog: Release v10.8.3 · npm/cli · GitHub
npm notice To update run: npm install -g [email protected]
npm notice
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:44:49] INFO: e[32mStarting Node-RED…e[0m

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Sep 20:44:50 - [info]

Welcome to Node-RED

5 Sep 20:44:50 - [info] Node-RED version: v4.0.2
5 Sep 20:44:50 - [info] Node.js version: v18.20.3
5 Sep 20:44:50 - [info] Linux 6.6.46-haos x64 LE
5 Sep 20:44:51 - [info] Loading palette nodes
5 Sep 20:44:51 - [info] Node-RED Contrib Theme Collection version: v4.0.8
5 Sep 20:44:56 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Sep 20:44:56 - [info] Settings file : /etc/node-red/config.js
5 Sep 20:44:56 - [info] Context store : ‘default’ [module=memory]
5 Sep 20:44:56 - [info] User directory : /config/
5 Sep 20:44:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Sep 20:44:56 - [info] Flows file : /config/flows.json
5 Sep 20:44:56 - [info] Server now running at http://127.0.0.1:46836/
5 Sep 20:44:57 - [info] Starting flows
fileServer listening on ip 192.168.0.13 and port 8098
[20:44:57] INFO: e[32mStarting NGinx…e[0m
5 Sep 20:44:57 - [info] [wled:1b1cabb698f8b240] wled 192.168.20.11
5 Sep 20:44:57 - [info] Started flows
5 Sep 20:44:57 - [red] Uncaught Exception:
5 Sep 20:44:57 - [error] TypeError: Cannot convert undefined or null to object
at Function.values ()
at Timeout._onTimeout (/config/node_modules/node-red-contrib-things/red/trigger.js:102:29)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
[20:44:57] INFO: e[32mService Node-RED exited with code 1 (by signal 0)e[0m
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[20:44:57] INFO: e[32mService NGINX exited with code 0 (by signal 0)e[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
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

LOGS FROM SUPERVISOR
2024-09-05 20:42:02.675 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting…
2024-09-05 20:42:02.680 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
2024-09-05 20:42:03.035 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package node-red/amd64 · GitHub with version 18.0.5
2024-09-05 20:42:20.366 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting…
2024-09-05 20:42:20.372 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
2024-09-05 20:42:20.749 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package node-red/amd64 · GitHub with version 18.0.5
2024-09-05 20:42:38.255 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting…
2024-09-05 20:42:38.260 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
2024-09-05 20:42:38.617 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package node-red/amd64 · GitHub with version 18.0.5
2024-09-05 20:42:57.607 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting…
2024-09-05 20:42:57.612 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
2024-09-05 20:42:58.000 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package node-red/amd64 · GitHub with version 18.0.5

2

It looks like this is the cause. You can start in safe mode and see if there is an update. If not you may need to remove them. Chk it’s repository for any known fixes.

1 Like
3

I opened NodeRed in safe mode and updated the Conrib-things, and anything else that needed updating. Everything works in safemode.
however when I turn off safe mode and start to start in still nothing.

I’ve tried restoring a backup from when I know it was working nothing. If I uninstall and reinstall and then resort a working backup will that retain all my flows?

here is the log again.
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

up to date, audited 853 packages in 16s

93 packages are looking for funding
run npm fund for details

40 vulnerabilities (1 low, 14 moderate, 18 high, 7 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues possible (including breaking changes), run:
npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
npm notice
npm notice New minor version of npm available! 10.7.0 → 10.8.3
npm notice Changelog: Release v10.8.3 · npm/cli · GitHub
npm notice To update run: npm install -g [email protected]
npm notice
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[15:38:59] INFO: Starting Node-RED…
s6-rc: info: service legacy-services successfully started

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

6 Sep 15:39:00 - [info]

Welcome to Node-RED

6 Sep 15:39:00 - [info] Node-RED version: v4.0.2
6 Sep 15:39:00 - [info] Node.js version: v18.20.3
6 Sep 15:39:00 - [info] Linux 6.6.46-haos x64 LE
6 Sep 15:39:00 - [info] Loading palette nodes
6 Sep 15:39:01 - [info] Node-RED Contrib Theme Collection version: v4.0.8
6 Sep 15:39:05 - [info] Dashboard version 3.6.5 started at /endpoint/ui
(node:297) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at Migrate from version 2.x to 3.x of the AWS SDK for JavaScript - AWS SDK for JavaScript
(Use node --trace-warnings ... to show where the warning was created)
6 Sep 15:39:05 - [info] node-red-contrib-home-assistant-websocket v0.68.9 nodes initialized
6 Sep 15:39:05 - [info] Settings file : /etc/node-red/config.js
6 Sep 15:39:05 - [info] Context store : ‘default’ [module=memory]
6 Sep 15:39:05 - [info] User directory : /config/
6 Sep 15:39:05 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Sep 15:39:05 - [info] Flows file : /config/flows.json
6 Sep 15:39:05 - [info] Server now running at http://127.0.0.1:46836/
6 Sep 15:39:05 - [info] Starting flows
[15:39:05] INFO: Starting NGinx…
fileServer listening on ip 192.168.0.13 and port 8098
6 Sep 15:39:06 - [info] [wled:1b1cabb698f8b240] wled 192.168.20.11
6 Sep 15:39:06 - [info] Started flows
6 Sep 15:39:06 - [red] Uncaught Exception:
6 Sep 15:39:06 - [error] TypeError: Cannot convert undefined or null to object
at Function.values ()
at Timeout._onTimeout (/config/node_modules/node-red-contrib-things/red/trigger.js:102:29)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
[15:39:06] 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
[15:39:06] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
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 base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs 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

4

It’s still that same node that is throwing an error. You can submit an issue with the code owner or remove the nodes in their entirety.

edit Samsung has their own set of NR nodes, It seems they should work with smart things.

5

Thanks I need to learn to read logs better. I deleted it and all is working! thanks again.