Nodered corrupted, can not use inject node

Canedje · December 29, 2022, 8:02pm

I’m running the latest HA.

I thought that the Supervisor must be 2022.12.1?

I do run NodeRed as a addon
Since this afternoon I did founf out that I can not use the inject node anymore.
It is there but I can not push the button anymore to activate.

The flows itself are running.
The log give some errors:
But I don not know what they mean or how to fix or do the commands.

I did install old backup from a week ago, but still no change
What can I do to fix it?
Please help

EDIT: I did found a workaround. By opening the node I can inject by pushing:

EDIT2: Debug is also not showing information anymore

EDIT 3:
I did found a guy with the same problem:

github.com/hassio-addons/addon-node-red

Inject and debug are greyed out, nothing to update or process, no errors in the log

opened 01:03PM - 27 Dec 22 UTC

magiva

# Problem/Motivation the inject nodes and debug nodes are greyed out with no ou…tput to the debug window ![image](https://user-images.githubusercontent.com/7522405/209670281-2ac78c03-be07-44e4-8dfe-3c0c7fbc3eac.png) there are no nodes to update ![image](https://user-images.githubusercontent.com/7522405/209670332-72e5bf3b-3c0b-46c9-ba33-fdc466ca8f5a.png) nothing to process the debugs do output to the log when automations happen but not to the ui logs show no errors s6-rc: info: service init-nodered successfully started s6-rc: info: service nodered: starting s6-rc: info: service nodered successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [14:01:57] INFO: Starting Node-RED... > start > node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js 27 Dec 14:01:59 - [info] Welcome to Node-RED =================== 27 Dec 14:01:59 - [info] Node-RED version: v3.0.2 27 Dec 14:01:59 - [info] Node.js version: v18.12.1 27 Dec 14:01:59 - [info] Linux 5.15.80 x64 LE 27 Dec 14:01:59 - [info] Loading palette nodes 27 Dec 14:02:02 - [info] Dashboard version 3.2.3 started at /endpoint/ui 27 Dec 14:02:03 - [info] Settings file : /etc/node-red/config.js 27 Dec 14:02:03 - [info] Context store : 'default' [module=memory] 27 Dec 14:02:03 - [info] User directory : /config/node-red/ 27 Dec 14:02:03 - [warn] Projects disabled : editorTheme.projects.enabled=false 27 Dec 14:02:03 - [info] Flows file : /config/node-red/flows.json 27 Dec 14:02:03 - [info] Server now running at http://127.0.0.1:46836/ [14:02:03] INFO: Starting NGinx... 27 Dec 14:02:03 - [info] Starting flows 27 Dec 14:02:04 - [info] Started flows 27 Dec 14:02:04 - [info] [mqtt-broker:hass-mqtt] Connected to broker: mqtt://localhost:1883 27 Dec 14:02:08 - [info] [server:Home Assistant] Connecting to http://supervisor/core 27 Dec 14:02:08 - [info] [server:Home Assistant] Connected to http://supervisor/core ## Expected behavior ability to click injects and see debug details as before ## Actual behavior greyed out ## Steps to reproduce create an inject or debug ## Proposed changes i have no workaround for this

This a workaround

roybosch · January 1, 2023, 9:33pm

I’m having exactly the same problem. Also my debug nodes show the same greyed-out button, what about yours?

My logs don’t show anything, and my problems seem to have started a few days ago. First all my lights responded very slowly on my switches (I use NodeRed to readout input from those switches to activate lights). In the end it seems that NodeRed gets slower and slower.

I’m running NodeRed 14.0, but going back to 13.5.3 doesn’t help. I’m running the latest HA (2022.12.8).

Canedje · January 2, 2023, 6:39am

I have the same experience. Inject and debug are greyed out.
It must indeed be supervisor causing this problem
I did open/ react on 2 issues in Github supervisor and nodered

EDIT: I see it is also not possible to select devices or so in the nodes, it looks like there is no connection to HA

roybosch · January 2, 2023, 2:02pm

Same here also. I thought it was related to the many “entity could not be found in cache for entity_id” errors in my NodeRed logs, which started to appear the last few days. Also the nodes kept disconnecting and connecting to the supervisor with no reason. None of the found solutions for those errors worked for me, so I had to reinstall NodeRed and restore my flows. That got rid of the entity_id cache error, but it didn’t fix the autofill of the entity id’s.

Let’s hope there will be a quick fix to this. My whole house depends on it.

Canedje · January 2, 2023, 2:53pm

The same over here.
I did try to reinstall Nodered from scratch, but that did give me errors.

EDIT: I did just install 14.0.1 the same problems

johntdyer · May 10, 2023, 11:11am

Did you ever get to the bottom of this ?

Canedje · May 10, 2023, 1:01pm

Yes. Suddenly after a update it did work again. But I’m now running NodeRed as a docker.
I don’t want this again

zimmer62 · June 24, 2023, 6:48pm

I’m having this problem. I wonder what the actual cause is.

nick4275 · July 5, 2023, 9:20pm

Could this be the recent update to NR inside HA ?
My system has been fine for years, now I’m getting the Inject Node greyed out.
I can work around it using the localhost:1880 but it would be good to find out what’s going on and get it sorted properly.

nick4275 · July 7, 2023, 10:57pm

Just in case anyone is looking here.
I upgraded to NR 3.0.2 this evening and the problem seems to have been fixed !

PhoenixG36 · July 10, 2023, 4:14pm

I have also this problem and for me is still there after upgrade to Node Red 3.0.2
What I figured out is, if you open Node Red direkt in Browser with the added http port for the Plugin, every thing works.

PhoenixG36 · July 10, 2023, 4:20pm

open over port direct in browser

open inside from HA

jimmyeao · July 22, 2023, 3:53pm

Still borked in the latest version for me

nOoboO · August 12, 2023, 7:32am

same for me. Opened it directly with port in Browser, I can see every Output. Inside HA it doesn’t show anything also trigger nodes are not triggerable. Any solutions?

RomanSch90 · August 12, 2023, 12:25pm

Same for me. Within HA not working and with direct call to Port not working either.

My System Details:
Home Assistant 2023.8.2
Supervisor 2023.08.1
Operating System 10.4
Frontend 20230802.0 - latest

Node-Red Addon: 14.4.4

Running on a RPI4B+ with 8GB Memory

kpurintun · September 9, 2023, 5:19am

Man… I seem to have a lot of Node Red Issues.

The inject node button is greyed out and doesn’t work. (works directly to node red, but not inside HA)
Not seeing the little status icons and messages below the nodes. (works directly to node red, but not inside HA)
Had issues with the node red companion integration. I think I might have that sorted… but still need to watch it.

anyone have any luck?

running the latest NR, NR companion, and Websocket

Tscherno · October 14, 2023, 4:59pm

Same issue here. Did a reinstall today because of the Entity lists not populating anymore. Now the Inject/Debug Buttons are bugged. At least Entity-Lists are working again

vijaykirann · December 2, 2023, 2:55am

Im able to use it from browser using <HA_IP>:1880…bookmarked and it’s working fine.

Tweedledee · January 31, 2024, 2:32am

Had this issue today - working fine yesterday but sometime this evening I noticed that it was giving the inject/debug button issue on my Firefox browser - client machine. Tried clearing cache - no luck.
But when logged in remotely to server GUI it’s working (also Firefox).
Also when i try chrome on client it’s working ok.
Running NR 3.0.2 on Linux Docker, not via HA. Firefox 121

lacrima08 · February 10, 2024, 3:45pm

Hi,

I have also issues with inject and debug node

It ask me for login/password if I tried to run throught http://IP:1880 (no ssl), i tried to config them in Configuration tab of NR Addon in HA in http_static section but it dosen’t seems to work ? How to deal with it, please ?

Addon version tested : 17.0.4 - 17.0.5 - 17.0.6