Often after Core updates Nod-Red won't remain connected to supervisor, until manually restarted. This is an occasional ongoing annoyance going back months.
After update Logs show:
10 Jan 13:10:04 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jan 13:10:04 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 Jan 13:10:04 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
10 Jan 13:10:04 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
10 Jan 13:10:09 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jan 13:10:09 - [info] [server:Home Assistant] Connected to http://supervisor/core
After noticing Nod-Red not triggering events I restart Node-Red and all in normal. until next Core-Update
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 14.0.1
You are running the latest version of this add-on.
System: Home Assistant OS 9.4 (aarch64 / odroid-n2)
Home Assistant Core: 2023.1.2
Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
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
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
s6-rc: info: service init-nginx successfully started
up to date, audited 263 packages in 3s
10 packages are looking for funding
run `npm fund` for details
7 vulnerabilities (2 moderate, 5 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
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
[13:12:58] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
10 Jan 13:13:01 - [info]
Welcome to Node-RED
===================
10 Jan 13:13:01 - [info] Node-RED version: v3.0.2
10 Jan 13:13:01 - [info] Node.js version: v18.12.1
10 Jan 13:13:01 - [info] Linux 5.15.80 arm64 LE
10 Jan 13:13:02 - [info] Loading palette nodes
10 Jan 13:13:05 - [info] Dashboard version 3.2.3 started at /endpoint/ui
10 Jan 13:13:07 - [info] Settings file : /etc/node-red/config.js
10 Jan 13:13:07 - [info] Context store : 'default' [module=memory]
10 Jan 13:13:07 - [info] User directory : /config/node-red/
10 Jan 13:13:07 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Jan 13:13:07 - [info] Flows file : /config/node-red/flows.json
10 Jan 13:13:08 - [info] Server now running at http://127.0.0.1:46836/
10 Jan 13:13:08 - [info] Starting flows
[13:13:08] INFO: Starting NGinx...
10 Jan 13:13:08 - [info] Started flows
10 Jan 13:13:13 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jan 13:13:13 - [info] [server:Home Assistant] Connected to http://supervisor/core
frenck
commented
1 year ago
Often after Core updates Nod-Red won't remain connected to supervisor, until manually restarted. This is an occasional ongoing annoyance going back months.
After update Logs show:
After noticing Nod-Red not triggering events I restart Node-Red and all in normal. until next Core-Update