Yale YDF40 door locker with "Null" payload for fingerprint unlocking

[relombardo]

What happened?

Yale YDF40 door locker is sending "Null" payload for fingerprint unlocking as follows:

Zigbee2MQTT:info 2022-10-04 15:37:11: MQTT publish: topic 'zigbee2mqtt/Fechadura Entrada', payload '{"action":null,"action_source_name":null,"action_user":null,"battery":90,"linkquality":255,"lock_state":"unlocked","state":"UNLOCK"}'

I can map all other actions. For example, users unlocking with passcode, which sends a message payload.action_user with the respective user through the source payload.action_source = 0 as follows:

Zigbee2MQTT:info 2022-10-04 15:43:11: MQTT publish: topic 'zigbee2mqtt/Fechadura Entrada', payload '{"action":"unlock","action_source":0,"action_source_name":"keypad","action_user":65535,"battery":90,"linkquality":255,"lock_state":"locked","state":"LOCK"}'

Regarding the fingerprint unlocking, I have seen YMF40 users being able to capture that through the payload.action_source = 4. I believe I should be able to do the same with the YDF40 as their documentation seems to be the same in that aspect.

What did you expect to happen?

The Fingerprint unlocking action should present some specific payload message, different than Null, especially because it can have multiple users associated, such as Keypad unlocking action. YMF40 can do it, thus I expected YDF40 to be able to do the same.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.28.0-1

Adapter firmware version

0x26780700

Adapter

ConBee2

Debug log

No response

[everson7]

I'm having the same problem!

[danieledwardgeorgehitchcock]

Could you enable the Z2M debug logging and the Herdsman debug logging, and perform a fingerprint unlock on the device - there may be a lot of log chat in your console, but it may help track down the issue..

[relombardo]

@danieledwardgeorgehitchcock , I enabled debug logging, but I only see the exact same message through the log tab or file. Should I see more details through another interface? I did not manage to enable Herdman debug logging. I have no idea where to enter this: DEBUG=zigbee-herdsman* npm start nor where to find STDOUT/STDERR after it.

[relombardo]

Hi @Koenkk ! Would it be possible to use external converter of YMF40 in my YDF40? Or is there a way to fix the YDF40 itself?

[everson7]

Debug 2022-10-07 21:43:33Received Zigbee message from 'Yale', type 'commandCheckIn', cluster 'genPollCtrl', data '{}' from endpoint 1 with groupID null
Debug 2022-10-07 21:45:03Received Zigbee message from 'Yale', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":2}' from endpoint 1 with groupID null
Info 2022-10-07 21:45:03MQTT publish: topic 'zigbee2mqtt/Yale', payload '{"action_source_name":null,"action_user":null,"battery":82,"linkquality":61,"lock_state":"unlocked","state":"UNLOCK"}'
Debug 2022-10-07 21:45:03Received Zigbee message from 'Yale', type 'commandCheckIn', cluster 'genPollCtrl', data '{}' from endpoint 1 with groupID null
Debug 2022-10-07 21:45:11Received Zigbee message from 'Yale', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":2}' from endpoint 1 with groupID null
Info 2022-10-07 21:45:11MQTT publish: topic 'zigbee2mqtt/Yale', payload '{"action_source_name":null,"action_user":null,"battery":82,"linkquality":28,"lock_state":"unlocked","state":"UNLOCK"}'
Debug 2022-10-07 21:45:15Received Zigbee message from 'Yale', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID null
Info 2022-10-07 21:45:15MQTT publish: topic 'zigbee2mqtt/Yale', payload '{"action_source_name":null,"action_user":null,"battery":82,"linkquality":91,"lock_state":"locked","state":"LOCK"}'

[everson7]

As you can see mine is always null.
I can only see the quality of the link, battery and lock state

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[relombardo]

Any help? The issue was not resolved and it is affecting other users of Yale YDF40.

[relombardo]

Hi @Koenkk, could you help us with this issue?

[gregolin]

The same happening here.
The full log (I started with a new pairing etc) is attached.
As you can see in the log, it shows me correctly when I open the lock internally (line 90 for instance), but when I open it externally with fingerprint, I can't see the action, action_source_name or action_user (next-to-last, 94, for instance). The most strange is that everything works fine when I try to open it with password (lin
e 95).
Thanks.

log.txt

[gregolin]

@relombardo , any news about this issue from other source?

[relombardo]

@relombardo , any news about this issue from other source?

@gregolin , unfortunately I haven't found a solution. Hopefully we can get some guidance shortly. Another user on this thread, @everson7, also had same issue, which makes me think it is persistent outcome of this model so far. And you are right, using password is fine, the problem occurs with fingerprint.

[relombardo]

Hi @danieledwardgeorgehitchcock, I noticed @everson7 shared logs you asked and now @gregolin also shared his logs. Would you have any comment on it?

[gregolin]

@danieledwardgeorgehitchcock , I have one more log file (from other period of the day) with Herdsman log as well. Included here.
log_herdsman.txt

[Koenkk]

Let's continue in #15665