Open a011528 opened 1 month ago
Can you clarify what’s freezing—the Node-RED UI or the server? Are you accessing it via an iframe in Home Assistant? If so, try connecting directly through port 1880. Also, check if there are any errors in the browser console.
When I upgrade the node, once it is installed after a restart, Nodered gets stuck in the UI, its similar to the entry below, except ive not been able to resolve yet, i need to revert to a back-up in HA without your node to get nodered to work.
https://github.com/zachowj/node-red-contrib-home-assistant-websocket/issues/1504
As mentioned in the linked issue, are you seeing any errors in your browser's console? Have you tried accessing Node-RED directly on port 1880? Additionally, have you tested it in an incognito browser session to rule out caching issues?
I have the exact same issue... it doesn´t matter if you try to open within homeassistant or access driectly on :1880 or even use an incognito tab... it takes around 3-5 minutes to load the ui... also there is a significant higher cpu load around 39-41% in my case, it was like 21-25% before....
@k2dp2k post setup info https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html. What was the last "working" version?
Version: 0.72.2
Home Assistant version: 2024.9.1 Companion version: 4.0.2
Node-RED version: 4.0.2 Docker: yes Add-on: no
Node.js version: v18.20.3 x64 linux OS: Linux 6.6.46-haos x64
sadly i have no idea which combination of versions was installed previously....
Describe the bug
Home Assistant Core 2024.9.0 Supervisor 2024.08.0 Operating System 13.1
NodeRed V4.02
When i load V 0.68.9 it prevents NodeRed from loading
To Reproduce
Update nodes in NodeRed
Expected behavior
for it not to freeze nodered
Screenshots
No response
Example Flow
No response
Environment Information
NA
Additional context
Ive needed to restore previous version to keep