As I said earlier, how about going to the Z-Wave settings page and click on "State" for that device?
1 Like
I had checked it before and just checked again and guess what it shows?
The new firmware. However, that is not shown from the Device Info tab under devices. Perhaps it'll fix itself after a while. See the screenshot.
1 Like
Maybe in a while. Maybe not. 
1 Like
I think you're using a C-8? I have never gotten my C-7 to work properly other than to indicate it's starting the update, but never progressing, no matter how many times the ZSE44 is "awakened". I know it was always finicky, but used to work at least back before the update tool was hidden as a sub menu in the Z-Wave main menu.
1 Like
I have seen in the past that there was some delay or block on updating the device page with a new upload. I think I may have forced with a reboot or something like that...
1 Like
Yes. I've should've included I'm using a C8Pro.
Just an add in late in this thread.
I was complaining a while ago about how laborious it was to firmware update several like kind devices. Having to wait for one before doing the next.
As it turns out you can do a few simultaneously. Just open separate windows to ZWave details and then open the firmware updater and you can have several simultaneous sessions. It just never occurred to me this would work, but it works just fine and takes away some of the wait time when you have a few devices to do.. Queue up a few and go grab a coffee and come back later...
I stopped at three session but I don't see why you couldn't do a few more. Anyway I think that's a nice discovery that could be a time saver for some.
1 Like
Semi related but don’t try this when adding devices with smart start. Been there.
I think this method might work for battery devices – it’s all based on the idea that they are normally not listening to the hub and when awakened by their respective wake-up combination, really only stay awake for seconds (maybe 10 at the outside).It appears critical that the device be awake at 2 places. The first is immediately after the particular device is selected – so before you select the device, press the awake sequence – and then select the device from the selection box within those few seconds the device is awake. If you miss that window, select a different device – and then try again – awaken the device you want and then select it quickly. The second place is immediately after you click Start update – so before you click that, awaken the device. Good luck.
1 Like
@Tom16, Thank you kindly! The method worked for the ZSE44 and the ZEN37. The process went to exactly 50% for the ZSE44and stopped with "FAILED", reporting a device number and firmware mismatch, which was untrue. I simply did another WakeUp (I kept doing them throughout, just in case...) and pressed START again. It resumed where it had stopped, and completed the process. When it said the device was flashing, I did another WakeUp, and it completed. I have no idea if the extra WakeUps were at all necessary, but didn't seem to cause any problem. I did a forced refresh and another WakeUp, and the data updated, along with the firmware version on display.
So now, I can only hope some of the device problems are solved by Zooz...
The ZEN37 is a bit different animal, but is a rechargeable battery powered device. That is on a different hub, so was easier to access everything. The "lower left" button is pressed 6 times for WakeUp. I followed the suggested sequence, and it went rather more quickly, and when done, the LED flashed red, green, and blue to indicate restart, I guess.
Wow, what a kludge of a method, both on the part of Hubitat and Zooz! The documentation is completely lacking, or, in the case of Zooz, completely in error: they claim, for both devices, a single WakeUp sequence keeps the device on for 60 seconds! They also claim that the blue LED will stay on while the device is awake, which could be true, as it turns off after 2~3 seconds!
I wish the Hubitat at least had some means to more easily restart or resume if interrupted by the device becoming catatonic. It would help if it might indicate the device didn't respond, but have a method to retry in such an instance.
Again, Thank You for the help!
2 Likes
I tried six ZEN04's simultaneously a couple days ago.
It did five firmwares. The sixth...not so much, lol.
It did three SmartStart joins.
I got in trouble once where I thought I could do an entire floor and then traipsing down to the basemen to cycle the breaker only once. Didn't work out, lol. A lot easier when a plug is on your kitchen counter vs in the wall.
I only did 3 simultaneously but 5 might be the new world record.... 
That said it is a nice work around when you have a few to do that you aren't locked to a console waiting for one to finish before starting the next.
My beef with the ZEN04/ZEN05 is I don't use the power monitoring features. But they are enabled by default settings and flood logs with inbound messages I don't care about. Would be nice if they had a single parameter to turn off all device reporting (kWh, W, V A, ...).
And that's new, lol!
edit: I've just starting checking out the power monitoring. I'm interested in how much energy my fridge uses in a month. I've found the ZEN04's reliable, so chancing it. Not that I have much in there, lol.
Although this is in a completely different topic that the one headlined, I use an Aeotec HEM Gen 5 meter on my entire house, which for several years has been rock solid. It is necessary to do some creative programming to prevent logs from swamping the hub. I have several Zooz ZEN15 Power Switches (indoor) for some things I like to monitor individually, especially the refrigerator. I use a couple to operate audio/video equipment; powered subwoofers and speakers that I don't to want to leave always-on, but like to monitor energy. I have a dashboard page dedicated to energy and power consumption, with an app that resets all power measurements at 12:01PM on the 17th of each month, writing a tally into a text log on the hub. I do use the ZEN05 outdoor switch for several specific applications, such as heaters and lights in my greenhouse. These replaced the ZEN25, mentioned below. I also have one that is used in winter to manage the water de-freezer for my chickens! The de-icer has a mechanical thermostat, but with the Z-Wave device I can tell when the heater (~260W) is ON, and how much energy is used, in genera)l. All have been reliable, so far, and rather accurate: each month, my energy usage has corresponded very well with the power company reports, although the mains company read at various intervals that don't always correspond with the 17th of the month. I have used the older, now obsolete, Zooz ZEN25 double plug. I still have a few controlling 100W plant grow lights, but have found that, while well constructed, they were among the least reliable of all my Z-Wave devices in terms of device durability; I had to toss several of them due to abrupt failure, but while they worked, they were good.
