Release 2.4.3.155 - Possibly fixed firmware update timeouts

🛎️ Get Help Devices
1

@bobbyD @gopher.ny
I’ve been struggling getting through FW updates on zooz ZSE41 on my C7 with the Device Firmware Updater. Most other zwave devices will update quickly after disabling the device, shutting down the hub and removing power.
Because i have consistent success on so many other devices (Aeotec Multi 7, Zooz zen 32 / zen 52 / zen71) I was not considering this to be a hub issue, but with the update in 155 I decided to try again after updating the C7 update w/o success. FW update seems to hang around 10 - 50% only on zooz ZSE41’s after 24 hrs of waiting.

I have managed to get 1 FW update to work after hard resetting the device and pairing w/o S2 and that was my plan to finish off the rest. If there are logs on my hub you guys can use to help improve the process just let me know and i’ll send you my hub id.

2

So am I understanding that this is the only device that you have trouble updating?

This is a sleepy device.. Have you disabled the device's driver (to prevent it from putting the device back to sleep) and woken up the device right before starting the firmware update?

1 Like
3

Yes, i have disabled the device and the multi 7 is also a sleepy device and i’ve gotten through several of those w/o issue. The zooz ZSE41’s on my C7 are the only devices i can consistently reproduce firmware update issues that look like they could be due to timeouts after updating my hub to .155.

I dont have access to any logs to know for sure, but if reproducing the issue on my hub can generate logs to help push zwave firmware update timeouts to resolution then I’m happy to help.

If my symptoms don’t match the symptoms for this issue, no worries. I know the steps i need to take to finish off my annual firmware updates.

4

@bcopeland

Just wanted to add a note on this subject - I updated FW on two iBlinds last night and both of them updated quickly and easily. One was joined w/out security, and the other had S2 authenticated.

I did have to remove and re-add the FW updater app between devices, as when I went directly to the second device the update was super slow, like the bad old days when FW updater could be almost unusable. I removed and re-added the FW updater app, started the second update again, and it went smoothly and quickly.

Very nice!

1 Like
5

Was that on JS or ZIP?

And to get the 2nd update going, you did not need to reboot the hub in between (i.e. in addition to remove/reinstall updater), is that correct?

6

Sorry - should have noted that - this is on Z-WaveJS, which is behaving very nicely for me lately, thank you very much @bcopeland. :slight_smile:

Yup - did not have to do any hub or device reboots at all...just removed/re-installed the FW update app and things were GO! :slight_smile:

1 Like