Well, no luck using the binary firmware updater device driver, which was the process that was suggested by Chris of Aeotec (@ccheng). Here is the result of trying that on my C-7 running 2.2.4.148:
It may be that the Binary Firmware Updater driver by Bryan Copeland (@bcopeland) was specific to the C-5 and earlier Z-Wave radio and stack, or that something in 2.2.4.148 broke the driver updater on a C-7 running 2.2.4.148.
I had previously used the Firmware Updater driver months ago, on an earlier firmware version on my C-5, to update my Zooz ZEN16, which was part of an early production run whose firmware did not match the firmware version on the ZEN16’s underside, so I know that I can make the driver approach work on my C-5, but I have never used it on my C-5 running 2.2.4.148. I have used the Device Firmware Updater app on my C-7 running 2.2.4.145 to update my ZEN16 to its recent firmware update.
So, now, it seems I have a few choices:
(1) try my C-5 on 2.2.3.148 (the oldest firmware the Diagnostic Tool will allow me to restore) with the Firmware Updater driver;
(2) try my C-5 on 2.2.4.148, the version it is currently running, with the Firmware Updater Driver;
(3) try my C-7 on 2.2.4.148 using the Device Firmware Updater app.
I was unable to update the firmware on the Aeotec using the Device Firmware Updater app when I tried before, but, apparently I ran into two Firmware Updater App bugs:
(a) any update following an update for a now-removed device would fail. Because Zooz requires that the ZEN16 be removed, reset, and included following a firmware update, the Aeotec update failed. Workaround, until this is fixed, is to delete the Device Firmware Updater app and add it back.
(b) the “sleepy device” issue that Bryan has now explained.
I will try again.
Sigh.
