-
-
Notifications
You must be signed in to change notification settings - Fork 600
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
Super slow network updating the same value many times #6284
Comments
Seems your device is spamming the controller for some reason. It may be useful to also check driver logs. Please make a driver log, loglevel |
Strange. Here it is. |
This looks like a connectivity issue where the command is received by the controller, but devices don't receive the acknowledgement for that, causing them (or repeaters along the route) to re-transmit. Node 10 (and at one point Node 22) only have a route that uses 9.6kbit/s, so there's definitely a problem. I'll start with a few links for you to work through.
Looks like you already have a priority route to at least one device, so you probably have played with this a bit already? Other than that: 700 series USB sticks are often reported to be problematic for EU users (terrible range). On top of that, some users have also reported that the 7.19.x firmware has terrible range for them. You have both. Do you have a 500 series stick you could go back to, e.g. Aeotec Z-Stick 5(+) with firmware 1.2? |
Its on a extension cable currently
Yes. Unfortunately to no avail.
Shucks... here I was thinking newer = better
I don't, but I can purchase one. Unsure whether a NVM backup works when downgrading 700 > 500 Thank you. |
Zwave-js converts the NVM so you can go to 500 and back. The firmware must be new enough though, so if the Z-Stick 5 isn't using 1.2, you need to upgrade it first. |
Walk/Downstairs seems like a problem. It only reaches 40kbit/s and several nodes are routing through it with even worse connectivity (9.6k). |
When you say that do you mean look into creating manual routes? |
Maybe, but not necessarily. Looks like Walk/Downstairs already has a direct connection, but a suboptimal one. Maybe there's a good repeater available that's not being used. Maybe its location is just not good. Maybe it needs another repeater inbetween. Or maybe it is actually not a big issue but the connection from it to the nodes "behind" it is. |
This issue has not seen any recent activity and was marked as "stale 💤". Feel free to reopen if the issue persists. |
Hello,
My network has become really slow, and I've noticed for many devices that the exact same value is updated a bunch of times. Slowing down the network. I do not have any idea what could cause this. When I turn on the lights, node 008 for instance shows
a total of 24 times, while it even is already the same.
shows up a total of 159 times.
These lights grouped together a staggering 28 seconds to all power on.
Any idea what this might be?
Full logs of switching ON all devices once:
The text was updated successfully, but these errors were encountered: