-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Removing failed nodes does not always remove the node from the UI #2975
Comments
Please make a driver log, loglevel |
Can reproduce. Node 13 was removed immediately, Node 14 did not get removed from the UI until reloading the page:
|
Interestingly, while Node 14 did not get removed, Node 15 was missing from the nodes table, although I did not remove it. After reloading the page, Node 14 vanished and 15 came back. |
* fix: improve socket messages delivery Fixes #2975 * fix: use new approach * fix: use app.apiRequest everywhere * fix: add support for some more apis * fix: remove useless props * fix: remove useless socket events * chore: add logger * fix: lint issues * fix: use config get/set * fix: add socket event logs * fix: print driver function result * fix: improved node updates management
Checklist
Deploy method
Docker
Z-Wave JS UI version
8.8.3
ZwaveJS version
10.5.5
Describe the bug
Removing nodes doesn't always remove the node from the UI. Requires a VM bounce to remove it. Subsequent removals of the node fail saying the node doesn't exist but the row remains displayed.
To Reproduce
Remove more than one node from a network. Screenshot attached.
Expected behavior
The node row is removed when the node is removed from the network.
Additional context
No response
The text was updated successfully, but these errors were encountered: