Node-RED crashes with unhandled exception on every Home Assistant restart

[marc965]

Every time I restart Home Assistant, Node-RED gets terminated due to an exception. This must be related to node-red-contrib-home-assistant-websocket.

29 Mar 22:20:19 - [info] [server:homeassistant] Connection closed to http://192.168....
29 Mar 22:20:19 - [info] [server:homeassistant] Connecting to http://192.1...
29 Mar 22:20:24 - [info] [server:homeassistant] Connecting to http://192.16..
29 Mar 22:20:29 - [info] [server:homeassistant] Connecting to http://19..
29 Mar 22:20:34 - [info] [server:homeassistant] Connecting to http://192.168.
29 Mar 22:20:39 - [info] [server:homeassistant] Connecting to http://192.16
29 Mar 22:20:44 - [info] [server:homeassistant] Connecting to http://192.168
29 Mar 22:20:49 - [info] [server:homeassistant] Connecting to http://192.1
29 Mar 22:20:54 - [info] [server:homeassistant] Connecting to http://192.1
29 Mar 22:20:59 - [info] [server:homeassistant] Connecting to http://192.168
29 Mar 22:21:04 - [info] [server:homeassistant] Connecting to http://192.168.
29 Mar 22:21:09 - [info] [server:homeassistant] Connecting to http://192.16
29 Mar 22:21:14 - [info] [server:homeassistant] Connecting to http://192.168
29 Mar 22:21:19 - [info] [server:homeassistant] Connecting to http://192.168
29 Mar 22:21:19 - [info] [server:homeassistant] Connected to http://192.168
29 Mar 22:21:49 - [info] [server:homeassistant] Connection closed to http://192.168.
[red] Uncaught Exception:
29 Mar 22:21:49 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<Object>".
    at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
    at processPromiseRejections (node:internal/process/promises:470:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:32)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 15h 20min 12.046s CPU time.
nodered.service: Scheduled restart job, restart counter is at 10.
Stopped nodered.service - Node-RED graphical event wiring tool.
nodered.service: Consumed 15h 20min 12.046s CPU time.
Started nodered.service - Node-RED graphical event wiring tool.
29 Mar 22:22:10 - [info]
Welcome to Node-RED
===================
29 Mar 22:22:10 - [info] Node-RED version: v4.1.5
29 Mar 22:22:10 - [info] Node.js  version: v20.20.0
29 Mar 22:22:10 - [info] Linux 6.12.62+rpt-rpi-2712 arm64 LE
29 Mar 22:22:10 - [info] Loading palette nodes
29 Mar 22:22:10 - [info] Node-RED Contrib Theme Collection version: v4.1.1
29 Mar 22:22:11 - [info] node-red-contrib-telegrambot version: v17.0.5
29 Mar 22:22:11 - [info] node-red-contrib-home-assistant-websocket v0.80.3 nodes initialized
29 Mar 22:22:12 - [info] Settings file  : /root/.node-red/settings.js
29 Mar 22:22:12 - [info] Context store  : 'default' [module=memory]
29 Mar 22:22:12 - [info] User directory : /root/.node-red
29 Mar 22:22:12 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Mar 22:22:12 - [info] Flows file     : /root/.node-red/flows.json
29 Mar 22:22:12 - [info] Server now running at http://127.0.0.1:1880/
29 Mar 22:22:12 - [warn] Using unencrypted credentials
29 Mar 22:22:12 - [info] Starting flows

Has anyone experienced this or has any idea what might be causing it? Any help would be appreciated.

Sincerely
Marc

[zachowj]

Post your diagnostics information

https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html

[marc965]

Version: 0.80.3

Home Assistant version: 2026.3.4
Companion version: 4.2.3

Node-RED version: 4.1.5
Docker: no
Add-on: no

Node.js version: v20.20.0 arm64 linux
OS: Linux 6.12.62+rpt-rpi-2712 arm64

[marc965]

Just a quick update – the issue is still present. Had 3 crashes again today, same pattern every time. Is there anything else I can provide to help track this down?

[zachowj]

You can try adding this to your Node-RED settings.js file to get more insight into the unhandled promise rejection:

process.on('unhandledRejection', (reason, p) => {
  console.log('Unhandled Rejection:', p, 'reason:', reason);
});