Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HA no entities no devices node-red 18.1.1 websocket 0.73 #1960

Open
zajaaczki opened this issue Oct 2, 2024 · 15 comments
Open

HA no entities no devices node-red 18.1.1 websocket 0.73 #1960

zajaaczki opened this issue Oct 2, 2024 · 15 comments

Comments

@zajaaczki
Copy link

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
node1
node12

@meineihan
Copy link

me too

@mhquail
Copy link

mhquail commented Oct 2, 2024

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
Copy link

cpuks commented Oct 2, 2024

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
Copy link

mhquail commented Oct 2, 2024

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
Copy link

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
Copy link

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

@redlegoman
Copy link

redlegoman commented Oct 3, 2024

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
Copy link

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
Copy link

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

@cpuks
Copy link

cpuks commented Oct 3, 2024

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
Copy link
Author

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

@meineihan
Copy link

I just fixed them one by one.

@redlegoman
Copy link

I just fixed them one by one.

How? What did you fix?

@cpuks
Copy link

cpuks commented Oct 3, 2024

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants