keymaster_lock_state_changed event not being fired when unlocking via code

[scrambled2k3]

Describe the bug
keymaster_lock_state_changed event not being fired when unlocking Schlage lock via pin code. The event does fire correctly when I manually unlock via the knob, and also when I send a zwave request to unlock, just not when unlocking with a code.

Environment (please complete the following information):

• OS: HassOS
• VMWare ESXi Virtual Machine
• Home Assistant version: 2023.6.2
• Hassio
• Component version: Keymaster v. 0.0.85
• Z-Wave integration name: Z-Wave JS UI v. 1.14.0
• Lock make and model: Schlage BE469BP

Logs
Here is my ZWave JS UI event log when unlocking via a pin code:

2023-07-13T14:22:12.376Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: currentMode
└─endpoint: 0
└─newValue: 0
└─prevValue: 255
└─propertyName: currentMode
2023-07-13T14:22:12.379Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: outsideHandlesCanOpenDoor
└─endpoint: 0
└─newValue: false, false, false, false
└─prevValue: false, false, false, false
└─propertyName: outsideHandlesCanOpenDoor
2023-07-13T14:22:12.380Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: insideHandlesCanOpenDoor
└─endpoint: 0
└─newValue: false, false, false, false
└─prevValue: false, false, false, false
└─propertyName: insideHandlesCanOpenDoor
2023-07-13T14:22:12.381Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: doorStatus
└─endpoint: 0
└─newValue: open
└─prevValue: open
└─propertyName: doorStatus
2023-07-13T14:22:12.382Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: boltStatus
└─endpoint: 0
└─newValue: unlocked
└─prevValue: locked
└─propertyName: boltStatus
2023-07-13T14:22:12.383Z - VALUE UPDATED 
Arg 0:
└─commandClassName: Door Lock
└─commandClass: 98
└─property: latchStatus
└─endpoint: 0
└─newValue: open
└─prevValue: open
└─propertyName: latchStatus

[firstof9]

Your logs there mean nothing, you need to use the event listener in HA to see what's being broadcast by zwavejs.

Enter that press "Start Listening" then go do your pin codes.

[scrambled2k3]

Listening for that event did not result in anything either. I saw the event where I locked the door using the keypad, and manually locked the door back with the knob after coming inside, but not when I unlocked the door via a code.

event_type: zwave_js_notification
data:
  domain: zwave_js
  node_id: 8
  home_id: 3513830924
  device_id: 7310cdefda3d23440705a5f4e14912fb
  command_class: 113
  command_class_name: Notification
  label: Access Control
  type: 6
  event: 5
  event_label: Keypad lock operation
  parameters: {}
origin: LOCAL
time_fired: "2023-07-13T18:23:57.965745+00:00"
context:
  id: 01H587XPGDA2VFDGYCB2DTTVFW
  parent_id: null
  user_id: null

event_type: zwave_js_notification
data:
  domain: zwave_js
  node_id: 8
  home_id: 3513830924
  device_id: 7310cdefda3d23440705a5f4e14912fb
  command_class: 113
  command_class_name: Notification
  label: Access Control
  type: 6
  event: 1
  event_label: Manual lock operation
  parameters: {}
origin: LOCAL
time_fired: "2023-07-13T18:24:24.617171+00:00"
context:
  id: 01H587YGH9TACD8EQXEWW9A6JY
  parent_id: null
  user_id: null

[scrambled2k3]

Oddly enough, it does get triggered when I use the code stored in slot 2, but does NOT when using the code stored in slot 1

Edit: Disregard the above statement. I got it to trigger 1 time after multiple attempts. I have tried a few more times with the code in slot 2 and it is not working.

[firstof9]

The issue you are experiencing is either going to be with zwavejs or the hardware itself.

[pyrodex]

Oddly enough, it does get triggered when I use the code stored in slot 2, but does NOT when using the code stored in slot 1

Edit: Disregard the above statement. I got it to trigger 1 time after multiple attempts. I have tried a few more times with the code in slot 2 and it is not working.

I had a similar situation and Z-wave JS had to be cleared of the current codes. Once I did that I was able to set/use them again.

[dougmaitelli]

This issue just started happening to me 4 days ago now