C7; firmware 2.5.0.123, just updated.
Attempted to update firmware on Zooz ZSE44 800 series from 2.0 to 2.4
Hub mostly will not communicate with device: new battery, device has updated itself in devices page.
Once I found the relocated updater, (I hade installed the correct file earlier, before firmware of hub was upgraded), firts the hub found the device, but once started the upload process, stuck at “finding device versions”. The correct present version was already recognized, and the new file identified, but process would not proceed. Tried rebooting hub, then powerdown and restart, It would no longer talk to the device, complaining that device did not respond to request. Removed device battery and restarted device; same problem.
Is there a Hubitat firmware updater that actually works? I’ve updated devices before, including battery devices, and specifically ZSE44s. It’s always been a pain to get it working, with several hub restarts, but now it just doesn’t seem to work at all. And, yes, I moved the device close to the hub, and repeatedly pressed the manual wakeup button, which responded with an led blink. It could be a Zooz existing firmware issue, but I think it unlikely.
Update: I got it to start the process again with initial success, but the process has been stuck at 0%,
“ Update status
Device Firmware Updater: Getting Device Versions”
for the past five minutes and refuses to advance.
Well, yes, but no! Yes, I did wake the device. The maker claims it remains awake for about 1 minute. But no, I have not repeatedly done that in this case, because the failure occurs immediately, making it irrelevant. There is no feedback from the Hubitat to tell me what is happening: it just displays the notice that it is requesting "Device Versions", which it seems happy to do forever, so I eventually have to abort the process and move on.
Yes, I know how difficult this process is: I've done the device firmware updates in the past, including on ZSE44 devices, and it's extremely painful and problem fraught. Hubitat should at least test the process with a few devices to discover that it really doesn't work!
Do you honestly believe that the firmware updater, and every other app/driver released by Hubitat, was released without extensive beta-testing?
It is possible you have a hub with a misbehaving zwave radio.
In that context, more frequently, it is observed that there are sometimes errant devices that reach some misbehaving internal state. Sometimes what works with such devices (on any platform) is to exclude them, then perform a factory reset, and finally reinclude them before attempting the process again.
Well...there is ZWJS, lol. Only by using a community driver was I able to get my ZSE41s on ZWJS, despite months of bitching about it-no response from Hubitat. But that, and other similar issues re: ZWJS and device drivers.....are another story.
To see if it worked for me, I'm *almost * tempted to update my five perfectly working ZEN44s on 2.10, but then, I'd have to update the Hub version. LOL. Resisting the 'beta'...for now.
I found with battery powered devices once you wake them up and start the update there was no need to wake it up anymore. It stayed awake until the update was completed. You have to wake it up for the initial interrogation of the existing (firmware target). If you don't start the update within a minute then the device would fall back to sleep. If that happens, just awake it again before the start update button is pressed.
I was a software developer before retirement, and I KNOW how poor testing can be!
I have updated several battery devices with that same hub, and while painful, the process succeeded, with an earlier version of the tool. I also have used an old community version driver for updates, before Hubitat offered the present app. So I do know the process.
I get very frustrated with this sort of issue. My ZSE44 800 series was supposed to be better on battery drain that the 700 series, but it seems the Zooz firmware in the device also has some issues which cause not only greater battery drain, but mis-calculate the present battery level. So, yes, the devices also have issues. The new firmware I'm trying to flash is supposed to fix those issues. At this point, the device will run about 2~3 weeks before completely draining the battery, and will report around 20% life remaining at the point where it quietly stops working! There is no report when it completely ceases to report in, which I find rather disconcerting in itself.
Nonetheless, I need a viable method to "fix" the device, otherwise the whole system is reduced in efficacy.
Worked.. It did take a while for file transfer, about 10 minutes. Seemed slower than line powered devices. Maybe cpu with battery powered devices is more minimal?
four quick clicks of button to wake up ZSE44 and blue led should flash indicating awakened,
yes went to JS months ago when I had Z-Wave ghost issues. Worked well enough that I never went back to ZIP. My feeling is JS has achieved parity or better than ZIP now. IMO Folks should start abandoning ZIP and move over.
I feel there is a bug on the mesh side related to what I call "Tortured ZWave Routes" When RSSi is on the lower end I think the algorithms to create and decide on multi hop routes is flawed. It can end up with unnecessary (and long) multi hop routes and never seems to migrate back to simpler more direct routes. I don't know if that bug resides in JS or the chip firmware. I suspect the chip firmware thus I don't hold much hope it will get resolved anytime soon.
