Hi everyone - I’m running HA 2025.9.4 and am using ZWave JS UI along with the ZWA-2 as my controller and I’m having difficulties getting any S2-capable device to include with S2 enabled and I need some help.
I currently have 54 Z-Wave devices on my network (including the controller) and it seems that as the network has gotten larger, it’s been more difficult to get the inclusion process to complete successfully with S2 enabled.
What I’m experiencing is that when I do manual inclusion I never get prompted to enter the last portion of the DSK and the device goes ahead and includes with no security (not even S0).
I’ve tried SmartStart inclusion - same result - no security once inclusion finally finishes. I’ve tried modifying the provisioning entry file for a single device and forcing S2 (per this thread - Z-Wave security setup failing during inclusion - #21 by EightBitWhit) and I’m still not finding success.
The ZWave network itself runs perfectly - the devices that I do have in are responsive and reliable… but I’m in a situation where I can’t really grow the network any more due to me not wanting to use unsecure devices.
Do you have all your S2 Keys setup? ZWaveJS-UI->Settings->ZWave->Security Keys
Maybe try using HA Companion App to add device …UI->Settings->Devices->+Add Device->Add Z-Wave device, Scan QR Code. Then check ZWaveJS-UI to see if it created a Provisioning Entry for the device. Then powerup the device (don’t push any inclusion button). Wait a little while for the device to announce itself and ZWaveJS to see it. BTW in my practice, I do inclusions near the controller. I don’t always get NWI to work.
I am experiencing the same and I’m also noticing that the vast majority of the devices I am adding are getting stuck in a state of provisioned, but not connected. It is quite frustrating.
I do have all the S2 keys set up… S2 inclusion has been working in the past and I’ve not changed any part of the configuration (other than migrating from a ZooZ ZST39 controller to the ZWA-2).
I’ve tried so many combinations - including the HA compantion app - to add devices.
I’ve been scanning the code in with the companion app and my phone, checking the provisioning entries, etc. I’ve tried factory resets, not touching the inclusion button, etc. You name it, I’ve tried it and the result is the same… no security.
I always do inclusions near the controller… as the process of getting anything included has gotten more and more difficult, I’ve had to resort to doing the inclusion at the controller to get anything to work (when it does).
NWI has always been hit/miss for me as well. I’ve had no issues (that I can tell) of including at the controller and then re-locating the device - whenever I do that I always give the mesh ample time (i.e, overnight) to update all of the neighbors and routes and the devices perform just fine.
Anyways - back to the topic - nothing I do makes S2 work and half the time inclusion itself won’t ever complete.
@maranhaoBruno - I see the same thing. For what will include, the devices will be stuck in ProtocolInfo for hours on end - sometimes overnight - with no progress.
Misery does love company so I’m glad to know it’s not just a “me” issue.
My question now is how do we report this as an issue? Should it go directly to the HA devs or does it go to the ZWave JS UI team? I’m thinking this is an issue at the core level (regression) for the HA devs, but I’m not sure of next steps on getting resolution (outside of this thread).
Well if you’re looking for a place to submit an issue, Z-Wave JS UI is unaffiliated with HA, so HA devs cannot help you with issues in Z-Wave JS UI. And vice-versa, the Z-Wave JS UI dev cannot help you with problems in HA. If both applications show similar behavior, well then that points to a deeper issue like in the Z-Wave JS driver.
First up - thanks for the willingness to help. I have followed all of the guidelines at the link you provided to no avail.
Here’s the stats on my ZWA-2:
Avg. signal noise (channel 0): -109 dBm
Avg. signal noise (channel 1): -110 dBm
Avg. signal noise (channel 2): -110 dBm
Avg. signal noise (channel 3): -104 dBm
Signal noise (channel 0): -110 dBm
Signal noise (channel 1): -111 dBm
Signal noise (channel 2): -111 dBm
Signal noise (channel 3): -105 dBm
Status: Jammed
I am running version 1.1 of the ZWA-2 firmware and I’m noticing that the status is switching from “Jammed” to “Ready” sporadically - sometimes flapping every couple of minutes, sometimes flapping only 2-3 times an hour… it’s inconsistent.
Jammed controller certainly is not good. Are you sure you don’t have any devices that are flooding the network, such as with excessive power reports?
Unfortunately you will probably have to start taking a look at driver debug logs, there’s no better way to investigate. You can try posting them here, or start a discussion in the Z-Wave JS Discord or GitHub project.
You bring up a point I’ve always been interested in - what would be considered “excessive” power reports? I can certainly go in and “turn down” all my devices power reporting if they are above a recommended threshold - I’ve just never known what that threshold should be… and how would I check for chatty devices?
Thank you for the links - very helpful. I’ll look them over and make sure I understand how to post good information and then go from there.
Of the 3 places you noted (here, the Z-Wave JS Discord or the GitHub project) which would you recommend to get the most eyes on it and it have the best chance of getting resolved and potentially helping others in the same boat? I’m seeing several other people in this thread with the exact same issue, and I’d like what I post (wherever) to help them out as well.
You should turn down the reports as much as possible. The “first steps” link has details on that, but I don’t think there’s a specific threshold that works for every case. Probably the sanest approach would be to turn down everything, so if any behavior and improves, and tweak it from there.
I would be cautious with assuming other people are really reporting the “exact same issue”.