Quickset 916

Rich37804 · February 21, 2024, 11:53am

I have this lock working well with the exception of one annoying bug…
When the lock jams, like if the door wasn’t closed all the way, it doesnt report the jam and also drops from the zwave network.
My son had some friends over a few nights ago and someone didnt close the door all the way. As a result, the lock dropped off the network and no notifications were sent. The door was basically open all night.
This is the only lock that meets the WAF due to the rest of the door handles in the home. There is a zigbee version now, but I dont feel like spending the $200…
Pretty sure this is a zwave/firmware bug and there is nothing I can do on my end…
Not sure if anyone else has experienced this…
The lock:
Kwikset SmartCode 916 Z-Wave Smart Lock, Keyless Entry Ring Compatible Door Lock, Touchscreen Electronic Deadbolt, SmartKey Re-Key Security, Smart Hub Required, Contemporary Matte Black - Amazon.com

swamplynx · February 21, 2024, 3:56pm

I have this lock and a few other Kwikset Z-wave locks. Starting late 2023 I two of them started dropping off the network. Before then they were rock solid, so I’m not sure if it is a device firmware issue or something with Z-Wave JS UI… In my case, when manually unlocked or the PIN pad is used they would then reconnect. I haven’t associated it with a jam signal, but you very much could be correct, as I do notice they drop after a lock command… I did however fully exclude/remove one and then re-pair it and it seems to be working fine. Not a solution I know, but something to try.

Similar issue below, but could not find anything else specific in the zwavejs github issues.

github.com/zwave-js/node-zwave-js

Issues with Kwikset 914 (nodes going dead, jamming up entire

opened 02:37PM - 19 Apr 22 UTC

closed 12:09PM - 16 May 22 UTC

jdiegmueller

stale 💤 Tech Support 📞

### Is your problem within Home Assistant (Core or Z-Wave JS Integration)? NO…, my problem is NOT within Home Assistant or the ZWave JS integration ### Is your problem within ZWaveJS2MQTT? NO, my problem is NOT within ZWaveJS2MQTT ### Checklist - [X] I have checked the [troubleshooting section](https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index) and my problem is **not** described there. - [X] I have read the [changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md) and my problem was **not** mentioned there. ### Describe the bug Hello! I have three Kwikset 914 deadbolts that I am having trouble with. I have a fairly active 131-node Zwave network currently powered by ZwaveJS 9.0.2 & ZwaveJS2MQTT 6.7.1 on a Raspberry Pi 4B, installed by npm. I am using an SiLabs UZB-7 (with 7.17.2 firmware) as the controller. I currently have HomeAssistant 2022.4.5 talking to this setup. What I am observing is that sending lock/unlock commands to the three deadbolts results in a variety of intermittent behaviors -- none of these necessarily happen "every time", but all happen very frequently: * slow response (often as long as 10 seconds or more) to lock & unlock commands * incorrect status after slow lock & unlock commands (ie, deadbolt may lock/unlock after a multisecond delay, but the status will not change to locked/unlocked) * deadbolt node going "dead" (and requiring a ping to come back alive) * commands to other Zwave network effectively freezes up for a period of time when the above happens -- commands to other devices This probably goes without saying, but the behavior tends to compound when trying to interact with multiple locks in a row -- for example, issuing a lock command to all three deadbolts at bedtime will typically jam up other Zwave commands for quite some time. I've made this behavior a little less painful by introducing a short delay between each lock command (3 seconds in the log I'm going to attach). PS: Last thought I thought might be worth sharing: Even though the three deadbolts are the same model, ZwaveJS detects one of them as something different (although all three report the same v4.10 firmware). I have observed these same results even after re-interviews, and exclusion/re-inclusion cycles: * Node 12 detected as Kwikset 914/Door Lock * Node 13 detected as Kwikset 914/Door Lock * Node 15 detected as GED1800/SmartCode 10 Touchpad Electronic Deadbolt PPS: I do have the capability to capture Zniffer logs if needed & requested. ### Device information Manufacturer: Kwikset Model name: 914 Node ID in your network: 12, 13, 15 ### How are you using `node-zwave-js`? - [ ] `zwavejs2mqtt` Docker image (latest) - [ ] `zwavejs2mqtt` Docker image (dev) - [ ] `zwavejs2mqtt` Docker manually built _(please specify branches)_ - [ ] `ioBroker.zwave2` adapter _(please specify version)_ - [ ] `HomeAssistant zwave_js` integration _(please specify version)_ - [ ] `pkg` - [ ] `node-red-contrib-zwave-js` _(please specify version, double click node to find out)_ - [ ] Manually built from GitHub _(please specify branch)_ - [X] Other _(please describe)_ ### Which branches or versions? version: node-zwave-js 9.0.2, zwavejs2mqtt 6.7.1 ### Did you change anything? yes (please describe) ### If yes, what did you change? For the past few months I considered this setup to be a sandbox as I got to know HomeAssistant and ZwaveJS a bit better, but I got comfortable enough with it that I migrated everything from another Zwave controller/platform in the past few weeks (growing me to the 131 nodes I have at the moment). I have anecdotally observed this problem has gotten more severe as I moved more and more Zwave devices over to this setup. ### Did this work before? Yes (please describe) ### If yes, where did it work? See previous comment about recent changes. ### Attach Driver Logfile [zwavejs_2022-04-18.log.gz](https://github.com/zwave-js/node-zwave-js/files/8513288/zwavejs_2022-04-18.log.gz) A great example of this behavior in action would be around 2022-04-19T03:16:09.817Z. Note that the ping sent to Node 013 at 2022-04-18T23:28:54.155Z is automated; when one of the three deadbolt nodes go "dead" I have my setup wait 15 seconds and then send it a ping to bring it back to life.

Rich37804 · February 21, 2024, 4:13pm

When I first got this lock, I was on a 700 series zwave stick and it would constantly drop off the network.
The lock was important enough to my wife that I got an 800 series stick and migrated everything over. The lock is much more stable with the only issue being the jamming of the lock kicking it off the network. Once its kicked off, I just pull the battery and reinsert and it connects back.
Removing/re-pairing has had no effect on it. Ive even tried pairing with no security.

homewirelessguy · April 29, 2024, 6:51pm

I have the same issue with the Kwikset SmartCode 916 lock. If it jams, the lock falls off the Zwave network. It does not report that its jammed, just unavailable in Home Assistant after it falls off the network. Anyone else see this? Any fixes for this? Thanks.

Rich37804 · April 29, 2024, 8:42pm

They now have a zigbee version at Home Depot. I picked it up and its way better.

homewirelessguy · May 3, 2024, 2:05am

I reset the battery in the Smartcode 916 and Im no longer seeing the drop from zwave on a Jammed condition.

Rich37804 · May 3, 2024, 3:40pm

I tried that several times. It always eventually came back.