I’m losing my mind here, updating to 18.1.x breaks node red for me. Rolling back fixes it but I rather not be stuck on an older version
After installing it asks me to update my connection:
And after there’s no connection between HA and Node Red
Here’s the logs:
17 packages are looking for funding
run `npm fund` for details
5 high severity vulnerabilities
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
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
[23:49: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
7 Oct 23:50:00 - [info]
Welcome to Node-RED
===================
7 Oct 23:50:00 - [info] Node-RED version: v4.0.3
7 Oct 23:50:00 - [info] Node.js version: v18.20.4
7 Oct 23:50:00 - [info] Linux 6.6.46-haos x64 LE
7 Oct 23:50:00 - [info] Loading palette nodes
7 Oct 23:50:00 - [info] Node-RED Contrib Theme Collection version: v4.0.10
7 Oct 23:50:01 - [info] Dashboard version 3.6.5 started at /endpoint/ui
7 Oct 23:50:02 - [info] node-red-contrib-home-assistant-websocket v0.73.0 nodes initialized
7 Oct 23:50:02 - [info] Settings file : /etc/node-red/config.js
7 Oct 23:50:02 - [info] Context store : 'default' [module=memory]
7 Oct 23:50:02 - [info] User directory : /config/
7 Oct 23:50:02 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Oct 23:50:02 - [info] Flows file : /config/flows.json
7 Oct 23:50:02 - [info] Server now running at http://127.0.0.1:46836/
7 Oct 23:50:02 - [info] Starting flows
7 Oct 23:50:02 - [info] Started flows
[23:50:02] INFO: Starting NGinx...
7 Oct 23:50:02 - [info] [server:HASS] Connecting to http://supervisor/core
7 Oct 23:50:02 - [info] [server:HASS] Connected to http://supervisor/core
7 Oct 23:50:04 - [error] [api-call-service:AI Camera Light on] NoConnectionError
7 Oct 23:50:07 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Oct 23:50:07 - [info] [server:Home Assistant] Connected to http://supervisor/core
The problem is not that you are not connected, it’s that you’re connected to 2 servers. Above the debug window choose home assistant. Expand the server section. There will be 2 servers 1 needs to be removed.
Thanks for the reply, unfortunately that did not correct the issue.
Fixed the nodes that were imported, so there is only one connection showing in node red
example
New logs:
17 packages are looking for funding
run `npm fund` for details
5 high severity vulnerabilities
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
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
[00:06:58] 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
9 Oct 00:06:59 - [info]
Welcome to Node-RED
===================
9 Oct 00:06:59 - [info] Node-RED version: v4.0.3
9 Oct 00:06:59 - [info] Node.js version: v18.20.4
9 Oct 00:06:59 - [info] Linux 6.6.46-haos x64 LE
9 Oct 00:06:59 - [info] Loading palette nodes
9 Oct 00:06:59 - [info] Node-RED Contrib Theme Collection version: v4.0.10
9 Oct 00:07:00 - [info] Dashboard version 3.6.5 started at /endpoint/ui
9 Oct 00:07:01 - [info] node-red-contrib-home-assistant-websocket v0.73.0 nodes initialized
9 Oct 00:07:01 - [info] Settings file : /etc/node-red/config.js
9 Oct 00:07:01 - [info] Context store : 'default' [module=memory]
9 Oct 00:07:01 - [info] User directory : /config/
9 Oct 00:07:01 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Oct 00:07:01 - [info] Flows file : /config/flows.json
9 Oct 00:07:01 - [info] Server now running at http://127.0.0.1:46836/
9 Oct 00:07:01 - [info] Starting flows
9 Oct 00:07:01 - [info] Started flows
[00:07:01] INFO: Starting NGinx...
9 Oct 00:07:03 - [error] [api-call-service:AI Camera Light on] NoConnectionError
9 Oct 00:07:06 - [info] [server:Home Assistant] Connecting to http://supervisor/core
9 Oct 00:07:06 - [info] [server:Home Assistant] Connected to http://supervisor/core
9 Oct 00:07:49 - [info] Stopping modified flows
9 Oct 00:07:49 - [info] Stopped modified flows
9 Oct 00:07:49 - [info] Updated flows
9 Oct 00:07:49 - [info] Starting modified flows
9 Oct 00:07:51 - [info] Started modified flows
Well, after backing up, restoring, backing up, restoring and playing around I can say it’s something to do with node-red-contrib-home-assistant-websocket.
For whatever reason, my 18.0.5 install of node red has node-red-contrib-home-assistant-websocket version 0.65.1 installed, updating to 18.1.1 installs websocket to 0.73.0 and it doesn’t like it.
