So I'm attempting to pair a Schlage BE468 with little luck. I have a total of 4 of these and two have paired just fine while two others refuse to pair. Here is a list of things I've done to troubleshoot as well as a screenshot from my logs.
Any suggestions?
You've done a lot of good troubleshooting. Keeping the hub close is usually necessary for these (though I've heard of some people having luck without doing that; I didn't), so I'd keep doing that part.
The one thing I'd add: have you tried an exclusion? If it's new, it shouldn't be paired already, but it can't hurt to try. There are instructions in the manual for this that are similar to the ones for pairing/including. You can use the "Start Z-Wave Exclusion" button on the device discovery page to do this, and if it finds something, it will say something like "Unknown Z-Wave device excluded." I'd try it a couple times to be extra-sure if it doesn't find anything the first time.
If Hubitat finds something to exclude, you'll probably be able to pair it fairly easily just by trying again. If it doesn't, I'd try to pair it a few more times. It took me probably 10 tries to get my BE468 to pair the first time I tried (but I think that was before Hubitat's Z-Wave improvements, so things should be better now--and it was for me when I recently moved my Z-Wave network to a new stick manually).
Tried that as well. 
Just updated my original troubleshooting list.
So what I did was do a z-wave exclusion.
reset the lock (since the z-wave chip is separate from it. but still linked in a odd way)
Do another z-wave exclusion.
Rinse repeat until you got a successful exclusion. Then try inclusion.
Also make sure there is no z-wave chatter while you are doing this. The Z-wave radio of Hubitat can hang with too much chatter during secure communications.
Also what firmware is it running? Mine are running 6.8 for that process
You’ve done all the right things. These things are super frustrating to get to pair and I know that the Hubitat staff continues to work on making them pair/work more smoothly.
One other thing to try (though you will lose all of your current codes) is to factory reset the lock. This doesn’t clear the z-wave connection to the hub, so you’ll still need to exclude as you’ve been doing just to be safe.
On my 469 the reset procedure if I recall is to unplug the batteries, then hold down the front Schlage button and reconnect the batteries. If it flashes red that means it is still paired to something and then an exclusion is needed to make sure it is fully unpaired. Again, you’ve already tried most, if not all, of these suggestions. Only trying to help.
You also mention that you are within 2 feet of the lock. I had to literally dangle my hub on the lock with the CAT5 cable. I had an old Airport Express that I used to ‘extend’ my network and plugged my Hubitat into that which gave me the freedom to my the Hub to my lock when pairing. Even then on a few of my locks I still had to exclude and repair 5-10 times to get it to finally connect.
CC @waynespringer79 and @aaiyar as they may have other suggestions. All of us have these locks as well.
Thanks for the encouragement! After completing the exclusion and inclusion process 16 times (yes, 16...I counted) it successfully paired. No freakin' clue as to why it finally decided to work. The kicker... I went to move over my last lock and it paired on the first go...
Glad it helped!
Ever since I completely rebuilt my zwave network from scratch and added the 4 Aeotec Range Extender 6's first followed by all hardwired repeating devices before any battery devices.....I haven't had a single bit of trouble with these anymore, in fact both (trouble) locks I was able to pair in place one about 25 feet from the hub, and the other over 50 feet from the hub outside on a metal building. (NOTE: I did still have to EXCLUDE them right near the hub). Since then I haven't had a single issue and reliable locks app hasn't missed a single poll in almost a month.
Check your device page and make sure in completed the configuration, which means it "fetches" all 30 possible codes from the lock.
It should look like this if it did.
Same here. And battery life is way better. To be honest, I'm still using Reliable Locks because I'm superstitious, not because it's still necessary.
Edit - damn, just saw a black cat
Sounds like the repair Z-Wave is not working as advertised. Because that's what it's suppose to do.
The zwave repair works fine, the zwave radio in these hubs however are significantly weaker signal, but really only noticeable with secure devices compared to other platforms. The Aeotec Range Extender 6's Amplifiy that weak signal up to the strength that other platforms already have.
So based on that I would assume it would recognize a better repeater and use it. But you had to force it to use that device before all others. Hence my comment. Or am I missing something?
It wasn't so much as forcing it, as one (the first device paired on my fresh network rebuild) of my 4 repeaters is literally within 2 feet from the hub. I'm assuming all other devices after that will join from whichever device produces the strongest signal, which will be the range extender. and the first 4 devices paired are the range extenders, so the mesh I assume would build through them, but I still did a zwave repair each time after adding about 5 devices.
It did work pretty good before I did the fresh rebuild by adding them after all the devices and doing zwave repairs after adding each extender, I only had a rare occurrence there was an issue. And I believe @aaiyar has done just that as well (no fresh rebuild) and he doesn't seem to have any issues either.
The zwave network rebuild wasn't because of this issue, it was unrelated nor by my choice.
Download the Hubitat app
