node-zwave-js: S2 message decryption errors when setting config params on multiple devices

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

• 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.

Describe the bug

What causes the bug?

Changing a configuration parameter in two S2 secured devices in short succession.

What do you observe?

Frequent messages in the logs about Duplicate commands and “Message authentication failed” for about a minute, slowing down the entire z-wave network.

What did you expect to happen?

Both devices should have the config parameter update and report back to the controller.

Steps to reproduce the behavior:

1. Add two devices with S2 Security (in my case both are Access Control)
2. Set a configuration parameter on one device, then immediately set a configuration parameter on the second.
3. Wait about 10 seconds
4. The logs will be flooded for about the next minute with error messages from both nodes.

Device information

Manufacturer: Allegion/Schlage Model name: BE469ZP Node ID in your network: 2 and 66

How are you using node-zwave-js?

• zwavejs2mqtt Docker image (latest)
• zwavejs2mqtt Docker image (dev)
• zwavejs2mqtt Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version: node-zwave-js branch: 8.5.0 zwavejs2mqtt branch: 5.8.0.36f1b6b

Did you change anything?

yes (please describe)

If yes, what did you change?

Upgraded both locks from S0 to S2 security

Did this work before?

Yes (please describe)

If yes, where did it work?

If both locks where at S0 security there were no issues.

Attach Driver Logfile

zwavejs_2021-10-12.log

Around 18:02:29Z you can see an example of the behavior I’m seeing. Around 18:05:05Z you can see the same exact call, but with a 10 second delay between setting the config param on node 2 and node 66.