CC Notification not being created on Conexis L1 for keypad unlock?

[xhemp]

Greetings!

Decided to post this in here before posting as a bug.
I have migrated from ZWave 1.4 on HA to Z-Wave JS and everything has been working great but I have been trying to find out how to get my Yale Conexis L1 to show the tag that was used to unlock the door.
I had installed first a snap version of zwave-js and I could see the alarm level and I could tie that to an user and it was working fine.
I decided to use the latest version ( I am using ZwaveJS 7.1.1. ) so I've been using npm and it looks like the notifications (alarm type) were being mapped (as per template_yale.json) which is working great (I could just get that value and show directly) but looks like alarm level isn't and there was a bug logged ( #2206 ). Bug was closed but even though I could see the alarm level and type coming in as per the zwave-js log:

0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.753 INFO ZWAVE: Node 17: value updated: 98-0-currentMode 255 => 0
0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.756 INFO ZWAVE: Node 17: value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => true,false,false,false
0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.758 INFO ZWAVE: Node 17: value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.761 INFO ZWAVE: Node 17: value updated: 98-0-latchStatus open => open
0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.763 INFO ZWAVE: Node 17: value updated: 98-0-boltStatus locked => unlocked
0|ZwaveJS2MQTT  | 2021-04-07 23:15:08.766 INFO ZWAVE: Node 17: value updated: 98-0-doorStatus closed => open
0|ZwaveJS2MQTT  | 2021-04-07 23:15:09.677 INFO ZWAVE: Node 17: value updated: 113-0-alarmType 144 => 144
0|ZwaveJS2MQTT  | 2021-04-07 23:15:09.679 INFO ZWAVE: Node 17: value updated: 113-0-alarmLevel 5 => 2

I can't see any notifications out of it like I see for manual lock/unlock, for example:

0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.291 INFO ZWAVE: Node 17: value updated: 98-0-currentMode 255 => 255
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.295 INFO ZWAVE: Node 17: value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => false,false,false,false
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.298 INFO ZWAVE: Node 17: value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.300 INFO ZWAVE: Node 17: value updated: 98-0-latchStatus open => open
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.303 INFO ZWAVE: Node 17: value updated: 98-0-boltStatus locked => locked
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.305 INFO ZWAVE: Node 17: value updated: 98-0-doorStatus closed => closed
0|ZwaveJS2MQTT  | 2021-04-07 23:09:41.316 INFO ZWAVE: Node 17: value updated: 98-0-lockTimeout 0 => 0
0|ZwaveJS2MQTT  | 2021-04-07T22:09:42.202Z CNTRLR   [Node 017] compat mapping found, treating V1 Alarm frame as Notification Repor
0|ZwaveJS2MQTT  |                                   t
0|ZwaveJS2MQTT  | 2021-04-07 23:09:42.209 INFO ZWAVE: Node 17: value updated: 98-0-currentMode 255 => 255
0|ZwaveJS2MQTT  | 2021-04-07 23:09:42.221 INFO ZWAVE: Node 17 CC Notification {
0|ZwaveJS2MQTT  |   type: 6,
0|ZwaveJS2MQTT  |   event: 1,
0|ZwaveJS2MQTT  |   label: 'Access Control',
0|ZwaveJS2MQTT  |   eventLabel: 'Manual lock operation',
0|ZwaveJS2MQTT  |   parameters: undefined
0|ZwaveJS2MQTT  | }

Edit: I just found a more verbose logging from earlier showing a notification for keypad unlock:

2021-04-07T21:13:23.375Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Access Control
                                      notification status: 255
                                      notification event:  Keypad unlock operation
                                      event parameters:    [object Object]
2021-04-07T21:13:23.462Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Access Control
                                      notification status: 255
                                      notification event:  Keypad unlock operation
                                      event parameters:    [object Object]

Is there anything I am missing here or there is an issue?

[AlCalzone]

I think #2248 solves this but it was merged after the 7.1.1 release.
If you can get into the container, you can manually pull the update as a workaround. Navigate into node_modules/zwave-js (I don't know the leading part of the path) and run

npm i @zwave-js/[email protected] --save-exact

there.

[xhemp]

Thanks, AlCalzone, I have tried that but had the same result.

0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.207 INFO ZWAVE: Node 17: value updated: 98-0-currentMode 255 => 0
0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.210 INFO ZWAVE: Node 17: value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => true,false,false,false
0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.212 INFO ZWAVE: Node 17: value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.215 INFO ZWAVE: Node 17: value updated: 98-0-latchStatus open => open
0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.218 INFO ZWAVE: Node 17: value updated: 98-0-boltStatus locked => unlocked
0|ZwaveJS2MQTT  | 2021-04-08 11:01:06.220 INFO ZWAVE: Node 17: value updated: 98-0-doorStatus closed => open
0|ZwaveJS2MQTT  | 2021-04-08 11:01:07.140 INFO ZWAVE: Node 17: value updated: 113-0-alarmType 144 => 144
0|ZwaveJS2MQTT  | 2021-04-08 11:01:07.143 INFO ZWAVE: Node 17: value updated: 113-0-alarmLevel 2 => 6

Got some logs on silly level (attached).
silly.txt

Edit: Just to add, the keypad unlock was at 10:09:21 and 10:09:22

[AlCalzone]

0|ZwaveJS2MQTT  | 2021-04-08 11:01:07.140 INFO ZWAVE: Node 17: value updated: 113-0-alarmType 144 => 144
0|ZwaveJS2MQTT  | 2021-04-08 11:01:07.143 INFO ZWAVE: Node 17: value updated: 113-0-alarmLevel 2 => 6

We currently don't map the RFID unlock report because there is no standardized notification event for RFID reader unlock/lock. Does the lock have an RFID reader and a keypad or just the reader? If it is the latter, we could add a mapping.

In any case, you can watch these two values I quoted. alarmType 144 indicates RFID, alarmLevel is the user ID.

[xhemp]

The lock just has an RFID header, no keypad on this one.
I used to watch those values and even if I enabled them, they were never getting updated but looks like now they are, great!
If there's any further debug you need me to do, let me know but I am happy to use those values too. Thanks for taking a look.

[AlCalzone]

Forgot to mention - we're tracking this in #2275

[xhemp]

cheers!