Node red add on crashing randomly

[dustin-auby]

Hi all,

it seems like a recent issue only happened for the last 2 weeks. the addon crahses with the bellow error.

2025-6-22 22:00:31
23 Jun 01:18:36 - [red] Uncaught Exception:
23 Jun 01:18:36 - [error] RangeError: Invalid WebSocket frame: invalid status code 1006
    at Receiver.controlMessage (/opt/node_modules/node-red-contrib-home-assistant-websocket/node_modules/ws/lib/receiver.js:626:30)
    at Receiver.getData (/opt/node_modules/node-red-contrib-home-assistant-websocket/node_modules/ws/lib/receiver.js:477:12)
    at Receiver.startLoop (/opt/node_modules/node-red-contrib-home-assistant-websocket/node_modules/ws/lib/receiver.js:167:16)
    at Receiver._write (/opt/node_modules/node-red-contrib-home-assistant-websocket/node_modules/ws/lib/receiver.js:94:10)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
    at Receiver.Writable.write (node:internal/streams/writable:510:10)
    at Socket.socketOnData (/opt/node_modules/node-red-contrib-home-assistant-websocket/node_modules/ws/lib/websocket.js:1355:35)
    at Socket.emit (node:events:524:28)
    at addChunk (node:internal/streams/readable:561:12)
[01:18:37] INFO: Service Node-RED exited with code 1 (by signal 0)

[JensRudolph]

Same, random happened.

[sinclairpaul]

node-red-contrib-home-assistant-websocket can be found at https://github.com/zachowj/node-red-contrib-home-assistant-websocket I would suggest logging your issue there.

[jimmyz5150]

I've been having a lot of crashes as well. Have to restart add-on. Watchdog not working. If inside NodeRed I will get a 502 error, have to go back out and restart add on

[cpuks]

Same here with latest Node Red, it crashes every 10-15 min
19 Jul 18:56:48 - [error] [modbus-flex-getter:rekuperator] Error: Timed out 19 Jul 19:02:01 - [red] Uncaught Exception: 19 Jul 19:02:01 - [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 "3". at throwUnhandledRejectionsMode (node:internal/process/promises:392:7) at processPromiseRejections (node:internal/process/promises:475:17) at processTicksAndRejections (node:internal/process/task_queues:106:32) [19:02:01] 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 [19:02:01] INFO: Service NGINX exited with code 0 (by signal 0)

[sinclairpaul]

@cpuks I have hidden your comment as it relates to a completely different node [modbus-flex-getter:rekuperator] please seek help with that at the source.

[osulivanDE]

Also here NR Addon does not restart although Watchdog is enabled

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[jimmyz5150]

It is still happening, watchdog isn't working or something. Keeping alive