Something wrong in the integration

Third party integrations Node-RED
1

HA: core-2024.11.2
NR: 18.1.1
node-red-contrib-home-assistant-websocket: 0.74.2

I have a lot of entities, and they are readily available inside node-red.

But every time I deploy og restart I see this in the logs:

20 Nov 17:11:42 - [info] [server:KF Home Assistant] Connecting to http://supervisor/core
20 Nov 17:11:42 - [info] [mqtt-broker:HA MQTT] Connected to broker: node-red@mqtt://172.30.32.1:1883
20 Nov 17:11:43 - [error] [api-current-state:Christmas time?] InputError: Entity could not be found in cache for entityId: input_select.season
20 Nov 17:11:43 - [error] [api-current-state:Anybody home?] InputError: Entity could not be found in cache for entityId: binary_sensor.familien
20 Nov 17:11:43 - [error] [api-current-state:Is window closed?] InputError: Entity could not be found in cache for entityId: binary_sensor.bedroom_window_contact
20 Nov 17:11:43 - [error] [api-current-state:Is window closed?] InputError: Entity could not be found in cache for entityId: binary_sensor.office_window_contact
20 Nov 17:11:43 - [error] [api-current-state:Is window closed?] InputError: Entity could not be found in cache for entityId: binary_sensor.livingroom_small_window_contact
20 Nov 17:11:43 - [error] [api-current-state:Is window closed?] InputError: Entity could not be found in cache for entityId: binary_sensor.livingroom_big_window_contact
20 Nov 17:11:43 - [error] [api-current-state:Is window closed?] InputError: Entity could not be found in cache for entityId: binary_sensor.adrian_window_contact
20 Nov 17:11:43 - [error] [api-current-state:Get season] InputError: Entity could not be found in cache for entityId: input_select.season
20 Nov 17:11:43 - [info] [server:KF Home Assistant] Connected to http://supervisor/core

And I see these messages in the debug:

20.11.2024 16.51.01[node: Anybody home?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error

"InputError: Entity could not be found in cache for entityId: binary_sensor.familien"

20.11.2024 16.51.01[node: Is window closed?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error

"InputError: Entity could not be found in cache for entityId: binary_sensor.bedroom_window_contact"

20.11.2024 16.51.01[node: Is window closed?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error
"InputError: Entity could not be found in cache for entityId: binary_sensor.office_window_contact"

20.11.2024 16.51.01[node: Is window closed?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error
InputError: Entity could not be found in cache for entityId: binary_sensor.livingroom_small_window_contact"

20.11.2024 16.51.01[node: Is window closed?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error
"InputError: Entity could not be found in cache for entityId: binary_sensor.livingroom_big_window_contact"

20.11.2024 16.51.01[node: Is window closed?](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error
"InputError: Entity could not be found in cache for entityId: binary_sensor.adrian_window_contact"

20.11.2024 16.51.01[node: Get season](https://homeassistant.fribert.dk:8123/api/hassio_ingress/M2fPmHuXm55nC72lSBcdwSymd5LdAlCHSvWopjoITpY/#)msg : error
"InputError: Entity could not be found in cache for entityId: input_select.season"

The entities are available in nodes, and they spelled correctly, so what’s up?

2

Are you using the NodeRed Addon in HomeAssistant?

I’m running NodeRed in docker container on a separate machine and using the websocket nodes to connect to HomeAssistant via REST API with a longterm key.

Since I upgraded HA from 2024.11.1 to 2024.11.3, NodeRed is unable to connect to HA.

3

I’ve found the culprit for me, it was a bad powersupply, that then didn’t power the fans in the rack, that in turn then overloaded the rack in the NUC, which failed, leading to thermal throttle.
After fixing the fan in the NUC, it’s all back to normal.