Home Assistant Node-RED Crashed out of the blue

General
1

Sorry if this isn't the correct place to post this.

Can anyone tell me what is going on in the error log below? This just recently started happening and I uninstall/reinstall node-red and add my flows back one at a time. So far, I can't pin it on any one flow/node, but I'm leaning towards node-red-contrib-alexa-remote2, but I've had it installed and working for months, maybe a year.

Any help would be much appreciated!

29 Sep 10:10:06 - [info] [server:Home Assistant-Mine] Connected to http://supervisor/core
29 Sep 10:10:07 - [red] Uncaught Exception:
29 Sep 10:10:07 - [error] Error: Invalid context key
    at Object.value (/opt/node_modules/@node-red/runtime/lib/nodes/context/index.js:291:31)
    at NodeRedContext.get (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/common/NodeRedContext.js:17:24)
    at EventsState.getComparatorResult (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/BaseNode.js:151:35)
    at EventsState.onHaEventsStateChanged (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/events-state/controller.js:71:32)
    at EventsState.onStatesLoaded (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/events-state/controller.js:179:18)
    at EventEmitter.emit (node:events:539:35)
    at /opt/node_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:230:27
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022/09/29 10:10:07 [error] 369#369: *486 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /icons/node-red-contrib-home-assistant-websocket/ha-events-state-changed.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/icons/node-red-contrib-home-assistant-websocket/ha-events-state-changed.svg", host: "qobh7***ed.ui.nabu.casa", referrer: "https://qobh7***ed.ui.nabu.casa/api/hassio_ingress/cdNAdzVXI0tOE-***yMVO4TaE/"
2022/09/29 10:10:07 [error] 369#369: *486 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /icons/node-red/timer.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/icons/node-red/timer.svg", host: "qobh7***ed.ui.nabu.casa", referrer: "https://qobh7***ed.ui.nabu.casa/api/hassio_ingress/cdNAdzVXI0tOE-P2n***4TaE/"
2022/09/29 10:10:07 [error] 369#369: *486 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /icons/node-red-contrib-home-assistant-websocket/ha-current-state.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/icons/node-red-contrib-home-assistant-websocket/ha-current-state.svg", host: "qobh7***ed.ui.nabu.casa", referrer: "https://qobh7***ed.ui.nabu.casa/api/hassio_ingress/cdNAdzV***aEKyMVO4TaE/"
2022/09/29 10:10:07 [error] 369#369: *486 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /icons/node-red/swap.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/icons/node-red/swap.svg", host: "qobh7***ed.ui.nabu.casa", referrer: "https://qobh7***ed.ui.nabu.casa/api/hassio_ingress/cdNAdzV***cyaEKyMVO4TaE/"
[10:10:07] WARNING: Node-RED crashed, halting add-on
2

The stack trace points at node-red-contrib-home-assistant-websocket as the right place to look

3

There seem to have been a whole slew of Home assistant issues recently. Maybe they have accidentally broken the web socket node in a recent upgrade.

4

I concur. Not only did NR crash for the first time in many years for me, but the NR UI wouldnt come up again without me disabling the HASS nodes from the commandline first.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.