Open guedini opened 2 weeks ago
I'm having the same issue but the flow seems to be working fine
Thanks for reporting this issue! Here to +1 the problem. Thanks to any devs working on this! Will be a huge QOL enhancement when this bug is fixed.
Same. This behavior appears to be random. The fix is either to jump into and out of the node drawer until you can edit it, or refresh the page until it works.
The flows are unaffected and they work... I just can't see their configuration or edit them until many attempts later.
Here's what that same one above was supposed to show me. Took me a bunch of tries to get this screenshot:
Are there any browser errors when the trigger fails to load?
Same problem . running newest node red 4.0.5 and newest nod red .... websocket 0.74.1 on seperate server
Describe the bug
When I create a device node, I fill all fields and everything is okay. But when I open it again trigger is empty. It works sometimes but sometimes it only displays "Running." and it stops working, so I need to restart flow (sometimes HA) to get it running again.
Trigger is empty when reopening device node screen.
To Reproduce
Create a device node filling all fields. Save it and deploy the changes. Reopen the created device node and trigger is empty.
Expected behavior
Keep the value filled when created
Screenshots
Example Flow
No response
Environment Information
Version: 0.72.4
Home Assistant instances: 2 Server: 8729b6fb.3f2178 Home Assistant version: 2024.9.3 Companion version: 4.1.0 Server: 99d99ef8.b2543 Home Assistant version: 2024.9.3 Companion version: 4.1.0
Node-RED version: 4.0.3 Docker: yes Add-on: 18.1.1
Node.js version: v18.20.4 arm64 linux OS: Linux 6.6.31-haos-raspi arm64
Additional context
No response