Kwikset 914 Zigbee Lock Connecting but no control

[Matts]

Hello, I have recently switched from Smartthings to Hubitat and have tried bringing over my Kwikset 914. The device pairs with no issues and then even reports the device status for Locked/Unlocked almost immediately. However, when I try to lock/unlock the door from Hubitat the device only responds 25% of the time. I have also moved the lock directly next to the hub and it still does not work. The lock status will change in Hubitat but the actual device won't unlock. Has anyone else had this problem?

I have attached the logs and you can see the Lock() comand sent and then the device saying it is unlocked but it does not physically unlock.

I get this when I press configure:

[dev:31]2022-11-02 12:59:11.581 PM[warn]CommandResponse skipped clusterId:8021, descMap:[raw:catchall: 0000 8021 00 00 0040 00 E566 00 00 0000 00 00 9500, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E566, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[95, 00]]

[dev:31]2022-11-02 12:59:11.578 PM[debug]parseCommandResponse: [raw:catchall: 0000 8021 00 00 0040 00 E566 00 00 0000 00 00 9500, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E566, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[95, 00]]

[dev:31]2022-11-02 12:59:11.542 PM[warn]CommandResponse skipped clusterId:8021, descMap:[raw:catchall: 0000 8021 00 00 0040 00 E566 00 00 0000 00 00 9400, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E566, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[94, 00]]

[dev:31]2022-11-02 12:59:11.539 PM[debug]parseCommandResponse: [raw:catchall: 0000 8021 00 00 0040 00 E566 00 00 0000 00 00 9400, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E566, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[94, 00]]

[dev:31]2022-11-02 12:59:11.505 PM[warn]CommandResponse skipped clusterId:8021, descMap:[raw:catchall: 0000 8021 00 00 0040 00 E566 00 00 0000 00 00 9300, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E566, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[93, 00]]

This is me Unlocking and Locking the door from Hubitat and nothing happens:

[dev:31]2022-11-02 12:57:08.902 PM[info]Front Door was locked

[dev:31]2022-11-02 12:57:08.899 PM[debug]parseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 E566 01 00 0000 00 01 00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:E566, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[00]]

[dev:31]2022-11-02 12:57:05.410 PM[debug]lock()

[dev:31]2022-11-02 12:56:33.666 PM[debug]parseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 E566 01 00 0000 01 01 00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:E566, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00]]

[dev:31]2022-11-02 12:56:28.950 PM[debug]unlock()

[dev:31]2022-11-02 12:54:48.200 PM[info]Front Door was unlocked

[dev:31]2022-11-02 12:54:48.197 PM[debug]parseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 E566 01 00 0000 01 01 00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:E566, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00]]

[dev:31]2022-11-02 12:54:43.858 PM[debug]unlock()

[Ken_Fraleigh]

I have 3 of these in use for about 3 years now and they have been great. My guess is that other Zigbee devices are causing a problem, or the batteries need to be replaced. It doesn’t matter how close to the hub it is, it’s going to route through what it thinks looks best. I never have seen mine show up as a child device in the route table.

[Matts]

I have very few Zigbee devices only 2 other battery powered motion sensors. Also the lock is at 80% charge

[anon47916022]

Welcome to the forum!

First and foremost, can you go join the owners group? This will allow you to post screenshots here.

Can you go to http://your-hub-ip-address/hub/zigbee/getChildAndRouteInfo and post a screenshot? Be sure to replace the "your-hub-ip-address" part with the IP of your hub.

[Matts]

Ahh I was wondering how to post screenshots, thanks!

There isn't much on the Zigbee side of my network. It is mostly Z-Wave

[TomG]

@Matts

There isn't much on the Zigbee side of my network.

I believe that is the problem. You need a Zigbee repeater. I have the same exact lock, and also switched from ST after owning the lock for a few months. My HE hub is no more than 5 feet from the lock, and it gave me fits until I added a repeater.

YMMV

[Matts]

I will try that and report back

[TomG]

Tuya Zigbee repeaters work well for me. They are USB and tiny.

I bought mine from AliExpress but they come from China so expect 3-4 weeks.

[US $12.74 53％ Off | Tuya Smart Life ZigBee 3.0 Signal Repeater USB Extender App Devices Mesh Home Assistant Deconz Automation https://a.aliexpress.com/_mrsHhZi

eBay has them

https://www.ebay.com/itm/195341558234?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=R5mPORIBRU-&sssrc=2349624&ssuid=m7sFJo7OQke&var=&widget_ver=artemis&media=COPY

[Matts]

So I got the repeaters and it helped a little but it is still having issues. I tried using the Generic Zigbee Lock Driver with no Keypad and the lock responds instantly to all commands but then the lock status is not being reported. When I use the Generic Zigbee Lock Driver with Keypad it pulls in only one code for all 16 I believe this is an issue with the Hubitat generic driver and the new Kwikset 914 Smartcode ZB 3.0 as different parts work with different drivers. I am hoping someone from Hubitat support will be able to help me with this issue.

@bobbyD I saw you were able to help another user with the newer 914 ZB 3.0 lock. Do you have any recommendations?

Need some advice on how to pair a kwikset 914 zigbee deadbolt

If you were going to go with the Z-Wave version I would strongly suggest going with the home connect 620. The latest version is Z-Wave 700, and the motor is much quieter than the old 9xx model. I got mine at gokeyless.com (I am in no way affiliated with them, that's just where I found them in stock first). Or if you want some used nickel colored 914s I probably have some sitting in a box somewhere that I haven't got around to selling yet. I have z-wave, Z-Wave plus, and original zigbee com card…

[Matts]

I have debugged while using the Generic Zigbee Lock Driver with Keypad I am sending the Lock() command and the lock is sending back that it was locked but it never physically gets locked.

[Ken_Fraleigh]

Did you follow the directions prior to inserting the battery pack? I know I had to do the setup a little different with this compared to the older 914 Zigbee locks. I didn’t initially follow the setup instructions btw and my lock said it was locked when it was unlocked and vice versa. I broke down and followed the instructions and the not only was the reporting fixed, but the locking/unlocking became much faster. It sounds like the older ones on steroids.

[Matts]

I have tried excluding and re-pairing multiple times and have always followed the instructions Kwikset provided. However I haven't seen any differences from the original ZB 1.2 and the new ZB 3.0

[Ken_Fraleigh]

does it not lock or unlock with the driver, only the Zigbee lock (no keypad)?

[Matts]

With the Keypad driver I have to repeatedly press the lock/unlock for it to work.

With the no keypad driver it locks/unlocks reliably but does not report back the lock status

[Ken_Fraleigh]

It sounds like maybe it’s not getting configured properly. Maybe try moving it to a different location long enough to hit “configure” on the device page, then move it back. I did have to hit configure again on mine due to it initially not behaving, but it’s been fine since.
Btw, mine is showing up as a child device of the hub even though I have a crap ton of repeaters nearby, so maybe bring it close to the hub and hit configure.

[Matts]

I just tried bringing it right next to the hub as well as near other repeaters and it does not seem to effect performance.

It kinda seems like it is going to sleep with the keypad driver. It works good if you are constantly using it but if it sits for 10+ minutes it requires multiple lock/unlock commands for it to work and then it will respond instantly.

Just to confirm you are using the newer model with Zigbee 3.0? I have read on other threads that this model isn’t officially supported but it seems some people are able to get it to work.

[Ken_Fraleigh]

@Matts

model with Zigbee 3.0

Yes. Like I said, it took a couple tries to get it working right, and it ended up pairing directly with the hub (about 10 feet away line of sight), so that makes me think it’s a little bit fussy about what it will connect with. Maybe try new batteries just in case. Another thought; did you hold down the black button in the middle while you were putting the battery pack in? That’s the part of the directions that I skipped initially, and what fixed it when it wasn’t working properly at first.

[Matts]

I will put new batteries in and retry. I wonder what instructions you have been using. I have been following the ones on the kwikset website.

[Ken_Fraleigh]

@Matts

I wonder what instructions you have been using

The ones that were in the box it came in.

[TomG]

I have the 914 Zigbee model and use the Generic Zigbee Lock driver.