Richy22B
commented
1 month ago Node Red has worked perfectly for years but I'm getting a similar issue which is preventing flows working. Like you said, restarting Node Red allows it to work for a while but then mine crashes again.
My Log...
Add-on: Node-RED Flow-based programming for the Internet of Things
Add-on version: 18.0.4 You are running the latest version of this add-on. System: Home Assistant OS 12.4 (amd64 / generic-x86-64) Home Assistant Core: 2024.8.1 Home Assistant Supervisor: 2024.08.0
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 Log level is set to NOTICE 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 358 packages in 2s
80 packages are looking for funding
run npm fund for details
15 high severity vulnerabilities
To address issues that do not require attention, run: npm audit fix
To address all issues possible (including breaking changes), run: npm audit fix --force
Some issues need review, and may require choosing a different dependency.
Run npm audit for details.
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.8.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
npm notice To update run: npm install -g npm@10.8.2
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
s6-rc: info: service legacy-services successfully started
start node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
11 Aug 18:58:13 - [info]
Welcome to Node-RED
11 Aug 18:58:13 - [info] Node-RED version: v4.0.2 11 Aug 18:58:13 - [info] Node.js version: v18.20.3 11 Aug 18:58:13 - [info] Linux 6.6.33-haos x64 LE 11 Aug 18:58:13 - [info] Loading palette nodes 11 Aug 18:58:13 - [info] Node-RED Contrib Theme Collection version: v4.0.7 11 Aug 18:58:14 - [info] Dashboard version 3.6.5 started at /endpoint/ui 11 Aug 18:58:14 - [info] Settings file : /etc/node-red/config.js 11 Aug 18:58:14 - [info] Context store : 'default' [module=memory] 11 Aug 18:58:14 - [info] User directory : /config/ 11 Aug 18:58:14 - [warn] Projects disabled : editorTheme.projects.enabled=false 11 Aug 18:58:14 - [info] Flows file : /config/flows.json 11 Aug 18:58:14 - [info] Server now running at http://xxxxxxxxxxxxxxxx/ 11 Aug 18:58:14 - [info] Starting flows 11 Aug 18:58:14 - [info] Started flows 11 Aug 18:58:14 - [error] [api-current-state:Is Sentry Mode On?] InputError: Entity could not be found in cache for entityId: switch.bfg_sentry_mode 11 Aug 18:58:14 - [error] [api-current-state:Open Plan Motion] InputError: Entity could not be found in cache for entityId: binary_sensor.shellymotionsensor_60a423872950_motion 11 Aug 18:58:14 - [error] [api-call-service:Turn Off Someone Was Home] NoConnectionError 11 Aug 18:58:14 - [error] [api-current-state:Logan Bedroom Temp] InputError: Entity could not be found in cache for entityId: climate.logans_thermostat 11 Aug 18:58:14 - [error] [api-current-state:Was Someone At Home Today?] InputError: Entity could not be found in cache for entityId: input_boolean.someone_was_home_today 11 Aug 18:58:14 - [error] [api-current-state:What Is Temp Top Of Buffer?] InputError: Entity could not be found in cache for entityId: sensor.shellyplus2pm_c049ef8662b4_temperature_3 11 Aug 18:58:14 - [error] [api-current-state:Solar Peak Today] InputError: Entity could not be found in cache for entityId: sensor.power_highest_peak_time_today 11 Aug 18:58:14 - [error] [api-current-state:Solar Peak Tomorrow] InputError: Entity could not be found in cache for entityId: sensor.power_highest_peak_time_tomorrow 11 Aug 18:58:14 - [error] [api-current-state:Heat Pump Heating Status] InputError: Entity could not be found in cache for entityId: binary_sensor.stiebel_eltron_isg_is_heating 11 Aug 18:58:14 - [error] [api-current-state:Is Hot Water On?] InputError: Entity could not be found in cache for entityId: binary_sensor.stiebel_eltron_isg_is_heating_boiler 11 Aug 18:58:14 - [error] [api-current-state:Is Heating On?] InputError: Entity could not be found in cache for entityId: binary_sensor.stiebel_eltron_isg_is_heating 11 Aug 18:58:14 - [error] [api-current-state:3pm Temp Lock] InputError: Entity could not be found in cache for entityId: input_boolean.3pm_temp_lock 11 Aug 18:58:14 - [error] [api-current-state:Outside Light Relay] InputError: Entity could not be found in cache for entityId: switch.shelly1_e8db84ab5efc 11 Aug 18:58:14 - [error] [api-current-state:Shelly PV Output] InputError: Entity could not be found in cache for entityId: sensor.shellyem_c45bbe796c9a_channel_1_power 11 Aug 18:58:16 - [error] [api-current-state:Buffer Target Temp] InputError: Entity could not be found in cache for entityId: sensor.stiebel_eltron_isg_target_temperature_buffer 11 Aug 18:58:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core 11 Aug 18:58:19 - [info] [server:Home Assistant] Connected to http://supervisor/core
fspuhler
lucode
Problem/Motivation
I have no idea why the communication between HA and Node Red is suddenly so slow, that it takes some times more then 3 seconds to execute a service call.
Expected behavior
Normally this should happen in milliseconds.
Actual behavior
The service call stays for seconds in sending mode:
The App consumes a lot of CPU power 40-55%
I switched to warn mode in the logs and see that that are many missing cache entries for entities. I guess that might be the problem, but I don't now how to clear the cache. Restarting does not help in my case.
https://community.home-assistant.io/t/refresh-node-red-entities-cache/218466
Steps to reproduce
Unfortunately I have no idea how to reproduce it.
Proposed changes
Sometimes it helps a bit for a certain period to restart Node-Red.
Logs