The issue with secure inclusion is that the key exchange must occur within 15 seconds of the device being added to the network. So you need to ensure the device is excluded and reset or this certainly won’t happen. Otherwise I guess we need to know what is going wrong - have you checked the logs?
The Schlage lock is likewise very finicky with inclusion. I tried repeatedly to securely include the lock but it was just not working. It finally worked after a lock reset, followed by moving the z-wave hub right next to the lock and trying several times more. I believe I used full power inclusion but I’m not 100% sure anymore.
One other hint about secure inclusion… As mentioned above - it is extremely time critical and everything needs to happen in approximately 15 seconds. If there is a lot of other activity going on, this can impact on the key exchange and cause the key exchange to fail. The binding does prioritize these commands, but there is always plenty of scope for things to get blocked if there’s a lot happening as ZWave only allows one transaction to be “in flight” at once.
For this reason, I would avoid including a secure device when the system is starting, or when some other heavy activity is taking place. Pick a quiet period and it will be more likely to succeed.
Documentation is always a good place to start when answering these questions
The exact location of the logs will depend on your system and how you’ve installed openHAB. Take a look at the install documentation as this should tell you where openHAB stores the logs given your installation.
The binding documentation tells you how to enable debug logging for Z-Wave.
I just managed to include this in OH 3.1. I had to try multiple times before it was successfully included, I had my rpi just next to the lock. I didn’t have to reset the lock in between attempts, I just excluded it and re included it again.
Not really - if you include a device, then reset it and include it again, you will have two devices. You must exclude the device to remove the first one. Unfortunately you can’t now do this and you need to try and force remove it.
What do you mean by “no matter how many times I try”? You must exclude and reset the device if it doesn’t securely include - so the node ID will increase each time.