The error you got seems to align with the driver linked at the very top of this thread, which only works for the old OTZ firmware files, not the GBL files. That github repo has a binary version in it, but also the guide that I linked to specifically has a link to a forked version which fixes a bug and adds a couple features.
yeah, that was it. What's weird is that in the past it worked. I wonder if I already had the updated driver before but then it got reversed? is that possible with HPM or something?
Anyway, thanks for your help.. i'm up to 95% uploaded (been almost 2 hours :D).. this relay is pretty far from base station .so....
Yes unfortunately the old original driver, binary version, AND the forked version all have the same name / namespace. Only the original is in HPM, so if you do anything in there like a repair it will put the old driver back. I would recommend going into HPM settings and un-matching it.
Hubitat's built-in / native Device Firmware Updater app (available to add from the Add built-in app button) works well for everything now (incl S2 mesh and LR devices), with one caveat...
If updating more than one device, I had to do a hub reboot in between each update -- otherwise the update was ridiculously slow. Other than that, my recent LR and S2-mesh device updates lately (all Zooz stuff) went fast & easy.
Quick update. I tried the built-in firmware updater twice to update a ZEN54 LR. It took about 10 hours... and then failed. I have security disabled on the device.
Rebooting the hub in between (any/all) attempts seems to be an unfortunate necessity -- dunno why, but that's been my N=1 experience lately.
This also shouldn't be necessary, but every time I use it (successfully or not), I always purge all uploaded files and then remove / reinstall the app (and reload the necessary file). If it was successful, I just purge the file and remove the app.
When you start the process, double-check the correct device is selected (easy to mess up if you have several of the same), and make sure the app shows the correct current f/w value before initiating the update.
If the native app continues to be uncooperative, you can always try this method... It won't work for LR devices, but it should work well for everything else.
This is how I did my updates for a long time since I like S2, but the native updater app didn't support S2 devices until recently.
Thank you. How does one prevent corruption during transfer? (I did this three time and it failed each time). I finally did it on the fourth time and it was successful, but took about 5 hours.
Thank you. Rebooting definitely made a difference. After 4 attempts, I finally got the firmware updated.
(It seems that device firmware updating is considerably more difficult than it needs to be. It took 2 days with multiple attempts for a single device).
(It's a UI mess).
