I’ll add my experience…
I have a Z-Stick Gen5 w. 1.00 firmware. I have had it for several years, and thought it was a good time to get another stick just in case it failed (and not wanting to wait several days to get a replacement), so I bought a Gen5+ which comes with the 1.02 firmware, so that is what I am currently using in my operation. I still wanted to upgrade my Gen5 to 1.02, and if I bricked it, then I would still have a working Gen5+. I contacted Aeotec support and they provided instructions and the 1.02 firmware (and Windows upgrade drivers) for upgrading the Gen5. These look like the same ones provided by prilly. I successfully upgraded and tried it out operationally and it worked :), so for now all is good.
2 Likes
What’s the difference between 1.00 and 1.02? The Aeotec website says:
- If you are not using SmartStart in Z-Wave or not planning to, this firmware won’t change much for you.
So any other changes (e.g. faster response)?
I’m usually in favour of updating to a latest version, but since this is the most critical part of my HA instance, ‘if it ain’t broke, don’t fix it’ will also work for me 
Newer zwave SDK that allows you to export the NVM so you can import it to another stick.
Flashed the EU 1.2 update without a problem. The LED can’t be disabled anymore however. It’s steady yellow while charging and steady green when charged. This can’t be turned off for now untill someone finds the new hex adress…
I’m doing that already with Z-Stick Gen5 Backup Software : Aeotec Help Desk. Or is that not portable to a new stick?
The option doesn’t work anymore on a Gen5 ZW090 with FW 1.2 (or 1.02) . I’ve opened up a ticket at Aeotex Support to ask them to update the software.
This software only allows you to backup the NVM and restore it to another Aeotec Gen 5 stick, not import it to another stick.
If you have the 1.02 firmware you can export that stick to other sticks via zwavejs2mqtt.
Ok, I had to press the Enable/disable checkbox multiple times in the Backup software. After that, the LED could be disabled, even on FW1.2!
For me this update, coming from 1.0, fixed that in Zwave JS I do not have to manually “enable” the devices any more after the container was booted. Previously I had to “Re-intervew Device” to enable it in HA (is was grayed out as a device) every time to host or container restarted.
Hi
I’m confused. I have the ZW090 GEN+ aeotec dongle and the information on ZWAVE-JS-UI are
FW v1.1
SDK v4.54.0
Do I have to upgrade to 1.2 ? I don’t understand if 1.02 is 1.2 ?
Which changes between 1.1 and 1.2 ?
1 Like
Mine shows FW: 1.2 and SDK: v6.7.0 as I did the upgrade when it was publically available. If you are not having any issues with Z-Wave, I wouldn’t worry about it.
It may be possible to request the firmware from Aeotec support, but be aware that there have been reports of people bricking their Z-Stick, so make sure you take a backup of it first.
Although they are the same version, ZWaveJS will call the stick’s version 1.2, whereas Aeotec will call it version 1.02.
The reason I upgraded my stick from 1.1 to 1.2 is because 1.2 is required to do Smart-Start inclusion.
It’s been available again for some time now. Personally, I think SmartStart is well worth the marginal risk involved in updating.
I hadn’t realised it was back. Confusingly, it’s labeled as " Z-Stick Gen5+ V1.02 firmware update" but it is for the Gen5.
I have the Aeotec Z-Wave Gen5 stick. Recently started using it in Windows with Z-WaveJS UI. Having some oddeties where it starts failing to communicate with devices. Tried upgrading the firmware from 1.01 to 1.02 but didn’t help. Think it’s related to HWInfo app when I launch it and it queries devices. HWInfo person feels it’s the firmware/device/driver of the stick that it’s doing this. That said, I have the Sigma Designs driver I found on Aeotec site dated 6/10/2013 and renames the device to UZB (COM3) in the Windows Device Manager. Pretty old. Is this the latest driver available? Figured if there was something newer maybe would play nicer.
so just updated my stick ,
Z-Stick Gen5+ V1.02 firmware update : Aeotec Help Desk,
had to use method 3 to get the drivers to work,
showing 1.2 and no missing nodes
I don’t think anyone has proven it works for a Gen5.
Given Aoetec indicates applying a firmware update can brick the stick (and hence cause you to lose the zwave network) proceed with caution.
When I did this I used the aoetec utility and two gen5 sticks.
I did the following with there utility (shutting down and restarting it between each step(
- first I backed up the gen5 stick that was being used
- second I grabbed a new gen5 stick, upgraded it to new firmware
- third restored backup from step 1 to new stick
Plugged new stick into zwavejs and restarted. Verified network was ok and let it run for a day.
After that I shutdown zwavejs, took a backup of the new stick, upgraded the old stick then restored. So now I have two identical sticks.