Kwikset zigbee lock won’t work (March 2023)

Hmmm…couple of things don’t make sense here.

The default Zigbee lock handler in the lua libraries is responsible for generating the event. For the codeName, it first assigns a default value “code (codeId used to unlock the lock)” and then tries to do a lookup in the lockCodes array. If it finds a non-empty value for the codeId in the array, it assigns the name it found in the array. Otherwise, you get the default value

    if (source == 0) then
      local code_id = zb_rx.body.zcl_body.user_id.value
      local code_name = "Code "..code_id
      local lock_codes = device:get_field("lockCodes")
      if (lock_codes ~= nil and
          lock_codes[code_id] ~= nil) then
        code_name = lock_codes[code_id]
      end
      event.data = {method = METHOD[0], codeId = code_id .. "", codeName = code_name}

This would imply that the default handler finds a completely empty array or an empty value in the array for the codeId that unlocked the lock. Since we know that the lockCodes array is populated, there is some disconnect between the driver and the default handler. @Mariano_Colmenarejo might be able to do some digging to figure out what is happening here.

The more confusing thing for me is that the codeId is in the event data so, in theory, SLGA should be able to find the associated name that it has already pulled out of the lockCodes capability from the driver. This is going to take getting ST support involved since they are responsible for the SLGA. I looked back in the history of this topic, but didn’t see it, so refresh my memory that you do see the names when you go to the Lock Codes drop down in SLGA. Also, do you see a “Last unlocked (date)” under their names?

If the codeName in the unlock event were populated properly, you could use Sharptools to generate a notification that included it. Since the codeName is not being properly set, a notification that says “Code 1 unlocked the door” is pretty useless.

yes i see the lockcode name but it shows updated…no last unlock. is there any way to look at the ST driver and slga program? Or is there a way to get the ST driver and add my fingerprint into it to see if that will work?

No last unlock time/date also seems symptomatic of SLGA not recognizing which code is unlocking the lock.

My cursory comparison between the stock ST driver and the one from @Mariano_Colmenarejo is that there is no difference in the actual operation of the driver. Like other authors who add additional fingerprints to the driver, they have simply taken the stock driver and updated the yaml file. That being said, if you have the skills to create your own drivers, the stock Zigbee lock driver is here. The SLGA code is not published.

My feeling about the codeName wrong in the event data is that there is probably a bug in the lua libraries in accessing the lockCodes capability maintained by the driver. What’s going on with SLGA is beyond me.

I have the Zigbee 914 same lock he has but his is a slightly different fingerprint. I’m using the same driver and it is working fine. Maybe an issue with the lock itself? I know ST told me that if your fingerprint is not in the stock driver then Kwikset didn’t report it to them as a radio that came in those locks.

@chris21 is that the original radio card that came in that lock or?

1 Like

Yes. My old lock had an issue and they sent me that as a replacement. Brand new. Could I have pulled the wrong fingerprint or could it have be gotten wrong

You have the right fingerprint as that is what it shows in the API. What I meant was did you change the Zigbee radio card from what was originally in the lock. If I have the same lock but a different Zigbee radio and I’m using the same driver and it works fine. Then I’m wondering if there is an issue with the lock or the Zigbee radio that you have. Kwikset made those locks for a few different platforms like Deconz, Control4 etc. Where did you buy that lock? That fingerprint looks like an Amazon model maybe the Key Edition. I’m not an expert on this but I have read that some of those editions are proprietary.

Sharptools could still be used with variables

Yeah, it’s doable but a pain since you have to update your rules in Sharptools every time you add/delete/change a code. Plus, there is no way for Sharptools to send a native phone notification to the phone. Have to do SMS or Pushbullet or the like.

They sent me a whole new lock.

The thing that makes no sense is that the device is emitting the necessary data to generate lock/unlock events. The codeId is present, the lockCodes array is populated in the driver, SLGA has the proper codeNames. There is no obvious reason that the default handler doesn’t properly populate the event data with the correct codeName nor for SLGA not making the association.

Do you have a copy of what the logs look like for your lock? Can you post them?

I will generate the logs today and post them.

2023-03-23T11:54:54.457809813+00:00 DEBUG Zigbee Lock Mc  driver device thread event handled
2023-03-23T11:55:24.458461707+00:00 DEBUG Zigbee Lock Mc  driver device thread event handled
2023-03-23T11:55:36.278357046+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:36.279539712+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x23, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: MANUAL, OperationEventCode: NON_ACCESS_USER_OPERATIONAL_EVENT, user_id: 0xFFFF, pin: "", local_time: 0x2BAEC27D, data: "" > > >
2023-03-23T11:55:36.358468046+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:36.366841379+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:55:36.368179379+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"unlocked"}}
2023-03-23T11:55:36.408654379+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:36.409641379+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:36.410915712+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x24, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[UNLOCKED] > > > >
2023-03-23T11:55:36.471468046+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:36.472328712+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:55:36.474028379+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"unlocked"}}
2023-03-23T11:55:36.492210379+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:45.019722717+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:45.032628383+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD0, rssi: -75, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x25, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: MANUAL, OperationEventCode: ONE_TOUCH_LOCK, user_id: 0xFFFF, pin: "", local_time: 0x2BAEC283, data: "" > > >
2023-03-23T11:55:45.191932717+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:45.192939383+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:55:45.194711050+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"locked"}}
2023-03-23T11:55:45.227832717+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:45.229108717+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:45.230295050+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD4, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x26, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[LOCKED] > > > >
2023-03-23T11:55:45.334580050+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:45.336003050+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:55:45.380947383+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2023-03-23T11:55:45.382305050+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:51.838366720+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:51.839548386+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -75, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x27, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: KEYPAD, OperationEventCode: UNLOCK, user_id: 0x0001, pin: "", local_time: 0x2BAEC28C, data: "" > > >
2023-03-23T11:55:51.929614720+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:51.930456720+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:55:51.938657053+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"codeId":"1","codeName":"Code 1","method":"keypad"},"value":"unlocked"}}
2023-03-23T11:55:51.940453720+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:52.298365720+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:52.299329053+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x28, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[UNLOCKED] > > > >
2023-03-23T11:55:52.323434053+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:52.331492720+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:55:52.333189387+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"unlocked"}}
2023-03-23T11:55:52.336393387+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:54.426521721+00:00 DEBUG Zigbee Lock Mc  driver device thread event handled
2023-03-23T11:55:54.675570054+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:54.676832388+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD0, rssi: -75, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x29, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: MANUAL, OperationEventCode: ONE_TOUCH_LOCK, user_id: 0xFFFF, pin: "", local_time: 0x2BAEC28E, data: "" > > >
2023-03-23T11:55:54.769318055+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:54.770151388+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:55:54.771852721+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"locked"}}
2023-03-23T11:55:54.773734721+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:55:55.178400388+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:55:55.179373388+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xCC, rssi: -75, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[LOCKED] > > > >
2023-03-23T11:55:55.198997388+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:55:55.206833055+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:55:55.208556055+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2023-03-23T11:55:55.211927721+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:03.967939392+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:03.968908726+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xCE, rssi: -77, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x2B, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: KEYPAD, OperationEventCode: UNLOCK, user_id: 0x0002, pin: "", local_time: 0x2BAEC295, data: "" > > >
2023-03-23T11:56:04.329433392+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:04.330410392+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:56:04.338284392+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"codeId":"2","codeName":"Code 2","method":"keypad"},"value":"unlocked"}}
2023-03-23T11:56:04.470169726+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:04.471432392+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:04.472623059+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[UNLOCKED] > > > >
2023-03-23T11:56:04.795243059+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:04.796647059+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:56:04.802442726+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"unlocked"}}
2023-03-23T11:56:04.845202059+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:06.345745727+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:06.346719727+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xC8, rssi: -76, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x2D, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: MANUAL, OperationEventCode: ONE_TOUCH_LOCK, user_id: 0xFFFF, pin: "", local_time: 0x2BAEC299, data: "" > > >
2023-03-23T11:56:06.429379727+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:06.430223060+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:56:06.432277393+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"locked"}}
2023-03-23T11:56:06.434204060+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:06.531898727+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:06.532874060+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -78, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[LOCKED] > > > >
2023-03-23T11:56:06.549759060+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:06.557757060+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:56:06.559482727+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2023-03-23T11:56:06.562740727+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:13.403871063+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:13.407906063+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x2F, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: KEYPAD, OperationEventCode: UNLOCK, user_id: 0x0003, pin: "", local_time: 0x2BAEC2A1, data: "" > > >
2023-03-23T11:56:13.580741397+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:13.581585730+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:56:13.588473063+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"codeId":"3","codeName":"Code 3","method":"keypad"},"value":"unlocked"}}
2023-03-23T11:56:13.598408063+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:13.845777730+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:13.859203064+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x30, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[UNLOCKED] > > > >
2023-03-23T11:56:13.864736397+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:13.865928397+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:56:13.878331064+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"unlocked"}}
2023-03-23T11:56:13.904380730+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:20.072778400+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:20.074207067+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xD2, rssi: -76, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x31, ZCLCommandId: 0x20 >, < OperatingEventNotification || DrlkOperationEventSource: MANUAL, OperationEventCode: MANUAL_LOCK, user_id: 0xFFFF, pin: "", local_time: 0x2BAEC2A8, data: "" > > >
2023-03-23T11:56:20.127515067+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:20.207103067+00:00 INFO Zigbee Lock Mc  Executing ZclClusterCommandHandler: cluster: DoorLock, command: 0x20
2023-03-23T11:56:20.216975733+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"locked"}}
2023-03-23T11:56:20.251204067+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:20.255748400+00:00 TRACE Zigbee Lock Mc  Received event with handler zigbee
2023-03-23T11:56:20.260475733+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x528C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DoorLock >, lqi: 0xCC, rssi: -76, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x32, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Enum8, LockState: LockState[LOCKED] > > > >
2023-03-23T11:56:20.388117400+00:00 TRACE Zigbee Lock Mc  Found ZigbeeMessageDispatcher handler in zigbee-lock
2023-03-23T11:56:20.390385733+00:00 INFO Zigbee Lock Mc  Executing ZclClusterAttributeValueHandler: cluster: DoorLock, attribute: LockState
2023-03-23T11:56:20.392141067+00:00 INFO Zigbee Lock Mc  <ZigbeeDevice: f3bad400-bd5a-4148-a85c-4fa6b8027534 [0x528C] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2023-03-23T11:56:20.474629067+00:00 DEBUG Zigbee Lock Mc  Front Door Lock device thread event handled
2023-03-23T11:56:24.538158402+00:00 DEBUG Zigbee Lock Mc  driver device thread event handled
listening for logs... done

@h0ckeysk8er
@chris21 My unlock events look just like yours. Seems something going on with SLGA.

going over your debug it look pretty much the same. codeid, codename, and user_id are all in the same format and the output seems the same. The only difference I can think of is that I installed the new driver when he added my fingerprint. I wonder if anything else was changed.

I diff’d the main part of both the stock driver and Mariano’s and they are identical. And when drivers are updated, they are pushed to all subscribed users so both you and Michael are likely running the same version of the driver at this point.

I see in Michael’s logging that the codeName is not set to a value from lockCodes which is actually a good sign that the behavior at the driver and default lock handler is behaving the same for both of you. And comparing both the incoming Zigbee message and the lock handler generated event, they are identical except for things like the device ID and lock code used to unlock. This confirms for me there is likely some problem in the default lock handler (or other part of the library) that results is “Code x” being in the event.

I’m at a loss as to why SLGA is generating notifications and history with names in them for Michael but not Chris.

@mlchelp You can confirm that your SLGA history shows who unlocked the lock and there is a “Last unlocked” date/time under each user in the SLGA lock codes?

Yes I can see who unlocked the door in history and I also get a notification from SLGA. I was never able to see last unlocked. Even with Groovy and a DTH I didnt see it. This is the history from when I created the log I posted this morning.

I was also thinking that Im using a Galaxy S22. Maybe something with the app on Chris’s Phone?

@chris21 what phone are you using?

Last unlocked should be under the name associated with the lock in SLGA like this.

Hmmm…now that’s an angle I haven’t thought about. @chris21 Any chance you have an Android phone to try it out on (even temporarily on a friend’s phone) if you aren’t on Android already?