So I noticed this a while ago and decided to run a little test. It seems that secure encapping commands is not actually needed anymore?
Here is before || after running a cmd through the zwaveSecureEncap function. The second one is the supervision reply which does not have anything happen to it (does not need to be secured).
secureCmd Command: 2501FF || 9F03022501FF
secureCmd Command: 6C023AFF00 || 6C023AFF00
I am only using the zwaveSecureEncap in this log message to see what it was doing exactly, I removed it from the code where it actually sends the commands.
The hub still sends out secured commands and the devices works fine, as shown with zniffer logs:
