HA no entities no devices node-red 18.1.1 websocket 0.73

[zajaaczki]

After update to 18.1.1 no entities no devices only display action and random signs in device field.
After nodes update same issue.
Rollback to 18.0.5 back to work ok

[meineihan]

me too

[mhquail]

I have the same issue (when Cache autocomplete results is checked under UI Settings). Unchecked and I can see my entities, checked, I am unable to search for anything (under Targets or Actions). This started on this update.

[cpuks]

Try accessing node-red addon directly by typing ha_ip:1880 - you can log in with same passwd / user that is used for HA login..
With recent version of node-red ha-node there's issue with iframe.

[mhquail]

Try accessing node-red addon directly by typing ha_ip:1880 - you can log in with same passwd / user that is used for HA login.. With recent version of node-red ha-node there's issue with iframe.

This works fine.

[KillSwitchIO]

I too ran into the same issue and was concerned I broke something this should likely be noted in the docs somewhere easier to find as it leaves people not able to use NodeRed when they update.

[KillSwitchIO]

To further add to this, my inject button is not functioning unless I do as suggested http://{ip}:1880.

[redlegoman]

Pointless same-here comment incoming: I had the same issue, but I restored to 18.0.5 and all is well again. I shan't be updating again, that scared me!
On the Node-red issue, they are saying it may be a CORS issue. Hopefully @frenck has seen this

[redlegoman]

I have just upgraded the node-red-contrib-home-assistant-websocket node-red plugin to 0.73.0 (it was 0.65.0) while still running node-red 18.0.5 and the problem with the inject nodes has returned. So it looks like an issue with the node-red-contrib-home-assistant-websocket palette/plugin...

[redlegoman]

Looks like it has been reported.. zachowj/node-red-contrib-home-assistant-websocket#1480

[cpuks]

Looks like it has been reported.. zachowj/node-red-contrib-home-assistant-websocket#1480

Yeah, that's my bug report, but it's rather problem with HA iframe not working correctly - addon itself works fine.
I'm surprised that nr addon was upgraded despite that bug, so many less experienced users will be complaining :-(

[zajaaczki]

Yes 18.1.1 works as before out of HA on port 1880 :-/

[meineihan]

I just fixed them one by one.

[redlegoman]

I just fixed them one by one.

How? What did you fix?

[cpuks]

That didn't fix issues in my case - I fixed all NR complaints before moving to HA 2024.10 and after upgrade I still see same problems.

[yuckypants]

I'm a little surprised there are so many different tickets open on this and no one has acknowledged them.

[jonrupell]

I am also having the same issue. I honestly have been having nothing but issues lately with all the home assistant updates. Seems like with each update something breaks the last few updates. Hope this is not the future of HA. I never had issues previously. I trusted each of their updates were tested well and work and never had issues as a result until the last few updates. As a home that has about 500 smart devices connected to HA, this is really concerning. Hope this gets resolved soon!

[HermesHonshappo]

Same issue here
Same nodes through HA add-on interface:

Through local 1880 access to the HA add-on:

It's the same Nodered instance, running as a HA add-on. I have no errors showing up in Nodered top right corner.

Seems to me that it is the embedding of Nodered interface within HA main interface that introduces this

I also noticed that sometimes, after an undetermined period of time, the function is restored when using the HA main interface

This is a problem (at least for me), as I'm not exposing HA or NR directly to the internet, and am using Nabu Casa service. So I can't access NR using the 1880 port when not at home.

EDIT: created a long lived access token, and reconfigured NR to use this and the real HA URL instead of being in "HA add-on mode". Also tried to reset to default HA theme. Also tried to open HA in a different browser. No luck, neither attempts solved the issue

[jerryac]

Have the same problem going through HA and also direct via port 1880. Also missing various installed nodes and unable to update or install any other nodes.