I’ve tried several of this model of dongle and the behavior was the same on each, so presumably “switching radios” would mean switching to a different brand. Is the NVM really inter-compatible between different models/brands of radio? (I.e., can I backup NVM from this Zooz and then restore it to some other brand of Z-wave controller?)
A while ago I had tried to restore NVM from a ZST-39 to a ZAC93 (both 800LR), and it didn’t work. If I recall, the error said something about different NVM sizes…
At the moment, my only hope is that magically the 1.4 firmware for the ZST39 gets released and actually solves this problem…
Zooz emailed me a few days ago, new firmware had been released for the ZAC93 that “testing it has resolved 99% of the reported lockup issues.” Looks like ZST39 has an update, too.
Now if only I can update the firmware without bricking the zst39. (I tried doing an upgrade previously via OTW in home assistant and it bricked it. Zooz support said I should only update using the Silicon Labs software, but neglected to mention that that requires a windows PC (which I do not have).) I guess I have to roll the dice?
After a YEAR of frustration and thousands of dollars, my Z-wave network is now completely non-responsive after a recent HomeAssistant and/or ZWave JS UI software update:
Am I completely screwed? I have about 80-100 devices (many of which are light switches that are not easy to access internally (to see QR codes) and/or cut power to). I have tons of dashboards, scripts, etc. referring to these devices that it will be a nightmare to rebuild (and frankly, why would I given the unreliability of this technology???). I have tons of backups… Is there any hope of getting things back or should I just cut my losses and give up on this garbage system?
Driver: Failed to initialize the driver: WaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6977:23) at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:1061:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1913:46) at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1639:16) (ZW0100)TICS * COMPACT
Error: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6977:23) at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:1061:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1913:46) at Immediate. (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1639:16) (ZW0100)
FYI, I was having similar “timeout” problems with Zwave and nothing seemed to make it better. Finally I discovered the cause – my HA setup (on a Pi) had 1GB of RAM. Changing to a Pi with 8GB of RAM made all the problems go away.
My suspicion is that the footprint of RAM usage with all the devices and integrations that I had added over time exceeded 1GB. So as a result the OS had to spend time “swapping” memory to and from the SD card. That process is very slow, and could explain the “timeouts” that were happening. On the new hardware, memory usage runs now between 1.2 and 2GB, so the old hardware of 1GB could certainly have been underpowered.
This may not be relevant to your specific setup, but if it is I’d suggest getting HA onto a system with more memory. Good luck!
Hmmm thanks. I’m running on a pi4 (HA Yellow) with 8GB. System report says only 1.4GB is currently used… I do have a CM5 to upgrade to (also 8GB) but I don’t think I’m running out of memory…
Thanks so much for the pointer, @JohnBeMe ! That got my controller working again. (For anyone else reading this, the TL;DR is: 1. shutdown your home assistant. 2. Remove the usb Z-wave controller. 3. Boot your home assistant. 4. Shutdown your homeassistant. 5. Re-insert the USB z-wave controller. 6. Boot your home assistant.)
I still have the same problem that originated this lengthy thread – that many new devices are failing to include – but at least now I’ve regained access to those devices that did manage to include in the network. Thank you.
Very glad you got it working again, I know it can be stressful when everything just disappears all of a sudden.
I have read through this thread and I agree with what others have stated before, you don’t have an inclusion problem, you have a network problem. I’ve used Z-wave networks for over a decade and the only time I’ve had inclusion problems are as follows:
First-gen (Zwave 300-series chips) locks: they use “whisper mode” for inclusion so the controller needs to be right next to it.
First-gen Z-wave devices (non Z-wave+) that don’t support network-wide-inclusion (NWI). Without NWI support, the device being added to the network needs to be within 1-hop of the controller, in other words, not too far away.
You haven’t built out your mesh network properly. When adding devices, you need to work outwards from the geographic center of the controller. As you keep adding devices starting from the center, the mesh network gets stronger.
You’re trying to add devices at locations that are simply too far away. That’s why I have a test-rig, it’s simply a piece of wood with an electrical box and power cord mounted on it. This allows me to install a dimmer in the box and plug it in near the controller, and troubleshoot it from there.
You have a faulty Z-wave device somewhere. They can wreak havoc by either transmitting continuously or not relaying packets at all.
It would be interesting to know what device you’re currently trying to add that won’t include properly.
I’m using a Zooz ZST39LR controller, and most of my devices (including the ones that are failing to include) are late model Zooz switches, Aeotec sensors, or Swiget outlets. So I don’t think it’s an issue with early/first gen devices.
The problems don’t correlate with distance from the controller. I’m struggling with devices a few feet away… and am fine with many devices much further away. I also have cases of big problems with one switch in a gang box while another in the gang box is just fine. It’s also a pretty dense network, so I don’t think devices are struggling with signal strength.
Faulty Z-wave device is totally possible. I have a lot of devices… No idea how to even begin troubleshooting this, as many devices are built in (so I can’t unplug them one-by-one) and they’re on circuits that have other things that can’t be switched off (so I can’t flip breakers one by one). FWIW it doesn’t feel like a case of “faulty device is a weak link in the mesh network and downstream devices fail to connect” (since there is no spatial correlation between the problem devices) but could be a case of “faulty device swamps the network or occupies the provisioning slot, so other devices can’t do their things”…
My process for including hardware devices (e.g., light switches or power outlets) has been generally like you describe: connect temporarily to a stripped extension cord and plug in next to my controller, then try to include, then my electrician installs the “pre-included” device in it’s “real” location. Unfortunately, a number of devices just never successfully included – and when the electrician came by he went ahead and installed them unincluded. I’ve been trying to get them online since. (And a few that were included have dropped out.) I did manage to copy the DSK QR codes before the devices were installed, and they’re sitting in the “Provisioning Entries” section of ZWave JS UI… Periodically I will get a new device appearing in my devices list of type “Unknown Manufacturer” / “Unknown Product”, but it stalls out on “ProtocolInfo”…
To the best of my ability to guess something weird is going on that causes devices to fail to complete an initial “ProtocolInfo” interview(?)… and rather than moving on, the controller hangs on this… sometimes for days… and it seems to only try to add 1 or 2 devices at a time, so others never get a chance. It also seems like whatever is going on also strains the bandwidth of the network (hence the repeated failures of OTA updates…)
I’d really appreciate any ideas (other than suggestions to start over or to remove all devices and try re-adding them one by one…)
Thanks!
To properly include battery devices, you need to manually keep the device awake (by performing it’s wake up command over and over and over). If you have any that are not included, it will take days for the include to finish based on battery device wake cycles. Mains devices are typically simple, if you get unknown manufacturer with a mains device, re-interview the device.
@istapeter The current “unknown device” is listed in ZWave JS UI as a mains device. I don’t know what device it is, of course, but it just sits for days on “ProtocolInfo”…
I’ve developed a “ritual” that I’ve been using whenever I have a ZWave device that has problems with inclusion. I use an old Aeotec Minimote ( https://products.z-wavealliance.org/products/143 ) to reset the problem device. The Minimote appears to be discontinued but one of the newer similar devices may work as well. The process I use is:
The Minimote should itself be excluded from any Zwave network, i.e., it is not on any ZWave system.
open the lower door on the minimote to expose the 4 additional buttons
hold the minimote as close as possible to the “problem device”, and push the “minus” button (exclusion) on the minimote. The LED should start flashing red.
on the problem device, do whatever it requires to start inclusion/exclusion (hit switch paddle, push button 4 times, whatever…)
within a few seconds, the LED on the minimote should flash blue for a few seconds, indicating it has successfully communicated with and reset the device. Then it will resume flashing red, indicating it’s ready to exclude another device. If it doesn’t, try the exclusion action on the problem device again until you see the LED flashing blue (or give up)
push any of the top buttons on the minimote to get it out of the exclusion mode, so you don’t accidentally remove other devices from your network!
now use your normal technique to add the problem device to your ZWave network
I’ve used this ritual to migrate 100+ devices from one controller to a new ZST39-LR. One device to go, as soon as I get a ladder out to get up to where I can push the device button 4 times within 2 seconds…
