The UI within Home Assistant doesn't work properly

[Jens-Wymeersch]

Problem/Motivation

Basically since a couple of days, nodered doesn't work properly within home assistant. Meaning that I can't search the entities, I don't see the connection status, etc.
However, when I use it via the 1880 port, all works perfectly.

Expected behavior

I would expect the same behavior in the iframe as the webpage

Actual behavior

I see all the flows but no connection status nor the ability to search for entities.

Steps to reproduce

Since the latest NodeRed update, I've seen this change.
Here is the version I'm using
Node-RED version: v4.0.3
Node.js version: v18.20.4

Proposed changes

I don't know what to do or to search for. Nothing visible in the logs

[mattmeiser]

Seeing the same here.

[ecard0]

Same here :(

[oliver073]

Same here - and most of the time all inject nodes are grayed out and cannot be started.
I believe this is since the last update.

[amaisano]

Perhaps related: all my HA Companion sensors have doubled in HA's entity list. binary_sensor.pc_status duplicated to binary_sensor.pc_status_2 - this happened for all of them. The non-_2 entities all say they have no Unique ID and cannot be deleted or renamed, which is of course breaking all my automations.

[Mikefila]

Perhaps related: all my HA Companion sensors have doubled in HA's entity list. binary_sensor.pc_status duplicated to binary_sensor.pc_status_2 - this happened for all of them. The non-_2 entities all say they have no Unique ID and cannot be deleted or renamed, which is of course breaking all my automations.

zachowj/hass-node-red#126 (comment)

[nappyjim]

Same issue for me. Accessing it through port 1880 works good. I corrected my 100+ issues it had, but still accessing through HA doesnt work correctly.

[IkaSGC]

Same problem here... Sometimes it work, sometime not.... On my home computer it not working... But today i connect from my work computer and first time everything works... But then i close all windows, log again into HA and bug is there...

For example, all inject nodes are shaded and the can not be operated... No connection or other statuses.... It has something with WebSocket....

[kerowog]

Same. UI loads but inject nodes are greyed out and no status is displayed under any node. Flows and automation work. Locally I can access via browser and HA address with port from NR settings and then everything is displayed and working.

[kerowog]

And now it's suddenly back to normal. I haven't changed anything. We'll see how long it lasts...

[orangelizard]

Just in case it helps. Same problem here with no connection status for nodes.. After Node Red uninstall, delete Node Red folder in HA and import all flows and modules it worked fine. Then updated this websocket to 0.74.0

and they disappeared again. Repeated fresh install as above leaving the websocket update for now and all ok and waiting to see if it lasts. 😉

[kersten-lohmeyer]

Just in case it helps. Same problem here with no connection status for nodes.. After Node Red uninstall, delete Node Red folder in HA and import all flows and modules it worked fine. Then updated this websocket to 0.74.0 and they disappeared again. Repeated fresh install as above leaving the websocket update for now and all ok and waiting to see if it lasts. 😉

Doesn't work for me. I uninstall the addon, delete the folder, restart the host, install Node Red again. All my flows are still there??? Then I restore 18.0.5 and all it says is: "503: Service Unavailable". If this is not fixed anytime soon I might try to put my automations into HA. NR has been working flawlessly for years now with every update!

Even trying to setup NR from scratch won't work. Injection nodes are grayed out. Won't bother any further.

[orangelizard]

It survived yesterday but back to no inject and connection status this morning. Just using port 1880 for now as that is fine as others have commented.

[rlyons20]

Similar problem here? I don't see any node status and debug messages are delayed and/or non-existent.

[Ticker918]

Same here. Greyed out inject nodes and not seeing any status changes etc.

[kersten-lohmeyer]

Isn't this one of the most important addons of Home Assistant? I don't get it why there's still not assigned anyone. No offense!

[Dodoooh]

I am dealing with the exact same problems..

[DocN0]

I also have these problems, the flows work, felt slower. but no debug or inject possible.
I hope it is allowed to ping @frenck ?

My question is also what is the workflow to fix this? reinstalling nodered and reimporting the flows really solves the problem?

[kersten-lohmeyer]

My question is also what is the workflow to fix this? reinstalling nodered and reimporting the flows really solves the problem?

Didn't work for me at least.

[Dodoooh]

I did the same—set up a fresh Home Assistant instance on Proxmox, installed Node-RED 18.1.1, and imported the flows. Unfortunately, I’m still seeing the same errors, so they must be embedded somewhere in the flows themselves.

[kersten-lohmeyer]

I did the same—set up a fresh Home Assistant instance on Proxmox, installed Node-RED 18.1.1, and imported the flows. Unfortunately, I’m still seeing the same errors, so they must be embedded somewhere in the flows themselves.

Did you try rebuilding your flow from scratch? Including injection nodes?

[Dodoooh]

@kersten-lohmeyer
Hej, yes with the new installation everything worked when I reinstalled it, only after the import I have the errors described.

[bennybubble]

Same here, problem started yesterday. Only way to acces NR is via :1880.

[bennybubble]

I just installed the 2024.10.3 update and the problem seems to be gone ... fingers crossed...

[orangelizard]

Update 2024.10.3 made no change for me, still exhibiting the same issues.😔

[nappyjim]

I'm fully updated as of 10/18/2024 and issue is still there.

[Jenzemann1]

Same problems and all updates are up to date... Port 1880 works still..

[1192410]

I have the same issue, and I'm really wondering why this hasn't been addressed with higher priority. Port 1880 works for me too. This is how it looks in the add-on. Someone should be assigned to resolve this issue asap.

Many thanks, Andreas

Add-on:

1880:

[kersten-lohmeyer]

I have the same issue, and I'm really wondering why this hasn't been addressed with higher priority. Port 1880 works for me too. This is how it looks in the add-on. Someone should be assigned to resolve this issue asap.

Many thanks, Andreas

Add-on:

1880:

I don't see the status below the nodes. I can't even login to https://.....:1880 even though I setup a username and password in the NR config. Trying to login with the credential_secret doesn't work either. I'll stay on 18.0.5 for now and if this doesn't get fixed I try to build my flows with HA automations.

[orangelizard]

@kersten-lohmeyer try using your HA login details for the 1880 login credentials, that should work.

[kersten-lohmeyer]

@kersten-lohmeyer try using your HA login details for the 1880 login credentials, that should work.

Yes, it's working. Thanks!

[FuturamaPhill]

having this issue as well

[kersten-lohmeyer]

Is it working for anyone with HA Core 2024.10.4? It shows "Connected" below the nodes for me but that doesn't update.

[Dodoooh]

@kersten-lohmeyer nope. same issue. I think the addon needs to be fixed i still have problems

[Jens-Wymeersch]

Again the NR went totally down due to an unstable server connection. Is there a work around ?

[DocN0]

uff it's odd that there is no news at all i still have the problem.
and it seems to affect quite a few people...

@frenck have you at least seen it? i would be happy to provide more information/logs, but the update currently seems to be unusable. inject nodes grayed out ect. see comments above.

[Jens-Wymeersch]

@DocN0 I'm planning to move away from the add-on towards a separate installation. But for the time being, I read that upgrading the node-red-contrib-home-assistant-websocket (palette inside NR) is the way to go

[kersten-lohmeyer]

@DocN0 I'm planning to move away from the add-on towards a separate installation. But for the time being, I read that upgrading the node-red-contrib-home-assistant-websocket (palette inside NR) is the way to go

Thanks a lot, that actually worked! Though I thought I tried this before. But why is this not communicated by the NR or HA team? Or was it?

[Dodoooh]

@DocN0 I'm planning to move away from the add-on towards a separate installation. But for the time being, I read that upgrading the node-red-contrib-home-assistant-websocket (palette inside NR) is the way to go

Thanks a lot, that actually worked! Though I thought I tried this before. But why is this not communicated by the NR or HA team? Or was it?

really, that worked for me too, just tested it now. and I'm pretty sure I tried it before.

thanks @Jens-Wymeersch

[kersten-lohmeyer]

really, that worked for me too, just tested it now. and I'm pretty sure I tried it before.

I think there was an HA core update in between and I might not have tried it after that one.

[mattmeiser]

Fixed here too.

[kerowog]

I had updated the HA core to the latest version and it still wasn't working.
But after updating node-red-contrib-home-assistant-websocket, the node status and inject buttons came back.

[Jens-Wymeersch]

I've been looking into this problem for the last couple of weeks on multiple github pages. It looks like Jason from https://github.com/zachowj/node-red-contrib-home-assistant-websocket is the most active.
@DocN0 I did the first test with a clean docker or a LXC with NR and the websocket. It works really well and so intend to move NR away from HA as I did with Z2M. The only question is to where ?

[super-bedst]

I had same issue, for me it helped then i go to menu->Manage Palette -> Nodes
here search for node-red-contrib-home-assistant-websocket, and look for an update, my version was 0.73 and there was a update button to 0.74.2, i pressed that and restarted the nodered add-on service in HA, and after that i was working with all my existing flows.

It was also fixing my greyed out inject and debug nodes :-)

[rlyons20]

@super-bedst has the solution here!

[github-actions]

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!