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
UI delays the driver massively when nodes with a lot of values are ready #2676
Comments
Possible fix published. Let's try with next 8.0.1 version |
@jcam Did you give that a try? |
I currently use the homeassistant addon that frenk maintains, so i either need to manually update / set up a private repo and all that, or wait for him. if he doesn't publish an update in the next day or two i'll build it myself. |
I don't use HA but I know there is a reference in addon readme at least |
Good day! I finally got 8.0.1 installed, unfortunately no change. Let me know if there are more details/debug logs or something I could gather. |
@jcam could you upload new logs please? Does pinging a node takes lot of time like before? |
It's not pinging the node that takes time. It's zui doing sth with the values after the node is considered ready. |
I need to see logs to see if there is a little bit of improvements or not. I sincerly have no idea about what is causing those delays |
Here's a debug log! May include a partial debug log at v8.0.1 and then again at 8.1.0 |
Looking at logs I see that the slowdown only happens for first 3 nodes, specifically 2-3-4 nodes takes ~20s from alive to ready. Starting from node 5 it takes ~1s so I don't think it's something strictly related to z-UI. any other consideration @AlCalzone ? @jcam I cannot check the zwave-js driver logs as I think you picked up the wrong file (an old one). |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
Continuation from zwave-js/node-zwave-js#5088 (comment)
On slower(?) systems, the UI's handling of ready nodes delays the driver for several seconds when a node with lots of values gets ready. Here's the example from the other post. I'm not sure what work ZUI is doing here and why the hell it takes 20 seconds to populate maybe 50 values - maybe there are some inefficiencies like emitting events or rebuilding the UI for each of those?
Driver
UI
/cc @jcam
The text was updated successfully, but these errors were encountered: