Hello, how did you manage to fix your blocked key, because I am in the same situation as you?
Has anyone tried 1.50? Is it safe to use this version now?
That’s the recommended version. Zooz even pulled the previous versions, 1.50 is the only one available. You only need to upgrade if you have problems.
I’m really not sure what you mean with the question 
Yes I finally flashed today. A kind of interesting story of how I got there too. For a few weeks I had been running two separate Z-Wave networks, both using it’s own ZST39. Because of an absolute insistence that the adapter be referred to using the “by-id” name, this was not a viable long term solution for me. So I got a HomeSeer SmartStick G8 for my secondary (non-LR) network. That solved my problem easy enough, but I noticed they just put out a firmware update based on 7.22.2, while this v1.50 from Zooz is based on 7.22.1. I still have not tried to find changelogs to see what differences might exist.
HomeSeer released their update packaged with what seems to be a purpose made runtime of Silicon Labs Simplicity Studio. Which btw I’ve never been able to get working despite trying on 3 different Windows PCs. An absolute abortion of an application. Well this runtime updated the SmartStick straight away without any drama. The readme does have some pretty scary warnings that you should never use the flash updater with anything other than the SmartStick. Well I have two spare ZST39 so decided to try it on one of them and it worked just the same as on the HomeSeer G8. So I then flashed my working ZST39 and have been running 1.50 for a few hours now. I had been having some intermittent issues that finally threw me over the edge this morning. I had several nodes, including SmartWings blinds and several ZEN32 that were completely non-responsive, yet not showing dead either. It used to be that I could soft reset when a node would go dead, but if it’s not even showing me that… well I’m pretty near the end with Z-Wave. It’s been an abusive relationship since before there was even “Plus”.
1 Like
Unable to use the Update function in HA Zooz integration to update my ZST39 USB stick to 1.50. When you updated yours did you have to disconnect the devices, exclude anything, or just use the Simplicity Studio with the downloaded firmware? Thanks for your reply.
I can add some info to this topic, I think. I am not sure what firmware I was running, but things were working relatively well. I was chasing down an odd behavior, and I followed a forum post with a link directly to a firmware. I blindly followed and updated. It was
ZST39_SDK_7.22.0_US-LR_V01R40
I initially bricked the 800. I was able to recover it with a method on my laptop with this command
npx @zwave-js/flash COM5 c:\temp\ZST39_SDK_7.22.0_US-LR_V01R40.gbl
Yeah, I now know that is a bad firmware. Nothing worked at all. I couldn’t successfully perform a single zwave device action (add, remove, etc.). All my devices were gone as well. I ended up restoring from backup before I made this mess. Still nothing working at all. I figured what the hell, it can’t get worse. I found
ZST39_SDK_7.22.1_US-LR_V01R50
and was able to install it with Simplicity Studio. From what I can tell for the last 7 hours or so, it is working perfectly. I was able to reset all my zwave devices and add them back. Now that I have a slightly better understanding of what can go wrong with a zwave environment, I will try to learn about NVM backups in case of failure. That is a new concept to me.
.
Thanks for letting us know! I was contemplating doing the same…
So, what will be the better FW for the ZST39 then? The 7.18.3 or the 7.22.1?
I am curious to find out what you guys use, as I have ordered the ZST39 to replace my Aeotec Gen 5 stick.
The 7.22.1 firmware is the recommended fw. All other firmware has been removed so you can’t download it anymore.
1 Like
Ah ok. Thanks. 