I know there have been a few threads on this but if there is a solution I must have missed it. Has anyone successfully been able to pair this lock with the C7? I now have every other device migrated to the C7 except for this lock and my Ring Doorbell. From what I've read, the Ring will only work with Alexa utilizing virtual switches to make it work with Hubitat anyway so I plan to leave it until I can find/afford a different solution.
The FE599 excludes fine from the C5. However, to do so I had to run a network cable all the way to the door. I then followed the instructions to set the FE599 to factory. Many attempts to pair with the C7 were futile, it would find unknown Zwave device with ID of 1B(This was different each time I tried) and then just hang on initializing.
I really like this lever lock, it looks really nice and it's worked flawlessly for almost 3 years with the C5 but the C7 just doesn't seem to like it. I had to give it up for the day so I repaired it with my C5 and it paired with no problem.
I normally do my best to work through these things on my own but this time I'm totally stumped so I just wondered if anyone has made one work with the C7.
@bluzeman Ring doorbell can be used with the unoffical ring integration in Hubitat Package Manager.
For the lock, what firmware are you using? If above 8.0 pair the lock within 3 feet of the hub. If you have a failed pairing of that or any other z-wave device, STOP what you are doing and look in your z-wave details page for ghosts and remove them or you will have more problems pairing.
Thanks for the reply. For Ring, I would still have to depend on Alexa or IFTTT as without one of those, I can't detect button pushes from what I understand. I only have the doorbell and the gen 2 button pad. I have other RTSP cameras that I rely on more than the ring camera.
How would I find what version of firmware the Schlage is using? I've been through everything under the driver, and zwave details under settings and don't see it anywhere.
I have a FE599. I spent a day of my life reading the forums and fighting my new C7. I read it all.
It is not possible with current Hubitat C7 firmware. Like you it sticks on initializing. Based on other posts I think its related to security handshake failure. Firmware of the lock does not seem to be that interesting as knowing won't help... you can't flash it.
If someone has figured out the magic on a C7 with the FE599 I would love to hear! Last device on SmartThings ...
Right now I am using a virtual switch on both Hubitat (combo contact/switch driver) and SmartThings for a bidirectional integration. That way I can switch in Hubitat or Alexa and things keep in sync.
I would love to flush SmartThings to give Samsung their reward for ruining that platform
On the keypad or the doorbell? I have the keypad integrated with the C7 and it works fine but when I read the community driver page I thought it said you still have to use Alexa or IFTTT to get the doorbell to work with Hubitat. I'll go read through it again. Thanks.
Yeah, I dumped Smartthings officially last year after I finally got everything onto my C5. Then last month, I decided I wanted to integrate the Ring Keypad into my security routines. Oops! Won't work with the C5. So I got a C7 and have almost everything moved over to it.
I've been reading another thread about keeping cloud and Alexa stuff on a separate hub so I think for now I'll just keep the lock on the C5, as it works fine there. That and my Ring Doorbell are the only physical devices I have left on it.
Thanks for the reply, sorry to hear you're having the same issues. The FE599 is a very nice looking lever lock.
My gen 2 doorbell logs when the button is pushed. You can use log entries to trigger automations. My only issue with the camera portion is the doorbell goes to sleep which causes display errors in the log until it wakes up.
Thanks, I'll test it out. Mine is a Ring 2 that I got in 2019 so I'm guessing that means gen 2.
I recently set up my harmony hub and remote and had to capture the codes for the bulb and socket buttons from the logs, so this would be something similar to that?
OK, that would be great. I want away from anything cloud based as much as possible, although in reality there will probably always be some cloud element involved for some things. Not sure if I'll get time to mess around with it much until after the holiday's now but I'll definitely reply back and let you know how it goes.
Well, to be fair, the ring integration is cloud based. If you want a doorbell cam that isn't there are far more elegant solutions available. For me my ring 2 is simply to talk if possible to who's outside, I bought it way before hubitat came into my life. I find it irritating because by the time we're notified someone is on the porch (lets say a delivery driver) by the time the cam comes up on my phone they're getting into their vehicle. Probably this year I will be abandoning that in favor of something else. I use a local NVR for all my video recording and that gets offloaded every 5 mins to the cloud for backup (30 day rotation). My primary cams throughout are foscams.
Ok I'll share my FE599 firmware version for posterity if it helps.
I don't see it on the back plate. But SmartThings is reporting the FW version as 43.37
Not sure if that helps. Again mine hangs every time on initializing. Factory reset. Exclude, etc. I have tried many different hoop jumps. Sadly nothing.
These aren't on the supported list, but still they should pair I would think. Maybe @bcopeland would have insight as to why they seemingly time out when trying to be included...
It was also pointed out elsewhere that that is a 14 year old lock that hasn't been updated since 2008. It's quite possible it's 300 Series lock and/or the firmware just won't play nice with the 700 series SDK. There are firmware issues with the be469 pre 7.10 firmware that behaves similarly.
