No debugging info whatosever

Problem/Motivation

All of a sudden all debug information disappeared! All the nodes seem to be working fine but they are not reporting anything within the node red web UI - neither in the right-hand side debug panel nor via status underneath each node.

Expected behavior

(What you expected to happen)

Actual behavior

No apparent trouble anywhere in the logs (e.g. core, supervisor), only these show up in the addon logs:

25 May 19:43:25 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
25 May 19:43:27 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
25 May 19:43:34 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
25 May 19:43:38 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)
25 May 19:43:43 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

System Health

version	core-2021.5.5
installation_type	Home Assistant Supervised
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.8.9
os_name	Linux
os_version	4.19.0-16-amd64
arch	x86_64
timezone	Europe/Sofia

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	5000
Installed Version	1.12.3
Stage	running
Available Repositories	890
Installed Repositories	17

AccuWeather

can_reach_server	ok
remaining_requests	15

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Debian GNU/Linux 10 (buster)
update_channel	stable
supervisor_version	supervisor-2021.04.3
docker_version	20.10.6
disk_total	108.1 GB
disk_used	33.9 GB
healthy	true
supported	true
supervisor_api	ok
version_api	ok
installed_addons	Samba share (9.3.1), Duck DNS (1.12.5), NGINX Home Assistant SSL proxy (3.0.1), File editor (5.3.0), ESPHome (1.17.1), Mosquitto broker (5.1.1), Node-RED (9.1.1), Home Assistant Google Drive Backup (0.104.3), UniFi Controller (0.20.3), deCONZ (6.9.0), Network UPS Tools (0.7.0), Glances (0.12.1), Portainer (1.5.0), AdGuard Home (4.1.6), Visual Studio Code (3.3.1), iPerf3 (0.1.0), Frigate NVR (1.13), Terminal & SSH (9.1.2)

Lovelace

dashboards	1
resources	11
views	13
mode	yaml

Spotify

api_endpoint_reachable	ok

[nibblerrick]

What exactly do you mean by «multiple “Server configurations” for the add-on»? The Node Red add-on config in HA supervisor? Can’t find any server settings there.

Haven’t been clear, sorry: In the home-assistant-websocket-nodes you can define the home-assistant-server(s). I assumed all of the people in this thread use the ha-websocket-nodes. Thinking over it that doesn’t have to be, but still seems very likely.

I think it worked a while with multiple server configurations, which where added at my site, too, when I imported other flows. If so, the problem could be a connection of this add-on and something which changed in the ha-websocket-nodes. So if this resolves the problem for more people it could be worth to commuicate this behaviour to the ha-websocket-node-author. But I think then more then one or two people need to verify that this is a thing.

@macieksonik Do you confirm that you have multiple configurations or that the problem is gone after “cleaning” the multiple configuration entries?

[mattbruman]

Fixed my issue too by deleting extra servers. Maybe this can be fixed in a future build to ignore servers with 0 nodes.