[RELEASE] Z-Wave Firmware Updater

I've given up on fancy ways, I want to remove the PC Controller Software from being a secondary hub (or whatever that's called) for my Hubitat but I cannot for the life of me figure out how.

Specifically, right now my PC Controller software can see my whole network, talk with the hub and so on. I want it to be standalone again so it's not associated with my hubitat.

I tried excluding it from HE and doing an NWE, but ... it's still talking to it all. After several more tries in various ways, I removed the device from HE, then force removed it when it couldn't remove. And yet PC Controller software can still see and control everything.

Any thoughts on removing PC Controller from my network? There are a few threads in these forums on this problem, but none have resolution.

Rubber duckie, you're the one!

Or is that better as "Ask, and the answer will come to you just before the first person answers?"

The DB was still on the stick. Answer was, in case anyone else needs to do this:

  1. Exclude device from HE
  2. (I'd close and reopen the ZWave PC Controller software at this point)
  3. In the PC Controller software, click Network Management
  4. Click your controller in the tree on the left
  5. In the center bottom is a "Reset" button. Give it a click.

And that cleared it.

This firmware updating tool is a great addition, but it would still be helpful to have a more comprehensive tool built into the Hubitat platform. Some thoughts:

The "biggest" advantage would be to have a comprehensive tool built into the platform that is able to update multiple devices of the same type. My thoughts on this . . .

  1. Using the Z-Wave manufacturer / device codes, the tool should be able to give you a listing of all of the "same" devices and their current firmware versions. You could then tick a check box identifying which ones you would like to update (generally, one would expect that you'd want to update them all) and a box to enter the firmware URL
  2. The tool would then allow you to begin the update process immediately, or on hub reboot, or at some time of day (middle of the night perhaps). My thought is it may be "safest" to update on a hub reboot before the hub starts processing other applications, etc.
  3. There may also be an option to "repair" the Z-Wave network after a firmware update. From experience on HomeSeer, I've seen cases where a firmware update causes nodes to forget their routing and need a network update - maybe that needs to be considered, particularly if the network has some nodes that aren't Z-Wave Plus or better.
  4. A progress indicator should be displayed informing the user how many devices remain to be updated.
  5. After each update, there should be a check (i.e., ping or otherwise to the device) to ensure it is responsive after updating - Also a check to see if any device commands have changed which might necessitate changes to the driver data - if a device fails, try again or stop the update process and don't update other devices until the user confirms that everything is OK - i.e., to be sure you don't brick devices.
  6. Longer term: Perhaps there could even be a provision within a driver (e.g., a driver attribute) that has a manufacturer-provided URL to a firmware source and the system could automatically check weekly to see if there is a firmware update.

I have tried to find the Z-Wave Firmware Updater driver for multiple devices (includig 2 DZ6HD's) but have had no luck. I've done a refresh and configure. Also the hub is fully up to date. It's never an option. Am I missing something?

Not sure what you are asking. Did you install the driver? If not, are you asking where to get it and how to install a user-written driver? This is not a built-in driver.

Oh, and welcome to the community!

1 Like

There are basically two ways to get this. Manually importing it (link to Github in first post) or by using the Hubitat Package Manager. Package Manager is nice because once you get the app installed, it is much easier to search for new community based apps and drivers, and it simplifies installing and updating things, especially something like Echo Speaks where there are multiple apps and drivers needed for one (main) application.

Again, you will have to import this Github raw link into the Apps Code section of Hubitat, but once you do that, it is fairly straightforward from there.

Just a caution: there are two versions of the updater, which one you need depends on the type of update file you are uploading. Unfortunately, both versions have the same version number, so it’s confusing, both to users and to HPM. For this reason, this is the one driver that I’d suggest not using HPM to do the install. Instead, figure out which type of firmware file you have, then read the first post of this thread to understand the types of files handled by the first version of the driver, then scan through this thread until you find the code for the second version with a discussion of the file types for it.

1 Like

You are correct, there are two updaters. But given these are DZ6HD Leviton, I think (please double check me) that the original one is what you want.

So, if yours is a boot loader included hex file, you need the version in the first post of the thread. What is the type of your firmware update file?

Here’s the first post of the thread with instructions and a GitHub link to the driver code:


And here is a link to the “new” version with comments by the programmer:



Well I don't know how I missed that but thank you @neonturbo and @672southmain ! I'll go get that driver added right now.

And thanks for the welcome @672southmain. Sorry I missed that snippet of code. Sleep training my kid which means I get very little :stuck_out_tongue:


So for the DZ6HD's do we use the original? I could never get that to work with the original haha, was hoping this updated version would be better

I don’t have that device, so I can’t answer. What type of update file (file extension type?) do you have? That is the determining factor.

1 Like

I Was using Leviton-DZ6HD_01_20.hex from https://raw.githubusercontent.com/djdizzyd/hubitat/master/Drivers/Z-Wave-Firmware-Updater/Leviton-DZ6HD_01_20.hex, but looks like that's gone now actually

If you can find a copy of that file, .hex work best on the original (first version).

1 Like

Though not in the case of this particular DZ6HD I guess, but thanks

Anyone else still having issues with the "please wake up your sleepy device" error? I've been trying to update an Inovelli lzw-31-sn and a lzw42 and both of them fail at the same error. I tried to capture logs and what not when I tried updating the lzw42 but this is all I get in the logs.

dev:2 2020-08-26 11:08:03.244 am debuglocked by:

On the device page the current states are as follows:
Current States
firmwareUpdateProgress : Please wake up your sleepy device
lockedBy : None
currentFirmwareVersion : null
firmwareUploadPercent : null
firmwareTarget : null
manufacturerId : null

I have to be doing something wrong because it looks like its doing nothing. I have tried loading the file locally and using http://192.xxx.yyy.zzz:8080/local/LZW42_2_30.hex and I've tried using the direct link from inovelli http://files.inovelli.com/firmware/LZW42/Beta/LZW42_2.30.hex both fail with the same output.

I read that it may be related to being connected directly to the hub and because this is a brand new C7 device I removed all devices and only had 1 device connected and the hub was only 3-4 feet away and it still failed with the same issue.

Any help would be greatly appreciated.

Which version of the updater are you using? See my post above:

I have used both versions of the updater and they both fail the same.

Download the Hubitat app