Can't enable debug or give inject

Third party integrations Node-RED
1

I can’t enable debug in node red or make a inject.
Want to test some things but notice this.

I did the latest updates of HA, restart and also have restart node-red self without luck.

Only have 1 HA in node red.

the flows are working fine that is not the problem

I access HA with local IP and port

somebody have a idea?

image
image1943×662 69.2 KB

edit:

see other topic with this problem… sorry

Log into nod red with local IP of HA and port number
http://HA-IP:1880/

I saw some errors.
All of them where nodes or entity’s of old devices or not connected nodes.
I resolve them all and after this I could use the inject and debug again.

image
image757×641 31.5 KB

edit:

local node red fixed all the issues top right corner.
Then restart HA and restart node-red.

local node red IP debug and inject is working.

Homeassistant local IP in node red not working…

2

That little HA logo | error count | caution icon keeps coming and going on my system.
When it is there, the inject and debug nodes work.
When it is not there, they don’t.

I haven’t figured out what controls it.
I fixed all but 2 of the errors last night. inject and debug were working.
today, it’s gone along with the functionality of the inject and debug nodes.

3

That’s because they all communicate with the Node-RED server using a WebSocket connection. When the WebSocket communication isn’t working, the inject node, status node, debug window, and Home Assistant issues information aren’t sent to the client, so they appear to not “work.”

4

I have the same problem as the OP. When I access NodeRed via it’s opened Port, the debug tab, the “connected”-Info below status nodes, etc. are working. When I connect via the (http-only) local IP of HomeAssistant, it’s not working - same when I access with the (https-only) duckdns / letencrypt.

I am using the nginx-plugin to separate the local (non-https) and remote (https) connections - could that be the culprit?

5

I was having the same issue. After reading this thread, I enabled SSL on the Node Red addon and it immediately fixed the problem for me. Thanks!