What a pain in the… I have been trying for months to connect this thing. Even warrantied it and got a new one. I have several kwikset 916 locks and had no problems connecting them. It is really cool when HA thinks its a door/window sensor or something else when adding it. The only few times it did connect securely it showed up as an Aeotec Multisensor. Each time I tried to re-interview it several times to see if it would show up correctly with no luck. Even tho it connected securely I couldn’t control it. I’ve tried holding my stick to every side of the lock with no luck. With it installed in the door and not installed. With it showing up as the wrong device when it connects securely it makes me think that something is wrong in HA. Could the lock have a firmware that is not supported? Several items on the install paperwork are wrong. Like I had to enter 7 digit code even though it says I can use a 4 to 8 digit. I tried a 6 and it would not except it. I tried on both the sticks that I have connect. 1 is an Aeotec Gen 5+ and the other is a Zooz 700 series. I’m running HA on a rpi4. The aeotec stick is connected with Z-Wave JS and the zooz stick is connected with Z-wave JS UI.
I have one of these. Zwave finds it fine. I will say it is located on the edge of mesh, and so it has dropped a few times off the network, but I never had any issues with identification.
Try Legacy security if you havent already.
I got rid of one of these a few months ago. Didnt have any issues.
Have a 916 now and had to upgrade my coordinator to get it to pair reliably.
Good call.
Mine is setup as S0 Legacy.
I have tried selecting S0 Legacy. Its weird that when it connects not securely it has the correct device just the lock is greyed and missing battery level entity and when it connects securely it is the wrong device the lock is not greyed out but can’t control it. In the hundreds of attempts to connect it I had one of my Go Control Garage Doors disconnect. It has to be S0 Legacy also. When it connected not securely I got battery level entity which I should have. When it connected securely I lost the battery level again. It took 5 tries to get it connected securely but that has been the norm when connecting S0 Legacy devices for me. Plus it was still mounting in the garage when I reconnected it. I haven’t checked recently if there are updates to the coordinator but I have 3 916 and they connected right up with little problems. I can’t remember if it was 23 or 22 but I switched the coordinator from a Zooz 700 to a Aeotec Gen5+ because I was tired of the dead nodes. That was fun reinstalling over 120 devices. And just recently added the Zooz 700 back to get a few high traffic devices off the main z-wave network. I have tried restarting HA, rebooting HA and even powered everything off for a few minutes. I even tried a few times to connect it to the Zooz 700 with no luck.