Node-RED Is not working and shows entitys not found

Third party integrations Node-RED
1

Hello guys,

i was travelling in past month and everything was ok at my HA. Now, im back and my Node-RED stopped to. The issues tab says that some entities was not found. I dont know what is wrong. Someone could help me?

image
image484×1277 60.2 KB

12 Feb 17:22:14 - [error] [api-current-state:Tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.medicado_atentah
12 Feb 17:22:14 - [error] [api-call-service:Desliga Medicado Vivian] NoConnectionError
12 Feb 17:22:14 - [error] [api-current-state:Vivian tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.vivian_medicada
12 Feb 17:22:14 - [error] [api-current-state:Vivian tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.vivian_medicada
12 Feb 17:22:14 - [error] [api-call-service:Desliga Medicado Reconter] NoConnectionError
12 Feb 17:22:15 - [warn] [alexa-remote-account:1d9308ddb3959360] failed to load routines: "no body"
12 Feb 17:22:17 - [error] [proxmox-server:c1a9f33ff5a65eaa] Failed to connect to Proxmox
12 Feb 17:22:17 - [error] [proxmox-server:c1a9f33ff5a65eaa] StatusCodeError: 401 - {"data":null}
Unhandled rejection ReferenceError: response is not defined
    at /config/node_modules/node-red-contrib-proxmox/proxmox/proxmox-server.js:73:47
    at tryCatcher (/config/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/config/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/config/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/config/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/config/node_modules/bluebird/js/release/promise.js:725:18)
    at _drainQueueStep (/config/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/config/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/config/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues (/config/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:491:21)
12 Feb 17:22:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core
12 Feb 17:22:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core
12 Feb 17:22:19 - [info] [server:Home Assistant] Connected to http://supervisor/core
12 Feb 17:22:19 - [info] [server:Home Assistant] Connected to http://supervisor/core
12 Feb 17:22:32 - [error] [api-current-state:Temperatura do CPU Proxmox] InputError: Entity could not be found in cache for entityId: sensor.proxmox_cpu_temperature
12 Feb 17:22:41 - [error] [api-current-state:Temperatura do CPU Proxmox] InputError: Entity could not be found in cache for entityId: sensor.proxmox_cpu_temperature
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[17:23:00] 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 init-nginx successfully stopped
12 Feb 17:23:00 - [info] Stopping flows
12 Feb 17:23:00 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
12 Feb 17:23:00 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
12 Feb 17:23:00 - [info] Stopped flows
[17:23:01] INFO: Service Node-RED exited with code 0 (by signal 0)
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
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: 19.0.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.2.2
 Home Assistant Supervisor: 2025.02.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
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 318 packages in 16s
62 packages are looking for funding
  run `npm fund` for details
25 vulnerabilities (5 low, 11 moderate, 9 high)
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.
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:22] 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 17:23:24 - [info] 
Welcome to Node-RED
===================
12 Feb 17:23:24 - [info] Node-RED version: v4.0.8
12 Feb 17:23:24 - [info] Node.js  version: v22.11.0
12 Feb 17:23:24 - [info] Linux 6.6.73-haos x64 LE
12 Feb 17:23:24 - [info] Loading palette nodes
12 Feb 17:23:25 - [info] Node-RED Contrib Theme Collection version: v4.0.11
12 Feb 17:23:26 - [info] node-red-contrib-telegrambot version: v16.1.2
12 Feb 17:23:28 - [info] Dashboard version 3.6.5 started at /endpoint/ui
(node:334) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
12 Feb 17:23:29 - [info] node-red-contrib-home-assistant-websocket v0.75.0 nodes initialized
12 Feb 17:23:29 - [info] Settings file  : /etc/node-red/config.js
12 Feb 17:23:29 - [info] Context store  : 'default' [module=memory]
12 Feb 17:23:29 - [info] User directory : /config/
12 Feb 17:23:29 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Feb 17:23:29 - [info] Flows file     : /config/flows.json
12 Feb 17:23:29 - [info] Server now running at http://127.0.0.1:46836/
12 Feb 17:23:29 - [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 17:23:29 - [info] Starting flows
12 Feb 17:23:29 - [warn] [telegram bot:54e282a1aafddfe8] Aborting: Token of Octopus is not set
[17:23:29] INFO: Starting NGinx...
nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /etc/nginx/servers/direct.conf:3
12 Feb 17:23:29 - [error] [ha-sensor:8cde7329121d669f] Error: Invalid entity config
12 Feb 17:23:29 - [error] [ha-sensor:46bd6a6bbf637137] Error: Invalid entity config
12 Feb 17:23:29 - [error] [ha-sensor:c1651e31460ae28a] Error: Invalid entity config
12 Feb 17:23:29 - [error] [ha-sensor:d0090dd2a9541423] Error: Invalid entity config
12 Feb 17:23:29 - [error] [ha-sensor:c35bd9d3ac2a4e41] Error: Invalid entity config
12 Feb 17:23:29 - [warn] [telegrambot-notify:Avisa Telegram] bot not initialized
12 Feb 17:23:29 - [warn] [telegrambot-notify:Avisa Telegram] bot not initialized
12 Feb 17:23:29 - [info] Started flows
12 Feb 17:23:29 - [info] [alexa-remote-account:1d9308ddb3959360] intialising with the PROXY method and saved data...
12 Feb 17:23:29 - [error] [api-call-service:Desliga Medicado Atentah] NoConnectionError
12 Feb 17:23:29 - [error] [api-current-state:Tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.medicado_atentah
12 Feb 17:23:29 - [error] [api-current-state:Tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.medicado_atentah
12 Feb 17:23:29 - [error] [api-current-state:Tomou os Remédios?] InputError: Entity could not be found in cache for entityId: input_boolean.medicado_atentah
12 Feb 17:23:29 - [error] [api-call-service:Desliga Medicado Vivian] NoConnectionError
2

Look in developer tools → states and see if the entities are there. Possibly with a _2 suffix?

3

No, the entities name still the same:

image
image1237×566 23.2 KB

image

for any reason, Node-RED cant reach.

4

“switch.fan_do_rack” and “switch.fan_do_rack_local” are different entities.

5

You appear to have two Home Assistant servers (configuration nodes). One has 125 nodes using it, the other 16. You should only have the one HA server node.

This may not be the main cause, but it certainly does not help. Two HA servers will compete and may block the WebSocket connection (hence some of your entities will not be found).

6

Thank you! I just realize that my LocalTuya is not configured.

7

Yes! How can i unify both?

8

HA tab. Server list.

Click on the second entry, disable the server config.

Double click on the number 16 on the second entry. Brings up a list of the connected nodes. Edit each in turn, and change the Server to the correct one.

Deploy

Delete the second Server node when number of connecting nodes is 0

9

Thank you!