Zooz 800 Z-Wave-USB-Stick not working after update to V1.30 about core HOT 11 OPEN

I am dealing with the same issue and wanted to provide some more information. Upgraded to try and fix some compatibility issues and hanging issues with some devices as per Zooz support. When the stick hangs it requires a power cycle. A restart or even reboot of the HA server will not fix it. You need to power HA off and back on or unplug the stick and plug it back in. Once I do that it will start working again for 2-12 hours it seems like. Most of the time when it hangs the blue LED light on the stick is off. I have a case open with Zooz and will report back anything I learn.

from core.

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

from core.

I have now attached a log file of my Z-Wave JS, when that happens. Hope that helps.

home-assistant_zwave_js_2024-05-28T16-26-19.319Z.log

from core.

There is a long discussion about this in another thread: #104230

Basically boils down to a code issue that only Silicon Labs can fix in the 800 firmware. Until they fix it, all manufacturers of 800 devices are affected.

edit: copied the wrong link

from core.

Your link does not work.

Zooz support got back to me yesterday and said “At the moment it is unclear if this is because of a) the new SDK 7.21.3, b)ZST39 custom firmware, and c) the HA/Z-Wave JS issue”

So they are not saying it’s firmware related yet. Said it could be a zwave JS compatibility issue. I highly doubt that is the case as silicon labs does not seem to have a good track record fixing bugs with this dongle.

from core.

Fixed the link... wasn't familiar with referencing other issues in syntax :). Overall it looks like a big finger pointing game. At this point I've put my Zooz 500 controller back in until they can get this mess sorted out. I've heard some rumblings of staffing issues at Silicon Labs so hopefully this isn't indirectly related.

from core.

So far 1.20 works ok for me. I have a Zooz ZEN14 that keeps going dead on me along with a half a dozen HomeSeer switches. The ZEN14, Zooz does not know what the issue is as they wanted me to upgrade to 1.30 which was a nightmare. HomeSeer thinks its that encryption is enabled. They just lock up every week or two and when they do most of the time even the button on switch itself does not work. That does not do well for the wife approval factor. Going to exclude/include them next weekend when I have time and see if that fixes the issues. I still have another 30 zwave devices still on Smartthings that I want to migrate over but concerned its just going to cause me a bunch of other problems. :/

from core.

WAF is definitely a big thing. Thankfully all my lighting is on Lutron so that saves my bacon there. As much as it is frowned upon, I only use encryption when necessary (like locks, for instance) because it seems to cause issue with older Z-wave devices. I have some older 300 plugs around my network and as long as S2 is disabled on everything that isn't required, it works great. Luckily I'm moving so the Lutron system will go and it'll be my chance to upgrade everything to current ZW specs -- I had hope for the 800 adapter but it's definitely shelved until some stability can be obtained. It's bad when my BLE devices are more stable/reliable 👎

from core.

See Z-Wave JS bug here --> 6874

Note this is different from the "jammed" issue, and "switched to ready" to "switched to unresponsive" loop is a new (fun!) issue with fw 1.30 -- TL;DR don't upgrade to 1.30 yet or you'll likely effectively brick your ZST39. I was able to restore my network to a new stick I ordered as (thankfully) took an NVM backup before upgrading and the new stick came with 1.20.

from core.

See Z-Wave JS bug here --> 6874

Note this is different from the "jammed" issue, and "switched to ready" to "switched to unresponsive" loop is a new (fun!) issue with fw 1.30 -- TL;DR don't upgrade to 1.30 yet or you'll likely effectively brick your ZST39. I was able to restore my network to a new stick I ordered as (thankfully) took an NVM backup before upgrading and the new stick came with 1.20.

Thanks for pointing that issue out. It seems like new posts keep getting added every few days about similar issues. This particular issue you mentioned is more like what I was dealing with. The only difference is my network was completely quiet and failed no matter what firmware I put on the stick. I ended up restoring my 500 controller and my network is flawless again. Going to let the 800LR controller bugs get worked out before I jump again.

from core.

Thank you for the info, I had the same problem also when I setup the Zoom 800 Stick I got a warning had to up grade firmware so, I did Upgrade and it was the worst thing to do. Since then I started get switched to unresponsive like every 10 to 30 seconds. I see a lot of Note stating I can't downgrade 18 Ver of firmware. So I took my Aeotec 500 restored Back and it's work fine. But I get some drop outs from the device at the end of the network. That's Why I upgraded in first place so should I wait until new Firmware or will it get fixed in JS-Z-wave in future., or does anyone have any other idea or other option.

from core.