I have over a dozen Zooz devices. Most work fine with S2 security. The two ZSE42 leak sensors I own are an exception. When I add them to Home Assistant with S2 security, either authenticated or unauthenticated, it shows no sensor entities, and thus I’m not able to create any trigger with them in automations.
Strangely, if I exclude them and add them with S0 security (legacy), the sensor entity shows up, and everything works fine.
I’d like to report the problem to community developers, but I’m not sure where to do so on github. I’m using HAOS. Any help would be appreciated.
Is the device in the ready state? I’ve observed the same, but a re-interview solves it. I did have to wake it up twice to complete. I think this device, and other Zooz ones, have problems during interview when S2 is enabled. I’m more inclined to blame it on Zooz, than Z-Wave JS.
Yes, that makes no difference at all. They are essentially the same, except S2 Unauth does not need a PIN. Just to confirm again, after you re-interviewed did the node go to “Ready: Yes”?
I just re-included the node with S2 Auth. The Notification CC values were missing. I re-interviewed the device. Press the internal button 4 times quickly, and the interview was stopped. Press the internal button 4 times quickly again and the interview finished, and the Notification CC values are present. I can pretty much reproduce this every time. I had meant to submit a bug in regards to this device awhile back, but didn’t get to it.
When I reinterview with S2 Auth, the process starts, but does not complete. But actually, the “Water leak detected” sensor actually showed up afterwards !
What do you mean by “Notification CC values” ?
I contacted Zooz support about the issue with S2 Auth on this device, went through many procedures including factory reset, exclusion, inclusion. They are blaming Z-Wave JS for this problem. They told me to contact the developers. Hence my post.
Right, you need to wake it up (press button 4 times) for it to complete. From your latest screenshot, it looks to have finished this time.
The default wet/dry sensor is based on a Notification Command Class value. The initial interview always fails such that the Notification CC values are not discovered, which means the entity cannot be created. When you re-interview, it successfully discover the Notification values, and so the entity can be created.
Yeah, they tend to blame Z-Wave JS most of the time, and usually it turns out to be their devices at fault. There are number of devices that have workarounds enabled to avoid bad behavior. Based on this history, my initial blame is on the device. I don’t have problems with other S2 devices. It’s worth it to submit a bug though (on Github at node-zwave-js), and see if anything can be determined. If you don’t get to it, I eventually will.
What difference though? Based on this screenshot, you’ve got it working now. The unavailable battery devices are due to an interview error with the Battery CC, you can just delete those. Otherwise, you have the same result as I do. I’ll upgrade my firmware and see if there’s any difference in behavior.
Yes, using your post and waking it up twice (before the interview starts, and again after it starts), it completed. I did it successfully for both my ZSE42.
