Kwikset 914 ZigBee lock

Does the Control 4 version work with Hubitat? I understand that they may be using a different Zigbee standard?

Took the motor/gear housing apart and didn’t see anything wrong. Simple gear train with no hall sensor or anything to report position. Lubed everything with lithium grease, put it all back together, reset it, did the handing process and now the WAF is good.

Still have the motor coming. I don’t anticipate this being a permanent fix.

2 Likes

I have 3 of these in hand now. Got them to join HE fine after a factory reset. Used the Generic driver/Config and I can see them; they Refresh but no Lock/Unlock.
Any other things you might have done for funtionality?

State Variables

  • codeFetchComplete : 0
  • requestedChange : {}

dev:18562022-06-29 12:50:02.114 infofingerprint profileId:"0104", endpointId:"02", inClusters:"0000,0001,0003,0009,0020,0101,0402,0B05,00BD", outClusters:"000A,0019", model:"SMARTCODE_DEADBOLT_10", manufacturer:"Kwikset"
dev:18562022-06-29 12:50:01.983 traceZCL version:01
dev:18562022-06-29 12:50:01.980 traceSoftware Build Id:unknown
dev:18562022-06-29 12:50:01.979 traceModel:SMARTCODE_DEADBOLT_10
dev:18562022-06-29 12:50:01.977 traceManufacturer:Kwikset
dev:18562022-06-29 12:50:01.725 debuggetting info for unknown Zigbee device...
dev:18562022-06-29 12:49:59.706 debugconfigure() called...

Did you click the Config button on the driver page for each?

Yup

Any thoughts on post 23. Sadly all went well but no commands work.

I am using the ‘Generic ZigBee Lock’ driver.

Compare my ‘Device Details’ to yours.

Reboot the hub? Sorry I can’t help more but my knowledge of all things HE is lacking.

Well they are different. I did get 3, crashing around in a bubble envelope without any protection! Grrr.
Maybe I'll try another one and see if the result is different.

image

Sadly tired another card and same thing with a less informative data.
Here is a picture of my cards just to confirm they are the same as yours.

image

Here is my ZigBee module. Numbers match yours.

I would only work with one at a time.

1 Like

How many mains powered devices (repeaters) are between the lock and the hub and how far away is the hub from the lock? I have two of the same cards and mine have been rock solid.

I am probably 3M from a powered Tuya repeater, 10M from the hub with the BIG antennae.
Lock joins right away every time and all looks fine just no events or actions.
If it was Z-Wave I would be suspecting distance as locks are crappy at joining from too far.
I guess I could try moving the hub closer with the ol' eth cable.

Well I moved the hub to the lock and it pairs fine but no events. Could it be the 3 I have are a different software load even though I used the OP's link? I don't get that field filled in. Worried I did get Control4 like the listing said even though it worked for the OP.

image

dev:19202022-07-03 12:40:06.386 infofingerprint profileId:"0104", endpointId:"02", inClusters:"0000,0001,0003,0009,0020,0101,0402,0B05,00BD", outClusters:"000A,0019", model:"SMARTCODE_DEADBOLT_10", manufacturer:"Kwikset"

dev:19202022-07-03 12:40:06.306 traceZCL version:01

dev:19202022-07-03 12:40:06.303 traceSoftware Build Id:unknown

dev:19202022-07-03 12:40:06.301 traceModel:SMARTCODE_DEADBOLT_10

dev:19202022-07-03 12:40:06.300 traceManufacturer:Kwikset

dev:19202022-07-03 12:40:05.890 debuggetting info for unknown Zigbee device...

dev:19202022-07-03 12:40:05.746 infoZigbee parsed:[raw:catchall: C25D 0001 C4 C4 0040 00 F717 00 00 0000 00 00 080009000A00, profileId:C25D, clusterId:0001, clusterInt:1, sourceEndpoint:C4, destinationEndpoint:C4, options:0040, messageType:00, dni:F717, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[08, 00, 09, 00, 0A, 00]]

dev:19202022-07-03 12:40:03.872 debugconfigure() called...

Several other clues that it’s Zigbee, but ZCL -> Zigbee Cluster Library

So ZCL is not HE implemented ZB but just plain bad for me? :frowning:

Download the Hubitat app