Someone on Hubitat reported they literally had to duct tape the lock to the hub to get it to pair. These locks use a ‘whisper’ pairing to exchange the security keys.
Also, I’m assuming since this is an older lock it needs s0 inclusion. Zwavejs is trying to support newer s2 inclusion, but in the process, some s0 inclusion has been negatively impacted. See here https://github.com/zwave-js/zwavejs2mqtt/issues/1645 and here Device randomly loses security / network key and no longer able to add securely
Hopefully that issue isn’t impacting this but it could be. I’d make sure you are on the latest version of zwavejs which hopefully straightens it out, and try the steps detailed above by @NathanCu as well.