Zooz 800 Z-Wave-USB-Stick not working after update to V1.30

[AuPaGri]

The problem

Hi,
yesterday I updated my Zooz 800 Z-Wave USB-Stick (European version) from V1.20 to 1.30. Since than Z-Wave is working for some minutes after starting HA, than it stops and in the "800 Series USB controller status" I get lots of error messages, it changes from "switched to ready" to "switched to unresponsive" like every 10 seconds.
I downgraded to 1.20 and everything is working fine. Don't know, if this is a problem of the Z-Wave stick, Home Assistant OS or Z-Wave JS (0.5.0).

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS (0.5.0)

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[AuPaGri]

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

[cf-mp]

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.

[kk3844]

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

[cf-mp]

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.

[kk3844]

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.

[cf-mp]

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. :/

[kk3844]

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 👎

[kreucher]

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.

[kk3844]

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.

[djecot]

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.

[tmsteinhardt]

I upgraded to 1.30 and have the issue of switching between ready and unresponsive every 5-10 seconds. Anyone have a link to the old firmware so I can downgrade mine?

[AuPaGri]

You will find all firmware versions here:
https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/

[tmsteinhardt]

You will find all firmware versions here: https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/

Thank you! For some reason I couldn't find that page.

[tofurky]

1.40 based on sdk 7.22.0 (2024/06/05) was just released per https://www.support.getzooz.com/kb/article/1352-zst39-800-long-range-z-wave-stick-change-log/; curious if this resolves the issues seen with 1.30. from sdk change log "Z-Wave NCP controller stability improvements" (https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.0.0.pdf).

[AuPaGri]

...who will give it a try and tell us all??? ;)

[tofurky]

so far so good with zwave-js-ui 9.16.3. flashed via HA 'UPDATE' button on Device info. it's only been about 15m, though. i'll be sure to reply here if i wind up encountering any issues with it.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.