Node-Red startet nicht mehr

Moin,
bin neu hier und habe da ein kleines Problem mit node-red.
Mein node-red startet nicht mehr in ha seitdem ich mir die easy e4 Erweiterungen installiert habe und auch über modbus tcp versucht habe meine easy e4 auszulesen. Aufgrund der LOG Datei denke ich das das Problem an der E4/Modbus TCP Erweiterungen liegt.
LOG
[13:30:31] INFO: Starting NGinx…
3 Sep 13:30:31 - [error] [easyE4 VAL:366e36c147f80611] Requested element is not part of cyclic request in IN node
3 Sep 13:30:31 - [error] [easyE4 VAL:366e36c147f80611] Requested element is not part of cyclic request in IN node
3 Sep 13:30:31 - [red] Uncaught Exception:
3 Sep 13:30:31 - [error] TypeError: Cannot read properties of undefined (reading ‘forEach’)
at processValues (/config/node-red/node_modules/node-red-contrib-modbustcp/modbustcp.js:342:18)
at SetupLoop (/config/node-red/node_modules/node-red-contrib-modbustcp/modbustcp.js:377:9)
at ModbusTCPRead._inputCallback (/config/node-red/node_modules/node-red-contrib-modbustcp/modbustcp.js:400:9)
at /opt/node_modules/@node-red/runtime/lib/nodes/Node.js:210:26
at Object.trigger (/opt/node_modules/@node-red/util/lib/hooks.js:166:13)
at ModbusTCPRead.Node._emitInput (/opt/node_modules/@node-red/runtime/lib/nodes/Node.js:202:11)
at ModbusTCPRead.Node.emit (/opt/node_modules/@node-red/runtime/lib/nodes/Node.js:186:25)
at ModbusTCPRead.Node.receive (/opt/node_modules/@node-red/runtime/lib/nodes/Node.js:485:10)
at Immediate. (/opt/node_modules/@node-red/runtime/lib/flows/Flow.js:831:52)
at processImmediate (node:internal/timers:476:21)

Ich hoffe jemanden hier zu finden der mir helfen kann node-red wieder zum laufen zu bringen.
Danke vorab schonmal
Gruß Rolf

Hast Du mal dein gesamtes System (Hardware) neu gestartet?

Node Red im Safe-Mode starten und das entsprechende Modul deinstallieren, oder den Flow deaktivieren.

moin, kannst Du mir auch sagen, wo ich in der Konfiguration “safe_mode: true” eintragen muss?

OK. habe es gefunden und es läuft wieder. Danke

Hallo zusammen, bin blutiger Anfänger habe irgendwann Node Red installiert lief auch, jetzt ewig nichts mehr gemacht in HA und brauche Node red aber es Startet nicht. deinstalliert und neu aufgesetzt habe ich Node Red schon. hat jemand eine idee was ich machen kann?

Protokoll:
6-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.4.5
You are running the latest version of this add-on.
System: Home Assistant OS 10.5 (amd64 / generic-x86-64)
Home Assistant Core: 2023.9.2
Home Assistant Supervisor: 2023.08.3

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-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
[18:22:39] FATAL:
[18:22:39] FATAL: SSL has been enabled using the ‘ssl’ option,
[18:22:39] FATAL: this requires a SSL certificate file which is
[18:22:39] FATAL: configured using the ‘certfile’ option in the
[18:22:39] FATAL: add-on configuration.
[18:22:39] FATAL:
[18:22:39] FATAL: Unfortunately, the file specified in the
[18:22:39] FATAL: ‘certfile’ option does not exists.
[18:22:39] FATAL:
[18:22:39] FATAL: Please ensure the certificate file exists and
[18:22:39] FATAL: is placed in the ‘/ssl/’ directory.
[18:22:39] FATAL:
[18:22:39] FATAL: In case you don’t have SSL yet, consider getting
[18:22:39] FATAL: a SSL certificate or setting the ‘ssl’ option
[18:22:39] FATAL: to ‘false’ in case you are not planning on using
[18:22:39] FATAL: SSL with this add-on.
[18:22:39] FATAL:
[18:22:39] FATAL: Check the add-on manual for more information.
[18:22:39] FATAL:
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[18:22:39] INFO: Service Node-RED exited with code 256 (by signal 15)
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

hat sich erledigt. ich habe in der YAML Datei SSL auf False gesetzt schon läufts problemlos danke

1 „Gefällt mir“

Ja, danke für den Hinweis!