Missing command class parameter for zwave keypad iSurpass J1825

[yoguiti]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
After inclusion of device j1825 (keypad isurpass), the following command class parameter is not displayed :
Command Class : 113 (0x71)
Command Index : 153
Type : Byte (int)
Name : Memory Code User

Missing in the below picture :

This happens on ZwaveJS (I am using Jeedom). On other Zwave implementation (previous jeedom zwave plugin), this was correctly recognized (see picture attached)

Anything else we should know?
I do not know how to modify the j1825.json to correct this. Any help would be greatly appreciated. The device json is here :

Software versions

Z-Wave JS UI: 9.6.2

Device information

Manufacturer: Shenzhen iSurpass Technology Co., Ltd
Model name: J1825 Wall Reader
Node ID: 95
Firmware : 2.16

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

The log is here, with device ID 095
zwavejs_2024-04-26.log

I have actionned the device, and the log code which is relevant is below. I am looking to get the "UserId" parameter :

"2024-04-26T14:02:34.462Z CNTRLR [Node 095] [Notification] alarmType: metadata updated [Endpoint 0]
2024-04-26T14:02:34.463Z CNTRLR [Node 095] [+] [Notification] alarmType: 0 [Endpoint 0]
2024-04-26T14:02:34.463Z CNTRLR [Node 095] [Notification] alarmLevel: metadata updated [Endpoint 0]
2024-04-26T14:02:34.463Z CNTRLR [Node 095] [+] [Notification] alarmLevel: 0 [Endpoint 0]
2024-04-26T14:02:34.464Z DRIVER « [Node 095] [REQ] [ApplicationCommand]
└─[SecurityCCCommandEncapsulation]
│ sequenced: false
└─[NotificationCCReport]
notification type: Access Control
notification status: 255
notification event: Keypad unlock operation
event parameters:
userId: 0x01
2024-04-26T14:02:34.464Z CNTRLR [Node 095] [~] [Door Lock] currentMode: 255 => 0 [Endpoint 0]
2024-04-26T14:02:34.465Z CNTRLR [Node 095] [Notification]
type: Access Control
event: Keypad unlock operation
userId: 1

[zwave-js-bot]

👋 Hey @yoguiti!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[yoguiti]

driver log is irrelevant to the issue.

[AlCalzone]

I'm not sure what that value is supposed to be. If it's a notification, it's not a one from the Z-Wave specifications and apparently not one the device even reports to be supported.

So yes, the log is relevant and it should include some event that would modify this value.

[robertsLando]

I actually use this to parse notification parameters:

https://github.com/zwave-js/zwave-js-ui/blob/e51cf52bea1d1795f75fdf68abfbe9568131cfaf/api/lib/ZwaveClient.ts#L6413-L6420

I think that should return an object with the userId value like {userId: 0x01} ? If so that is the payload of the mqtt message sent to the node topic / notificationCC

[AlCalzone]

Ok then it might be up to Domotics to actually parse and expose that info.

[yoguiti]

Thanks a lot for your support.
However I am sorry I am unsure what needs to be done. Could you please clarify ? This userId value does not appear in zwave-js UI. Is there a modification to be made so it is the case ? Anything I can test ?

Thanks

[yoguiti]

@AlCalzone , when you say it might be up to domotics to parse and expose this info, you mean it is sent by ZwaveJS but the receiver end (Jeedom / Domotics) don't parse it correctly ? If that is what you are saying I am not sure this is the case because it does not appear either in zwaveJS UI. I would realla appreciate your help to move forward, and happy to test something. Otherwise I will have to do stupidely ugly like parsing the log of ZwaveJS in live to catch this event, which I definitely don't want to do ....

Thanks again !

[AlCalzone]

Z-Wave JS doesn't create values for event metadata that only has a meaning the instant it is received.
You should see the information in the events tab, which means Domotics/Jeedom should also see the information.