I have a problem with my node red addon. I does not start anymore and i dont know why. Does anyone have a hint? Here the Log:
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (amd64 / generic-x86-64)
Home Assistant Core: 2024.2.2
Home Assistant Supervisor: 2024.01.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 145 packages in 3s
21 vulnerabilities (5 moderate, 14 high, 2 critical)
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.2.3 → 10.4.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.4.0
npm notice Run npm install -g [email protected] to update!
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
[17:23:12] 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
19 Feb 17:23:13 - [info]
Welcome to Node-RED
19 Feb 17:23:13 - [info] Node-RED version: v3.1.5
19 Feb 17:23:13 - [info] Node.js version: v18.19.0
19 Feb 17:23:13 - [info] Linux 6.1.74-haos x64 LE
19 Feb 17:23:13 - [info] Loading palette nodes
19 Feb 17:23:14 - [info] Node-RED Contrib Theme Collection version: v3.1.9
19 Feb 17:23:14 - [info] Dashboard version 3.6.2 started at /endpoint/ui
19 Feb 17:23:15 - [info] Settings file : /etc/node-red/config.js
19 Feb 17:23:15 - [info] Context store : ‘default’ [module=memory]
19 Feb 17:23:15 - [info] User directory : /config/
19 Feb 17:23:15 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Feb 17:23:15 - [info] Flows file : /config/flows.json
19 Feb 17:23:15 - [info] Server now running at http://127.0.0.1:46836/
19 Feb 17:23:15 - [info] Starting flows
19 Feb 17:23:15 - [info] Started flows
[17:23:15] INFO: Starting NGinx…
19 Feb 17:23:17 - [error] [api-call-service:45e04beedca3e891] NoConnectionError
19 Feb 17:23:17 - [error] [api-current-state:4adb80e.556bf8] InputError: Entity could not be found in cache for entityId: input_boolean.poolcontrol
19 Feb 17:23:17 - [error] [api-current-state:Prüfung Regen] InputError: Entity could not be found in cache for entityId: weather.home
19 Feb 17:23:18 - [red] Uncaught Exception:
19 Feb 17:23:18 - [error] Error: Huejay: connect EHOSTUNREACH 192.168.1.117:80
at /config/node_modules/huejay/lib/Transport.js:106:15
at processTicksAndRejections (node:internal/process/task_queues:95:5)
[17:23:18] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[17:23:18] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nginx successfully stopped
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
Supervisor:
24-02-19 17:24:55 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:24:55 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:25:06 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting…
24-02-19 17:25:06 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
24-02-19 17:25:06 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:25:06 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:25:06 WARNING (MainThread) [supervisor.addons.options] Option ‘dark_mode’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:25:06 WARNING (MainThread) [supervisor.addons.options] Option ‘require_ssl’ does not exist in the schema for Node-RED (a0d7b954_nodered)
24-02-19 17:25:06 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on Package node-red/amd64 · GitHub with version