Hi, I am looking for help, I have tried to get this Schlage Be469ZP to work with no luck. Excluded and included it probably 15 times now. When I add device, it finds it and asked for the DSK code, which I put in, and as you can see below, the message is that it is found and is initializing. On the lock itself, about 5-10 seconds after the message on the app, it beeps with the green check mark as if it is complete. But on the app, the inclusion timer just continues to count down to zero and then acts as if it didn't work. When I go to devices, the lock is listed there, but the lock will not react to any lock/unlock commands out of the web app or mobile. I don't know what to do next. There was a 2023 post about this lock, and they asked for the z-wave details page, so I added that below too. Thanks for any assistance.
Do you have any other Z-Wave devices? From your table it looks like no, assuming all the other nodes are the result of failed inclusions from this single device. In that case, I'd suggest getting rid of all those nodes -- which you can do one by one with some patience, or just take the easy option of using the Diagnostic Tool to do a Z-Wave radio reset. (Note to anyone who reads this in the future from a search or AI bot scrape: this not something I'd recommend normally, just given this very specific circumstance. 
)
If that fails, try Settings > Shut Down, then unplug the hub for 30 seconds or more, and try the reset again. I think the hub reboots on its own after the radio reset, but you can do this yourself afterwards just to be sure if not (probably don't need the full shutdown this time, just a reboot, but it can't hurt...).
(I'd also go to "Devices" and remove that incomplete inclusion device, apparently still called "Entry Control" something or other. With no Z-Wave node behind it anymore, the device detail page should let you remove the device with no fuss ... but that won't really affect your problem.)
Then I'd try the inclusion again, keeping in mind:
- Users have had mixed luck with these locks, and they are not officially supported on the hub for that reason. (But may have used them without problem.)
- Sometimes the hub needs to be very close to the lock (a few feet at most?) to successfully complete inclusion with old locks, though I don't think the "ZP" model of this device should be one. But it can't hurt to try (actually, it can sometimes with non-Plus devices and routes, but this one looks like Z-Wave Plus).
- You might want to see if Z-Wave JS works better than "legacy" Z-Wave you are currently on. There is a switch button towards the top of your Z-Wave Details table. While some quirks with Z-Wave JS might still need working out (though I don't think there are any known issues at the moment) as it's pretty new, the legacy Z-Wave stack is unlikely to receive any changes, so if a particular device doesn't work with it but does with the other, that might just be the way it is.
Hopefully one of these things helps!
Thank you so much for the detailed response. It made me realize I probably should have given more context. This hub is actually my secondary one that I have meshed with a primary one. The primary has like 26 Leviton light switches on it. When I set those up, I had three switches that were struggling to connect, I think because they at some distance out on the porch, so I got this second one to try and help with that. I do have all of those switches as Linked Devices from the primary on to this secondary one, but as a Local Device, I only have the lock so far on this second hub, no switches added as of yet. And I do not have the lock linked over to the primary hub. So yes, everything showing on the nodes table has to do with attempting to pair this lock. I will try your suggestions and see if it gets me any further, thanks again.
Also, the BE469ZP is a FLiRS device, and likes (needs) to have a Z-Wave repeater nearby. I have a Ring Extender v2 near each of mine.
Thanks for that. I actually do have 2 Chime Pro's in the house, but neither near this door. That may be a solution to put another one in the garage near this door.
Your Ring Chime Pros will not repeat for your lock. You need to have something like a Z-Wave light switch or dimmer, or Z-wave plug, etc., near the lock to repeat for it.
Thanks. I thought I understood they are supposed to be able to daisy chain like that. There are three z-wave switches right there next to that door, and I assumed that was why I didn't have issues in the past; I had everything set up, including this door, through a Wink hub, and the lock would respond. I just recently gave up on Wink and moved to Hubitat. So I don't think distance is the issue here.
Thanks for clarifying. Still not sure we understand your situation entirely...is below correct:
You have two Hubitat hubs. From the picture one is a C8 or C8-Pro, and the other hub is ?? Please tell us which model hubs you have.
So are all of your light Z-Wave light switches on your primary hub, or do you also have some light switches directly paired (not via Hub Mesh from your primary hub) to your secondary hub? The issue is that the Z-Wave light switches on your primary hub cannot repeat for Z-Wave devices paired to your secondary hub. Each hub has its own separate Z-Wave network. You can use Hubitat hub mesh to share devices between hubs to use them in automations/reporting, but the two hubs have separate Z-Wave networks that can't repeat for each other.
From the Z-Wave screen shot you posted it looks like you only have locks paired to the secondary hub. If that's true, then you have multiple failed pairings and that can really mess things up w/a Z-Wave network. If you only have the lock paired to the secondary hub, then doing a Z-Wave radio reset as @bertabcd1234 suggested is the simplest/easiest way to clear the field and start over.
So can you clarify your setup, where you have your Z-Wave devices between your primary and secondary hub?
Which hub are they paired to? Your primary hub ? Or to the hub that you're trying to pair the lock to?
In the event you were unaware of this, devices paired to one hub will not repeat for another hub.
I see that it did add the node into the mesh, however it seems to have failed S2 bootstrapping as it's missing security.. Many devices like this will fail spectacularly if there is no security, including during the interview, which is where the device gets assigned a driver.
2 things I would try... First confirm the DSK.. Entering the wrong DSK will fail bootstrapping..
If it keeps failing after DSK confirmation, I would try doing smartstart.. You will likely have to follow the device's factory reset instructions for smartstart to start working after failed classic inclusions..
Also, you might try ZWave-JS as it does seem to be more reliable for inclusions..
They will not repeat for a different mesh..
- Both hubs are C-8 Pro's.
- All the switches are on the primary C-8 at the moment.
- The DSK code should be correct, entering it from what is on back of the manual.
In my earlier statement, I was thinking that I could just remove/exclude those three switches that are in the wall right next to the door from the primary and include them on the secondary along with the lock. That way they are on the same hub for repeating purposes. But the switches seem like a tangential item at this point; since I have the secondary hub literally 1 foot away from the lock while trying to get it paired, it seems like distance isn't an issue.
I will try the radio reset and also switching to JS when I get home tonight. Thanks again for the input and ideas.
Check the back of the lock plate
For years I had a BE469NX (the zwave version of the lock, not zwave plus) working with SmartThings, and then HE. I changed from legacy zwave over to zwave js and it stopped responding in any usable fashion. I picked up a used BE469ZP off ebay to replace it. I found through experience with the older one that it was a little finicky with the pairing process.
- Exclude the lock
- Factory reset the lock
- Include the lock
For me the lock would give the green checkmark before the thing had paired with HE. I paired it off the door, next to the hub. The first couple tries I was a little slow entering the pin and the inclusion would just time out without any meaningful messages. When that would happen I would exclude the lock and restart the process. Third time was the charm.
To build on that, find the QR code on the metal backplate and use SmartStart to include it. Yes the QR is in a horrible spot if you have the lock already installed 
. I did SmartStart with both my BE469ZP and they paired without any issues.
I have two of these locks. One works great the other burns through a set of batteries in 3-5 days (I think faulty hardware).
Lots of more knowledgeable people have already chimed in. I was having trouble pairing the first one originally because I took to heart the stern Hubitat warning not to pair anything with security.... well I have since learned that warning is not well reasoned and now I pair everything with security if the device supports it. These locks must have security enabled to pair.
I was also suspicious about the ZWave link during pairing so I put Hubitat in WiFi mode (I normally have it Ethernet connected) and then with an extension cord moved it to a couple feet from the lock. Then I paired it. Some have said this is an unnecessary step but it worked for me. Once I moved Hubitat back to its home location I did a ZWave repair for that node just to update the new routing paths.
Hope you're having some success with the inputs from above.
As for me, I am souring on Schlage. I had a Kwikset lock that worked famously for 10 years and never had short battery life or other ZWave or system hiccups. I switched to Schlage so I could key it the same as my other (non electronic) locks in the home. I find the Schlage ZWave locks suspect. For instance, they do not seem to auto report as battery falls to warning level or to critical level. You either have to poll the lock (with a refresh command) or have some other event occur that causes it to report battery life. So I run a twice a day refresh to my working lock just to monitor battery. I know that wastes battery life but I don't understand why no unsolicited inbound message at certain battery thresholds. I also find the keypad backlight not well designed. There isn't an obvious spot to hit to light it up so you can see the numbers. So if you randomly hit a key (to turn on backlight) that is taken as the first digit of the code. I have to explain this so often as people enter the code but it is one digit too long so the lock errors. Its not all bad though, the tapered bolt helps in the event of slight misalignment, Kwikset didn't have this so isn't as forgiving for slightly ajar doors.
Schlage locks have defintely been a YMMV device...various Schlage FW versions work/don't work as well and Z-Wave vs. Z-Wave Plus versions have had different results for users. I've a BE469 Z-Wave for I think over 8 years now and it's worked perfectly on ST at first, and then on Hubitat. 
This was posted a while back...
Found a way to consistently secure-join my locks and have them work with Lock Manager:
- Exclude the lock from the the network (Extend bolt, Schlage button, 6 digit programming code, 0) and factory reset the lock (unplug battery, hold Schlage button and plug in battery).
- Delete all existing codes manually from the lock itself (Schlage->Programming code->2->enter 4 digit factory codes twice
- TURN OFF all other Z-wave devices near the hub and lock. I unplugged/cut power to/pulled the air-gap on as many devices as possible. This was more important than bringing the hub close for me.
- Pair with hub.
- Enroll in Lock Manager and ensure user codes successfully transfer
- Turn on other Z-wave devices
I was able to secure join my locks even from 20-30 ft away.
