I have been using this Schlage reliably on ST for about 4 years.
I have tried resetting the lock, rebooting the hub, excluding and adding countless times. I have the lock located inches from the hub.
The lock will exclude, and then it will be discovered... but never get past the "Found Z Wave Device with ID XX + Initializing... dialog.
With other devices I am able to reboot and try again. I have been through this about 25X and I can't get it to pair.
I have the same lock, same results trying to pair on my C-7. And, yes, my lock worked fine on ST once I got it to pair (which was painful even on ST). TLDR - I finally gave up and bought a Kwikset to replace the Schlage
Take a look at this thread for more on this lock:
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)...trie…
@ArchStanton sounds like you’re in the same boat as me. I imagine you still have your ST hub? If so you could probably go the same route as I ended up going using hubconnect
That would be great. I'm pretty confused why lastCodeName wasn't thought to be included by the developers of HubConnect for ST? In any case I appreciate anything you're willing to look into!
In the meantime I believe I have a workaround. I have webCoRE running on that ST hub. webCoRE has the ability to parse that last used lock code easily, so I made a piston that for each lock code I have, it will ping a local endpoint trigger in a rule in HE RuleMachine and do what I want from there. With gro…
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.