Hello -
I am trying to upgrade a z-wave device over the air and the manufacturer has only .OTA files available. In the documentation of the firmware updater, it seems that the file needs to be .OTZ. Any idea how I can update the firmware with an .OTA file?
Here us the file I am referring to.
Thank you!
Linking @mike.maxwell and @csteele for possible advise
What type of device is it (brand and function?)
Wondering is you cant simply rename them, but that might be too easy
These steps work for Leviton .ota files, so they should work for whatever .ota file you have too.
Thanks for your answer. It is the Heating Thermostat HE-HT01 from Heltun.
I contacted them and they told me that my firmware 2.07 is actually the same as 2.7 and thus I have the latest version not yet available on their site... So I am not going to try crazy stuff for now.
I thought my firware was outdated as the built-in thermostat app (Heltun Heating Thermostat) does not seems complete : there is no reporting of the floor temperature, there is a useless cooling function, useless fan button... Does not seems right... But it is not the firmware of the device apparently.
Thank you for your answer. I received the info that on this device, firmare 2.07 and 2.7 are the same 
... So I will not try this now. This being said, I will keep this link as it seems to be the solution for upgrading from an .ota file.
How long should the firmware update for a single device take? I seem to have one stuck at 2% after 15 minutes of start.
Depends on the device, if it battery powered and distance from the hub. They can take a while, for battery you need to keep it awake.
Thanks @BorrisTheCat - 22 hours now and stuck at 39%.
Device = Inovelli Switch Red Series LZW30-SN
Hub = C-7 | 2.3.4.153
You should be using the built-in zwave firmware updater app on a C-7, and not this older driver that is meant for a C-5.
I remember this from my Fibaro battery powered devices when i was still on their HomeCentre.
They do a partial update in their wakeup period and it takes forever. If you can keep them awake however, this significantly should speed up the process.
For now, most important is that you see some progress at all, meaning the update is still running.
@aaiyar - I am using this - Device Firmware Updater | Hubitat Documentation - which I think is the built-in zwave firmware updater.
In that case your connection to them might be just weak.
Dont touch them until they are done, but you might check the link quality and see if you need to improve that in your situation. If the device works reliable, dont touch it!
OK! Here is something I found ...
I am now on C-8 | 2.3.5.103
So either the encryption is having an negative effect on the bandwith or the HUB has issues with the security part of Zwave. Ive seen many topics on the forum where solutions are suggestion by pairing zwave devices with S0 to solve issues. Shouldnt be that way, but it seems it is. Glad you found a workaround though
EDIT: not with S0 but pairing without security
Never ever ever ever pair with s0 it's the worst. Pair everything but locks and garage door stuff with no encryption.
S2 is with and S0 is without encryption, right?
No NONE is no encryption, S0 is a form of encryption as is S2. The problem is s0 is overly chatty on the mesh. But really pair everything with none. Less overhead
Thx for the insight, my mistake.
Some things like older locks are going to pair with s0 no matter what you do. Typically locks are fine. With other devices (lets say the 500 series 4-in-1) you would want to pair with a z-wave stick which is paired to hubitat as secondary controller so you can eliminate s0.
Download the Hubitat app
