You have the steps? (Or already know how?)
1 Like
This might be a less than ideal post for this because this post is discussing "inclusion" errors--your post might get more useful feedback either as a new post or in one more closely associated with your concerns and issues.
Yes, thanks, you gave them to me in another thread. I hope to get this done soon.
1 Like
Sorry - everyone looks alike here. 
1 Like
- HE Include (1st try after lock reset) result: FE599 blinks Green ~6 times. HE = Found Z-Wave Device with id 0B... Initializing. However the HE still just hangs in Initializing state.
I am encountering the same issue, FE599 an inch from C7 hub running 2.2.4. Get to the "initializing" step but nothing happens after that. I have to restart the hub (safe shutdown, unplug 30 secs) then exclude then the same thing happens again when I try to re-pair it (I have done it at least 15 times now)...tried new batteries too and that didn't help. While in the intizilating step I have gone to the z-wave devices page and it is at the bottom. I've tried hitting discover and waiting, that doesn't seem to help; same with repair and refresh.
See logs below:
Do you have a **Z-Stick? If so you might try including it on the hub as a secondary controller and then trying to include the lock that way. I was able to pair my Aeotec Recessed door sensor 6 doing this. Not sure how it would work with S0 security but might be worth a shot. The Z-stick is also good for excluding devices remotely.
** I apologize - I know this seems to be a repeating answer on these forums.. but Z-Sticks and UZB's are really darn useful especially when things go sideways.
I have the zwave.me USB stick. A few days ago I was able to successfully pair it using the USB stick as a secondary controller. Once paired the lock was not responsive in hubitat and the last activity parameter remained at the time that it was paired. Since then I've been under the impression that you can't pair S0 using the USB stick and that the lock needs S0 to function properly (hence why it may not have been responding?). So I abandoned that approach and instead went for the direct approach direct to the hub
1 Like
Ah okay - I knew you couldn't do that with S2 security wasn't sure about S0.
I'm not sure either 
I know its S0 and/or S2 that the USB can't pair with...but I figured the safest route was direct to hub, eliminate more potential confounding variables since the lock stuff seems to be really touchy
1 Like
How long do you wait on the Initializing step on the dicover page? I've had devices pop in up to two to three minutes after that initial Initializing message appears. Maybe try setting a four minute timer next time?
Also, when you get into the state below, how many times do you bang on the Discover, Refresh, and Repair buttons?
I ask because I've had devices in that state and had to hit the buttons (all of them!) 8 to 10 times or more before things changed and the device was discovered.
Also have found that just rebooting when a device is stuck like that sometimes allows it to complete the join process but sounds like that didn't work for you.
Just to be in the safest possible position, the next time you try to included it, I would exclude it again first. You can do that, excluding devices that aren't included is a normal action and ensures clears the Z-Wave deets on the device are cleared.
Well, that's unfortunate. It looks like this problem wasn't resolved with 2.2.4. I tried countless times to pair my FE599 to my C-7 running 2.2.3.148 without success. I finally gave up and replaced the FE599 with a Kwikset SmartCode 912, which paired right away. Your Z-Wave stick may come in handy, though, as you probably have a ghost node from the failed pairing of the Schlage.
How long do you wait on the Initializing step on the dicover page? I've had devices pop in up to two to three minutes after that initial Initializing message appears. Maybe try setting a four minute timer next time?
Also, when you get into the state below, how many times do you bang on the Discover , Refresh , and Repair buttons?
I ask because I've had devices in that state and had to hit the buttons (all of them!) 8 to 10 times or more before things changed and the device was discovered.
Ah I've done it some many times now with different variations. At least twice I've let it sit in that initializing step for between 15 minutes to a couple of hours operating on the suspicion that maybe it just needs more time. I've hit the Discover, refresh, and repair buttons while watching the z-wave log...messages come in for a few minutes then stop...then I hit the button again or tried another one like repair. Nothing appeared to be going differently, but you're saying you've had success hitting it 10+ that with devices that are stuck in initializing until it changes to an actual device? My experience has been those buttons have never done anything for me out of the 50+ devices I've added to my z-wave network...when they get stuck in initializing invariably I've had to exclude them and add them back.
Just to be in the safest possible position, the next time you try to included it, I would exclude it again first. You can do that, excluding devices that aren't included is a normal action and ensures clears the Z-Wave deets on the device are cleared.
Yup, I've been excluding it then resetting the lock every time before trying to re-include it. I've also used my old Smartthings hub to exclude as well as the USB stick.
@WindowWasher Ah that's a bummer, it's comforting to know at least that I haven't been alone in the struggle. I've checked for ghost nodes, sometimes it produces them sometimes it doesn't. I have used the USB stick to remove them when necessary
Turn off your ST hub when excluding the devices from HE. It's a "just to be sure" step that others have advocated due to ST potentially trying to join the inclusion party uninvited.
Yes, I've exlcuded ghosts/bad joins on 2.2.4 staring w/the first beta, by beating on those Discover, Remove, Refresh, Repair buttons repeatedly. Many times repeatedly. Has worked for me in all cases but one where I ended up having to kill it w/UZB+PC Controller.
Embrace the five-year old in you, the one who hits the Up and Down elevator buttons believing that will make the elevator arrive sooner. 
In this case that five-year old mentality can be helpful.
1 Like
I don't want to sound too negative, but the problem may be with the Schlage implementation. The FE599 is an old model. All of my other Schage locks paired easily on both SmartThings and my C7.
If you finally give up, remember that the Black Friday deals are happening soon. I picked up one of my locks last year during the BF sales. 
2 Likes
For sure! I have two of the BE469 camelot deadbolts and they work great and are paired with HE. This particular FE599 is on a gate so it needed to be a lever lock (not a deadbolt).
If I can't get it to pair I'll likely continue down the HubConnect route, which has it's own problems that I would need to solve- HubConnect Lock --> extracting unlock code used from an Event
Then if that doesn't work, I may buy another lock and spend more money 
C'mon...you know that's what you really want to do. [Says tiny Iwbenso character in red costume w/horns and pitchfork.]
1 Like
No doubt, I have to pick my battles these days though you know. Still have my fingers crossed that someone will step in with a magical tip to get this thing included in my hub!
For the FE599 someone took their hub within a few inches of the lock with a long patch cord and paired it that way then took the hub back to its normal location and did a repair and everything worked for them that way.
I've had to do something similar with my garage door opener.
1 Like
If you ever win a battle, the Yale locks are pretty nice. Opt for the zigbee and save yourself all the hassles of zwave.
1 Like
