Firmware update

[jmgiaever]

So I've been struggling with a device and just received a file (.otz) from the vendor, and wanted to try the feature of zjs2m. However, the dialog that pops up after «begin fw update» made me unsure what to plot in as a value. It asks me to choose target, as a numeric value, but I don't understand what to fill in.

The firmware target (i.e. chip) to upgrade. 0 updates the Z-Wave chip, >=1 updates others if they exist

I've tried to look through the manual, but it doesn't mention OTA at all, other then it supports it.

The text «updates others if they exists» confuses me.

Should I just continue with the value 0? What happens if thats the wrong value?

[jmgiaever]

Tried with target = 0, but it ends with

CNTRLR [Node 003] Firmware update timed out
INFO ZWAVE: Controller status: Node 3 firmware update FINISHED: Status -1, Time: undefined
[...]
CNTRLR [Node 003] Error while sending firmware fragment: Cannot set property 'progres
s' of undefined
[...]
CNTRLR « [Node 003] Received Firmware Update Get, but no firmware update is in progress
. Forcing the node to abort...

Am I doing something wrong?

[ziptbm]

I can do that. I'm running ZwaveJS2MQTT via Home Assistant, but I don't believe this has anything to do with Home Assistant. It's now isolated to ZEN77 Zooz series 700 switches and firmware updates. The other ZEN72 and ZEN71s I have also took multiple attempts, but they eventually took the updates (much further from the controller than these 2 ZEN77s). I've been trying periodically for almost a week, but it keeps failing.

Do I need to open something with Home Assistant first? I don't believe this is HA related per the above.

[AlCalzone]

Do I need to open something with Home Assistant first? I don't believe this is HA related per the above.

No

[jhein05]

I had problems with OTA fw updates too, and this has helped a bit:

1. I ping the node first and if the reply takes more than a second, it is highly likely that the update will fail
2. In order to fix it, I heal the node and ping again to see if it is faster afterwards.
3. Restart and wait an hour before trying again.
   It might be hocus pocus, but I feel those things helped.

[AlCalzone]

I ping the node first and if the reply takes more than a second

That sounds really slow.

[jhein05]

I ping the node first and if the reply takes more than a second

That sounds really slow.

I agree :)