Hallo
Ich habe Node Red auf die neueste Version aktualisiert. Wenn Ich jetzt in Seitenleiste auf Node Red klicke werden die Nodes in den Flows geladen. Wenn alles geladen ist fängt das Ganze wieder von vorne an. Kann ich etwas machen, dass die Flows nicht immer wieder geladen werden?
Hier noch die Einträge aus dem Log:
Ich habe Node Red auf die neueste Version aktualisiert. Wenn Ich jetzt in Seitenleiste auf Node Red klicke werden die Nodes in den Flows geladen. Wenn alles geladen ist fängt das Ganze wieder von vorne an. Kann ich etwas machen, dass die Flows nicht immer wieder geladen werden?
Hier noch die Einträge aus dem Log:
Code:
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
-----------------------------------------------------------
App: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
App version: 21.0.0
You are running the latest version of this app.
System: Home Assistant OS 17.0 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2026.2.1
Home Assistant Supervisor: 2026.02.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
s6-rc: info: service init-nginx successfully started
up to date, audited 129 packages in 2s
25 packages are looking for funding
run `npm fund` for details
4 vulnerabilities (1 low, 3 high)
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.
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
[12:29:55] 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
12 Feb 12:29:56 - [info]
Welcome to Node-RED
===================
12 Feb 12:29:56 - [info] Node-RED version: v4.1.4
12 Feb 12:29:56 - [info] Node.js version: v24.13.0
12 Feb 12:29:56 - [info] Linux 6.12.47-haos-raspi arm64 LE
12 Feb 12:29:56 - [info] Loading palette nodes
12 Feb 12:29:56 - [info] Node-RED Contrib Theme Collection version: v4.1.1
12 Feb 12:29:57 - [info] node-red-contrib-shelly version: v11.7.4
12 Feb 12:29:58 - [info] Dashboard version 3.6.6 started at /endpoint/ui
12 Feb 12:29:58 - [info] node-red-contrib-home-assistant-websocket v0.80.3 nodes initialized
12 Feb 12:29:58 - [info] Settings file : /etc/node-red/config.js
12 Feb 12:29:58 - [info] Context store : 'default' [module=memory]
12 Feb 12:29:58 - [info] User directory : /config/
12 Feb 12:29:58 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Feb 12:29:58 - [info] Flows file : /config/flows.json
12 Feb 12:29:58 - [info] Server now running at http://127.0.0.1:46836/
12 Feb 12:29:58 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
12 Feb 12:29:58 - [info] Starting flows
12 Feb 12:29:59 - [info] Started flows
12 Feb 12:29:59 - [info] [server:Home Assistant] Connecting to http://supervisor/core
12 Feb 12:29:59 - [info] [server:Home Assistant] Connected to http://supervisor/core
[12:29:59] INFO: Starting NGinx...
12 Feb 12:30:04 - [info] [server:Home Assistant] Connecting to http://supervisor/core
12 Feb 12:30:04 - [info] [server:Home Assistant] Connected to http://supervisor/core