Tons of errors in Node Red log

Third party integrations Node-RED
1

I’m seeing LOADS of these errors in the Supervisor > Node-RED logs. It also seems to be running very slowly. What’s going on here?

14 Jul 14:30:39 - [info] [server:Home Assistant] Connecting to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connecting to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connecting to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connecting to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connecting to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to http://supervisor/core
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to http://supervisor/core
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [info] [server:Home Assistant] Connected to undefined
14 Jul 14:30:39 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:30:43 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:30:45 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:30:51 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:30:55 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:30:59 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:31:03 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:31:05 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:32:35 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:32:45 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
14 Jul 14:32:47 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
2

Have you tried to restart node red?

3

Yep. As well as the VM itself.

4

Actually I just noticed that the errors were gone overnight. However, I left a NR tab open this morning and the errors are back.

Could an idle tab somehow be the cause of the errors?

5

It seems that it may have been related to this

A lot of “Connecting to …” logs each 5 seconds from node red · Issue #430 · zachowj/node-red-contrib-home-assistant-websocket (github.com)

I had a ton of servers (I think from importing other people’s JSON?). Once I removed them all and updated nodes, I think it’s better now.

2 Likes