search

hassio-addons / addon-node-red

Node-RED - Home Assistant Community Add-ons
https://addons.community
MIT License
539 stars 125 forks source link

No debugging info whatosever #1029

Closed dedepene closed 2 years ago

dedepene commented 3 years ago

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 -- | --
gterpstra75 commented 3 years ago

I have the same issue. I rolled back 1 week and everything worked fine.

dedepene commented 3 years ago

I have the same issue. I rolled back 1 week and everything worked fine.

no such luck here as I accidentally deleted my snaphots. Did you restore just node red or the entire snapshot?

Also, in my case I can get it properly showing debugging if I reach the web ui through the configured port in a separate browser tab. Did you try this?

gterpstra75 commented 3 years ago

Did you restore just node red or the entire snapshot?

Actually, I am running HA on a VM under Proxmox with automatic backups. I just restored one of the earlier VMs. I initially tried the last one but still had the issue so I picked one where NodeRed was at version 9.0.1. This is one of the many advantages of running HA on Proxmox.

dedepene commented 3 years ago

So when I run node-red in a separate browser tab through the config port, I seem to get superhigh CPU usage on account of the nodered container. The processes inside the container is listed here:

image

Also, this time around I'm getting the supervisor log spammed with these :

21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:57 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:58 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:16:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-06-01 10:17:01 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
JackoAmmerlaan commented 3 years ago

I had a smiliair issue socket error and most of the time no debug info. (yes sometimes briefly debug/status was displayed). I solved it partly by entering a port number in the network part of the add-on (used port 1880). after restarting. After wich I direct connect to node red <http://192,168.x.x:1880) logon with your home assistant password. When starting node-red inside home assistant no debug info...

dedepene commented 3 years ago

I had a smiliair issue socket error and most of the time no debug info. (yes sometimes briefly debug/status was displayed). I solved it partly by entering a port number in the network part of the add-on (used port 1880). after restarting. After wich I direct connect to node red <http://192,168.x.x:1880) logon with your home assistant password. When starting node-red inside home assistant no debug info...

This is precisely what I'm doing for the moment - loading node red in a separate browser via the port I opened in config. Still, this is only a workaround, and also started getting these massive CPU overloads on account of the node-red container.

I wonder if anyone is actually looking into this?

kwalkington commented 3 years ago

I am doing the same thing. Direct connect for now. I've updated everything and even uninstalled and reinstalled node red.

squireblackdens commented 3 years ago

Same issue here

mamos76 commented 3 years ago

I have the same problem. node red 9.1.3

matbrewer396 commented 3 years ago

same problem, on version 9.1.3

mamos76 commented 3 years ago

updated to version 9.1.4 the problem remains the same

nibblerrick commented 3 years ago

Same here, but as far as I take the changelog there isn't a specific update to this issue, more a general update, as different containers of the communityaddons where updated.

dedepene commented 3 years ago

I can also confirm 9.1.4 did not fix the issue.

Zkaning commented 3 years ago

Have the same problem. Latest config 9.1.4

JackoAmmerlaan commented 3 years ago

Issue still exists in 9.14. Also seeing huge CPU spikes (>26%) and during the spikes most flows are slow and lagging. If the CPU is running normal (<6%) all flows works perfect. Running on a nuc celeron j3455

th00mas88 commented 3 years ago

Yep same issue as everyone else.

I removed the add-on and folders, rebuilt and have at least the connection. But it failed to run and run debug. The connection and "visual" only worked in the app. The debug doesn't work at all.

I had a similar issue a while back also, I'm not sure if that was related to update or not. But that absolutely is. It worked until update.

Edit - This is running supervisor on a pi4 4gb

JackoAmmerlaan commented 3 years ago

Since I have several Home Assistannt instances running I decided to Install Node Red on my PI. (Same version's as on the NUC). And to my suprise debug and status worked...

dedepene commented 3 years ago

Since I have several Home Assistannt instances running I decided to Install Node Red on my PI. (Same version's as on the NUC). And to my suprise debug and status worked...

So where does that take us? Something else is breaking node-red?

gterpstra75 commented 3 years ago

Interesting. Is everyone with issues running on a NUC and could this somehow be causing the problem? My setup is using a NUC running with HA running on a VM under proxmox. I now have a Synology NAS where I could easily install HA for testing purposes.

dedepene commented 3 years ago

Interesting. Is everyone with issues running on a NUC and could this somehow be causing the problem? My setup is using a NUC running with HA running on a VM under proxmox. I now have a Synology NAS where I could easily install HA for testing purposes.

I'm on bare-metal x64 thin client, no virtualization whatsoever.

th00mas88 commented 3 years ago

I spent an AGE dealing with, I had this issue before or similar so tired again and it worked.

Make a copy of your flows. uninstall nodered Remove ALL nodered files - EVERYTHING Reboot Install nodered again but NOT using the "i use the homeassistant add on" using the IP and a token. reconfigure all the dam nodes (im sure there is a faster way but i dont have many flows to deal with) It's the only way I could get it working at all

Also in a bizarre way the nodered portal app I can see debug info , but not on chrome

JackoAmmerlaan commented 3 years ago

Interesting. Is everyone with issues running on a NUC and could this somehow be causing the problem? My setup is using a NUC running with HA running on a VM under proxmox. I now have a Synology NAS where I could easily install HA for testing purposes.

I am running W10 with HA in hyper-V.

JackoAmmerlaan commented 3 years ago

I spent an AGE dealing with, I had this issue before or similar so tired again and it worked.

Make a copy of your flows. uninstall nodered Remove ALL nodered files - EVERYTHING Reboot Install nodered again but NOT using the "i use the homeassistant add on" using the IP and a token. reconfigure all the dam nodes (im sure there is a faster way but i dont have many flows to deal with) It's the only way I could get it working at all

Also in a bizarre way the nodered portal app I can see debug info , but not on chrome

Will try this solution and post the outcome.

JackoAmmerlaan commented 3 years ago

Indeed removing node red also the directory located under config. Reboot and reinstall did the job .... for 5 minutes and then the debug/status info disappeared again. ..

.. A little but too fast... Updated the Home Assistant flow (as described by Th00mas88) and restarted node red. (debug/status appeared and stayed .. Yess).. Also CPU is back to normal again (5-9%)

th00mas88 commented 3 years ago

Indeed removing node red also the directory located under config. Reboot and reinstall did the job .... for 5 minutes and then the debug/status info disappeared again. ..

.. A little but too fast... Updated the Home Assistant flow (as described by Th00mas88) and restarted node red. (debug/status appeared and stayed .. Yess).. Also CPU is back to normal again (5-9%)

It's now been 12 ? 36 hours since I did it and got all working.

It still seems I'm missing debug in chrome but on the app it's there

R5fan commented 3 years ago

Same issue here. Running HAOS under proxmox on x64

gterpstra75 commented 3 years ago

OK, I used a modified @th00mas88 method to upgrade my Node-Red to the latest version:

I used the homeassistant addon. I did this two days ago.

kxqcvl commented 3 years ago

I have the same issue since a couple of weeks, running NR 9.2.0 i noticed some flows responding very slow. When i open NR and looked what caused it i noticed allot "call service" nodes are stuck at sending test with and without server token

All ready tried to completley removed node red and install again but now on server with token, worked for an hour or so but things got worse. Now i'm back on "i use the add_on" and couple times a day the delays are serval minutes.

delay

Allready started over twice this weekend but no luck, flows are still lagging cause status keeps beeing stuck at sending so allot of flows don't work anymore. Any idea?

MagicMountainMan commented 3 years ago

I am also experiencing this same issue. I might migrate out of the HASSIO addon for Node Red and just install it as a Docker anyway, but this is kind of a bummer.

MagicMountainMan commented 3 years ago

I had a smiliair issue socket error and most of the time no debug info. (yes sometimes briefly debug/status was displayed). I solved it partly by entering a port number in the network part of the add-on (used port 1880). after restarting. After wich I direct connect to node red <http://192,168.x.x:1880) logon with your home assistant password. When starting node-red inside home assistant no debug info...

This worked for me so this error must have something to do with the way Home Assistant/Node-Red is handling ingress.

I usually work on Node-Red remotely though via ingress and Nabu Casa so it is still a problem that needs a solution.

frenck commented 3 years ago

Is this happening in a specific browser?

I am not able to reproduce this at all (however, I am on dev)

MagicMountainMan commented 3 years ago

I'm on Chrome, however everything randomly came back. I don't know how to reproduce it now either.

frenck commented 3 years ago

If it happens, is there anything in the browser console?

MagicMountainMan commented 3 years ago

I'm getting

DevTools failed to load source map: Could not parse content for https://xxx.ui.nabu.casa/a0d7b954_nodered/gridstack.min.map: Unexpected token < in JSON at position 0

But the node statuses and debugging do end up popping up. So far I can't reproduce the same issue that I did have as they do populate within a few seconds now.

Edit: Also this as it's loading Node-Red, but it loads fine.

DevTools failed to load source map: Could not load content for https://xxx.ui.nabu.casa/api/hassio_ingress/r-xxx/vendor/purify.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
frenck commented 3 years ago

missing source maps is fine and would not be able to cause this.

MagicMountainMan commented 3 years ago

I figured. If I'm able to reproduce I will post the console log.

MagicMountainMan commented 3 years ago

I am getting this error now that I have been able to reproduce the issue:

Uncaught Error: cannot call methods on editableList prior to initialization; attempted to call method 'addItem'
    at Function.error (vendor.js:2)
    at HTMLOListElement.<anonymous> (vendor.js:10)
    at Function.each (vendor.js:2)
    at s.fn.init.each (vendor.js:2)
    at s.fn.init.t.fn.<computed> [as editableList] (vendor.js:10)
    at l (red.min.js:16)
    at red.min.js:16

as well as

The main 'lit-element' module entrypoint is deprecated. Please update your imports to use the 'lit' package: 'lit' and 'lit/decorators.ts' or import from 'lit-element/lit-element.ts'.

but I'm not sure the second one is relevant at all.

MagicMountainMan commented 3 years ago

This issue is happening pretty consistently for me again. I'm on the latest version of Home Assistant and the latest version of this add-on.

kxqcvl commented 3 years ago

Here also

mattbruman commented 3 years ago

Add me to the list of effected

Running on a W10 VirtualBox Latest Version of everything Tried on Brave, Chrome, and Edge

macieksonik commented 3 years ago

Same here. After reboot of the system node statuses and debug info are gone.

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment šŸ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

MagicMountainMan commented 3 years ago

It's still an issue, I've just given up and now access Node-Red either via VPN or a personal subdomain.

kxqcvl commented 3 years ago

Here also still problems

frenck commented 3 years ago

@MagicMountainMan If this:

Uncaught Error: cannot call methods on editableList prior to initialization; attempted to call method 'addItem'
    at Function.error (vendor.js:2)
    at HTMLOListElement.<anonymous> (vendor.js:10)
    at Function.each (vendor.js:2)
    at s.fn.init.each (vendor.js:2)
    at s.fn.init.t.fn.<computed> [as editableList] (vendor.js:10)
    at l (red.min.js:16)
    at red.min.js:16

is the source/root cause of the issue, it isn't an add-on problem, but it originates from Node-RED itself (or might be induced by one of the Nodes). From an add-on perspective, there is nothing I can do or fix about that.

Add-ons provide a runtime for an application to run in/on. We don't create/maintain/change the application itself.

MagicMountainMan commented 3 years ago

@frenck Fair enough, not a huge deal for me since I found other ways to easily access it, thanks for the help!

Jpsy commented 2 years ago

Is anybody else here experiencing extreme lags of the HA events:state nodes in conjunction with this debugging info problem? I see delayed reactions of these nodes of up to several 10 seconds after the original event happened. All other parts of the flows seem to work fast as usual.

kxqcvl commented 2 years ago

Is anybody else here experiencing extreme lags of the HA events:state nodes in conjunction with this debugging info problem? I see delayed reactions of these nodes of up to several 10 seconds after the original event happened. All other parts of the flows seem to work fast as usual.

I see delays in every node, when i use the inject node, the flow starts inmediatly but in my browser there are delays of 20-30 seconds.

nibblerrick commented 2 years ago

I had this problem, too. Somehow it went now away. I detected, that I had multiple "Server configurations" for the add-on. I wasn't specificly trying to get this solved, but wanted to do a bit cleaning in my node-red. After I deleted the multiple server entries and had only one remaining,configured as "using the HA-add-on" - not with a token, All went suddenly to normal. I have now debugging events again, the states are shown under the nodes which supports that. It is running for five days now and just to be sure I restarted HomeAssistant 3 times since then and the node-red add-on I think ten times or so. Used the palette to make upgrades of installed nodes and so on. Running on a ha-supervised install in a VM.

So I thought I share this here, maybe it helps someone or helps to find the root-cause of this odd behaviour.

Jpsy commented 2 years ago

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.