I have a growing network with 17 Z-Wave nodes, mostly wired (only one battery sensor) and almost all of them from Aeotec (including Z‐Stick Gen5 adapter). Most of the nodes are included through SmartStart.
I’m having some communication problems that become most apparent when doing firmware update through Z-Wave JS UI (I also tried the regular UI, same result).
Looking at the logs (https://pastebin.com/raw/Ztcvd816), there’s a few problems:
- When the update goes, it goes smoothly (sending fragments every 100-500ms), but if it trips (and it trips often), it gets stuck for couple or even dozens of seconds
- If any other sensor updates its values, it trips with “CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try in 100 ms.”
- Occasional “DRIVER Dropping message with invalid payload”
- Sometimes “received S2 nonce without an active transaction, not sure what to do with it” on otherwise healthy nodes
- “Firmware update timed out” after 34 seconds from the last sent firmware fragment (but having “Dropping message with invalid payload” in the meantime, which could be the fw request?)
- “Received Firmware Update Get, but no firmware update is in progress. Forcing the node to abort…” 5 seconds after firmware update timeout (looks like the node still wanted another fragment)
My wild guess is that problem 3 is the root cause, but extending the timeout (problem 5) would at least unblock firmware updates.
Any ideas?