I'm having the same problem on my C-8.
Trying to update a ZEN34 from 1.01 to 1.4 (to address multiple battery reports)
Getting stuck. Looks like the log says it's not upgradeable.
Anyone know what's going on?
@jtp10181 ? You're the ZEN meister. 
edit: Here's update file, from extracting the zip file:
This was totally unrelated to original post so I split it off.
Every Zooz device has that upgradable flag to false for some reason, might just default that way and they dont have it set correctly.
Did you wake the device up? Move it closer to the hub?
Yes.
I woke it up, but does the blue light have to be on?
It seems to turn off quickly.
I'm now trying closer to the hub as well.
I didn't know that.
Sorry I didn't read the thread close enough.
Upon first glance, it looked like it fit.
This is what I was driving at.
The blue light turns off pretty quick.
I'll keep trying.
Got it working.
Practice makes perfect!
Thanks
For future/other's reference, disabling the device can sometimes help with battery-device updates.
On a side note, it was total serendipity that I found the excessive battery reporting thing.
I was in the logs looking for something else and found that.
A search on the forums indicated a firmware upgrade would fix.
Two of my three ZEN34's were at 1.01, while the third, and probably newest one, was at 1.4.
I did notice that z-wave would hiccup once in a while, but figured, hey that's z-wave.
Yeah, I was pretty quick on the trigger this time.
Then, there's the wrinkle of probably pressing the up button only six times instead of seven!
An amber (to me-I'm partly colorblind) starts flashing. I didn't bother trying to see what that did-the button still did what it was supposed to, and that's good enough for me!
That seemed to help on the second one.
I was still pretty quick on the trigger though, because the blue light still went off quick, so who really knows?
Disabling the device is a good idea anyway: the first one turned on/off all the lights in the house and the second one turned open/closed a valve.
Of course, I'll have to remember to re-enable it, lol.
Yeah I always forget about that unless I am doing it myself. Prevents the driver from responding that it is done with the wakeup.
Looks like I shot myself in the foot.
I turned re-enabled it while it was still updating.
Now, it looks like it's permanently disabled.
Will be restarting hub shortly, lol. That's my go to move.
Yeah, leave it disabled.
Also, you may need to power off the hub and the device to clear the zwave radios before it will work again. I have had that happen before if they get stuck part way through.
Luckily, it was only uploading the file to the device not flashing it, so the device should be unharmed.
Shutdown/power cycle didn't help.
I don't know what you mean.
I enabled before I shutdown/power cycled.
Firmware is at 1.40, it says.
This wasn't stuck, it fully updated.
I don't think I did a good think disabling it on the device page during the update.
Excluding and re-including did the trick.
For me the moral is: don't re-enable the device while firmware is updating.
Some of the Zooz devices will factory reset themselves (or clear the lifeline association) after a firmware update. That may have been what happened on this one, maybe because it went from an old version. Usually does not happen on the newer devices anymore, I think they realized it was overkill and annoying.
I was wrong about the other one working-it did not, despite not messing with disabling.
I could've sworn it did.
I had to exclude and re-include, just like the other one.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
