BE469ZP nonce expired on keypad operations

Checklist:

• I am not using HomeAssistant. Or: a developer has told me to come here.
• I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog problem was not mentioned there.

Describe the bug

When performing a keypad unlock on a BE469ZP the communication (and thus notifications) for actions appear to be dropped due to an expiring nonces.

Manual thumb turns reflect appropriately, it’s only lock / unlock operations from the keypad.

Device information

Which device(s) is/are affected (make/model)? Allegion Shclage BE469ZP What are the node IDs? 26

Did you change anything?

• Yes: (please describe)
• No

Did this use to work before?

• Don’t know, this is a new device
• No, it never worked anywhere
• Yes, in: (specify application with versions)

How are you using node-zwave-js

• zwavejs2mqtt (latest) docker image – App 2.1.1 | ZwaveJS 6.6.0 | Zwave-js-server 1.1.0
• zwavejs2mqtt (dev) docker image
• zwavejs2mqtt Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• ioBroker.zwave2 adapter
• HomeAssistant version XYZ
• Pkg
• Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• Manually built (as described in the docs)
• Other:

To Reproduce

Steps to reproduce the behavior:

1. Add a BE469ZP to your mesh
2. Unlock and lock manually with thumbturn and confirm status
3. Unlock with code from keypad
4. See error in logs | Status does not reflect

Additional context

Logfile:

zwavelogsnippet.txt

[hanerd]

Looking at my timestamps, 44 zwave plus devices took 8 minutes to heal.

On OZW, it was about 25.

Anyway, thanks again for looking into this one and seriously thank you for creating such an awesome project.

[AlCalzone]

This seems to be a persistent problem with those locks. They request a nonce (number used once) twice in quick succession, the second request invalidates the first nonce and then they use the first nonce twice, also in quick succession.

Unfortunately, this is nothing we can fix or work around without breaking compliance with the Z-Wave specs.

Unless you included the lock with zwave-js, you could try and reset, then re-include the device to see if that changes its behavior.