Node Red websocket connection timeout

norsvn22 · April 27, 2026, 11:46am

Hi

I am running Home Assistant OS 17.2 on a rpi4 with all my automation handled by the Node-RED addon. I use the NodeRED Companion installed through HACS to handle sensors, triggers etc. between HA and NR.

For some time I have been getting error messages in NR such as “Unrecognized error 3” or “Error updating entity”. Sometimes everything works, but then these error messages re-appear.

I do not know when these errors first appeared. Most of my automations are managing energy consumption from my solar panels, so they are not regularly used during the dark winter months in Norway.

What I have tried:

Host reboot
Home Assistant is all up to date
NodeRED Palletes are the most recent version
Reinstalled both NodeRED and NodeRED Companion
Verified that I have only one HA server configured in NR.
Enabled HA server heartbeat in NR.

Error messages in NodeRED

NodeRED logs:

27 Apr 13:38:25 - [error] [ha-entity-config:Sensor Port H] Error updating entity. Error Message: 3
27 Apr 13:38:25 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
27 Apr 13:38:25 - [info] [server:Home Assistant] Connecting to http://supervisor/core
27 Apr 13:38:25 - [info] [server:Home Assistant] Connected to http://supervisor/core
27 Apr 13:38:25 - [debug] [server:Home Assistant] States Loaded
27 Apr 13:38:25 - [debug] [server:Home Assistant] Services Loaded
27 Apr 13:38:25 - [debug] [server:Home Assistant] Integration: loaded
27 Apr 13:38:25 - [debug] [ha-entity-config:sensor config for Info fra PS til HA] Registering sensor with HA
27 Apr 13:38:25 - [debug] [ha-entity-config:ev_lader_setpunkt] Registering sensor with HA
27 Apr 13:38:25 - [debug] [ha-entity-config:weather cloudyness] Registering sensor with HA
27 Apr 13:38:25 - [debug] [ha-entity-config:Port V] Registering sensor with HA
27 Apr 13:38:25 - [debug] [ha-entity-config:Sensor Port H] Registering sensor with HA
27 Apr 13:38:25 - [debug] [ha-entity-config:Solcelleproduksjon_kW] Registering sensor with HA
27 Apr 13:38:25 - [debug] [server:Home Assistant] HA State: running
27 Apr 13:38:59 - [debug] [api-call-service:Slå på vvb] Calling Service: {"domain":"light","service":"turn_on","target":{"entity_id":"light.vvbereder_light"}}
27 Apr 13:38:59 - [debug] [api-call-service:Slå av vvb.ps hjelper] Calling Service: {"domain":"input_boolean","service":"turn_off","target":{"entity_id":"input_boolean.vvb_ps_overstyring"}}
27 Apr 13:38:59 - [debug] [api-call-service:Slå av vvb overstyr hjelper] Calling Service: {"domain":"input_boolean","service":"turn_off","target":{"entity_id":"input_boolean.vvb_overstyr"}}
27 Apr 13:42:03 - [debug] [api-call-service:Deaktiver hjelper: negativ strømpris] Calling Service: {"domain":"input_boolean","service":"turn_off","target":{"entity_id":"input_boolean.negativ_strompris"}}
27 Apr 13:42:09 - [debug] [api-call-service:Soloverskudd nivå 1 PÅ] Calling Service: {"domain":"input_boolean","service":"turn_on","target":{"entity_id":"input_boolean.soloverskudd_niva_1"}}
27 Apr 13:42:09 - [debug] [api-call-service:Soloverskudd nivå 2 PÅ] Calling Service: {"domain":"input_boolean","service":"turn_on","target":{"entity_id":"input_boolean.soloverskudd_niva_2"}}
27 Apr 13:42:09 - [debug] [api-call-service:Soloverskudd nivå 3 PÅ] Calling Service: {"domain":"input_boolean","service":"turn_on","target":{"entity_id":"input_boolean.soloverskudd_niva_3"}}
27 Apr 13:43:22 - [trace] comms.close 5TBzLd9qIE7XbTiEjm0nGkBauxsU/wzxl01ZgFVDXi4=
27 Apr 13:43:22 - [trace] comms.open edxH1xIzz15zwg46jCtuigi328SZnE7wfXafq722RAw=
27 Apr 13:43:22 - [error] [ha-entity-config:Solcelleproduksjon_kW] Error updating entity. Error Message: 3
27 Apr 13:43:22 - [error] [ha-entity-config:Port V] Error updating entity. Error Message: 3
27 Apr 13:43:22 - [error] [ha-entity-config:Sensor Port H] Error updating entity. Error Message: 3
27 Apr 13:43:22 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
27 Apr 13:43:22 - [info] [server:Home Assistant] Connecting to http://supervisor/core
27 Apr 13:43:23 - [info] [server:Home Assistant] Connected to http://supervisor/core
27 Apr 13:43:23 - [debug] [server:Home Assistant] States Loaded
27 Apr 13:43:23 - [debug] [server:Home Assistant] Services Loaded
27 Apr 13:43:23 - [debug] [server:Home Assistant] Integration: loaded
27 Apr 13:43:23 - [debug] [ha-entity-config:sensor config for Info fra PS til HA] Registering sensor with HA
27 Apr 13:43:23 - [debug] [ha-entity-config:ev_lader_setpunkt] Registering sensor with HA
27 Apr 13:43:23 - [debug] [ha-entity-config:weather cloudyness] Registering sensor with HA
27 Apr 13:43:23 - [debug] [ha-entity-config:Port V] Registering sensor with HA
27 Apr 13:43:23 - [debug] [ha-entity-config:Sensor Port H] Registering sensor with HA
27 Apr 13:43:23 - [debug] [ha-entity-config:Solcelleproduksjon_kW] Registering sensor with HA
27 Apr 13:43:23 - [debug] [server:Home Assistant] HA State: running

Supervisor log:

2026-04-27 12:53:41.829 INFO (MainThread) [supervisor.host.manager] Host information reload completed

2026-04-27 13:16:19.708 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

2026-04-27 13:22:56.699 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Error WebSocket message received while proxying: TimeoutError('No PONG received after 15.0 seconds')

2026-04-27 13:22:56.703 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API closed

2026-04-27 13:23:16.194 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize

2026-04-27 13:23:16.214 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered

2026-04-27 13:23:16.225 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API proxy running

2026-04-27 13:27:56.700 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Error WebSocket message received while proxying: TimeoutError('No PONG received after 15.0 seconds')

2026-04-27 13:27:56.704 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API closed

2026-04-27 13:28:17.080 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize

2026-04-27 13:28:17.091 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered

2026-04-27 13:28:17.100 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API proxy running

2026-04-27 13:32:56.697 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Error WebSocket message received while proxying: TimeoutError('No PONG received after 15.0 seconds')

2026-04-27 13:32:56.702 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API closed

2026-04-27 13:33:22.221 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize

2026-04-27 13:33:22.228 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered

2026-04-27 13:33:22.237 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_nodered] Home Assistant WebSocket API proxy running

I seems that the connection times out every 5 minutes. This typically happens after the system have been up and running for a few hours.

I do not know if the following is relevant, but i typically also have problems installing the HA core updates as described in this thread. Core update not installing
After testing the suggested solutions, my solution has just been repeatedly starting the update until it works…

Is there anyone who might have any suggestions of what is causing this behavior?

norsvn22 · May 8, 2026, 9:50am

Any suggestions of additional information needed for this post?

Biscuit · May 8, 2026, 10:53am

The Websocket connection, established by the HA Websocket nodes HA Server, is usually very reliable.

The connection should ideally be always there, but it can close if unused for long periods [use the heartbeat option to keep it open] or if HA has an issue.

I believe (but I am certainly not an expert in this) that the Node-RED error suggests that the connection was closed unexpectedly at the HA end.

The HA error suggests that the regular HA check on the connection did not see a response, so HA assumed that the connection had failed.

Potential reasons for Websocket connection issues include having more than one HA Websocket Node Server (config node), having an (other) HA integration that is behaving badly and swamps the HA Websockets generally, or having a configuration whereby HA and Node-RED are running on different machines or in containers with a problematic connection between the two.

If, as you suggest, your HA setup is having issues connecting to the outside world for general updates, more information about your installation might be helpful to those who have greater understanding of how this "stuff" all works. If you have Node-RED running on an ESP32-S3 behind a firewall on a different network over WiFi, then yes problems will occur.

Edit

As you indicate that you have HA core, HAOS, Node-RED addon, Websocket nodes, NR Companion all up to date, only one HA Server, and presumably using "as addon" connection... the remaining suspects I suggest include: the RPi power supply, a problem with the SD card, other attached USB devices, and other integrations.