Anyway to stop zwavejs from attempting firmware update/network heal?

LearningHASlowly · December 3, 2022, 4:54am

I am running HAOS w/ zwavejs and a Zooz USB stick. I was trying to update a Zen14 (outdoor plug) firmware and got an error message ~7% in “update failed”. I thought I would try a network heal for this device and try again, but got an error message that a heal was already in process. After ~8 hours I noticed the heal was still going on… I tried rebooting, unplugging the devices, and it still is showing an active heal is underway. I then took a look at the zwave logs and saw this:

2022-12-03T04:48:15.562Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:16.288Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:16.497Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:16.720Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:16.917Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:17.125Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:17.238Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:17.463Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:17.668Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:17.875Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:18.084Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:18.290Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:18.498Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:18.707Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:18.919Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:19.124Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:19.332Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:19.543Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:19.750Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:19.956Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:20.162Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:20.371Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:20.579Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:20.792Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:20.998Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:21.206Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:21.414Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:21.622Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:48:22.177Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:22.563Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:24.172Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:24.534Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:24.900Z DRIVER   Dropping message with invalid payload
2022-12-03T04:48:36.663Z CNTRLR   [Node 059] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-12-03T04:48:58.453Z DRIVER   Dropping message with invalid payload
2022-12-03T04:49:01.206Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:02.106Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:03.113Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:03.464Z DRIVER   Dropping message with invalid payload
2022-12-03T04:49:11.130Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:15.765Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:20.645Z CNTRLR « [Node 059] Received Firmware Update Get, but no firmware update is in progress
                                  . Forcing the node to abort...
2022-12-03T04:49:21.014Z DRIVER   Dropping message with invalid payload
2022-12-03T04:49:21.729Z DRIVER   Dropping message with invalid payload

It looks like zwavejs is blitzing my device trying to do a firmware update and being unsuccessful with aborting. Is there any way to kill this? Something like a force quit?

freshcoast · December 3, 2022, 5:11am

Have you tried power-cycling the badly behaving node (59)?

LearningHASlowly · December 3, 2022, 12:38pm

Thank you! That seemed to solve the problem (I had only rebooted the hub thinking that was controlling everything)

Curious: from your experience do firmware updates need to take place when the node is close to the hub? Or if they are responsive in their current location should they be able to accept update?

The device I was trying to update is outside and is responsive on my network, but a little nervous about attempting another firmware update

freshcoast · December 3, 2022, 3:16pm

The firmware updates should work anywhere, but if there are communication issues in the network, the updates can either take a very long time, or just fail. Seems that may have happened in this case. You could try bringing the device in closer to the controller (easy with a plug), but be sure to heal it when you move it each time.

LearningHASlowly · December 3, 2022, 3:49pm

Cool thanks!

freshcoast · December 3, 2022, 4:16pm

Also, if your Zooz controller is a 700-series, make sure the firmware is v7.17.2 or later, and your USB stick is on a USB extension cord, away from noisy USB ports and any other interference.

LearningHASlowly · December 4, 2022, 3:00am

Thanks - I haven’t done the USB extension, but will give that a try too…

I wish there was a way to evaluate the mesh network to see how things are going overall (e.g. good health? bad health?) to then be able to see whether things like USB extension or network heals are making any difference

freshcoast · December 4, 2022, 4:51am

Z-Wave JS UI has a network health check feature.

A USB extension is such a common effective solution that it’s the first thing to mention when troubleshooting. There’s no question it makes a difference, but it’s not 100% successful.