Damn son - you been busy!!
1 Like
@mike.maxwell has said no need to pair locks in place, unlike other devices. Why are you go through the effort? Does it make them more reliable in the long run?
Yes I know he's said that, but I have found that I like this statement (although not regarding locks) a lot better and seem much more reliable, if they do pair in place.
And actually somewhere I read (from Aeotec) that stated something to the effect of if you still have issues with locks after adding their repeaters to do a remove/readd to the lock to ensure the repeater finds your lock easier.
2 Likes
And are we finding it necessary to press "configure" on the device page after installing or reinstalling the device into Hubitat? It seems to be a necessary step on my old fe599.
2 Likes
Watching the logs if I brought the lock close (strong) enough signal to fully pair, the configuration/get codes ran automatically after inclusion (at least with my BE469's), But I did tap the configure a separate time for good measure (and mainly to see how responsive it was) between when I tapped it and when the log showed the events.
I don't think configure is needed if the lock fingerprint is in the driver, which if it says it's supported, then it is. But can it hurt to do it anyway, or does it just not do anything?
Yes it will log configuring again, but you are right, since it paired as a "Generic Zwave Lock" the driver automatically configured upon inclusion.
1 Like
I found this was necessary for the FE599, but not the BE469.
I’m not quite ready to call this one solved yet as it had been driving me bonkers for weeks.
But... 4 Aeotec repeaters has so far been the magic number for me. 1 within 5 feet of the hub and 1 in the closest outlet possible to each lock.
For the past few days things have been running smoothly. I will give it at least a full week before I will consider it solved, however 
2 Likes
Unfortunately my locks started getting flakey last night and today completely fell off again.
BUT there is hope due to this post! Adding user lock code failed on schlage lock
I will wait patiently knowing that it’s now being worked on, even though I am sure there are many priorities ahead of it.
Agreed, try rebooting your hub until then, When I had an occasional issue, that seemed to bring them back normal again.
1 Like
Im hoping this solves my issue, As I dont want to replace locks. Im thinking it will because if I move my hub in visual site of the lock it works fine. Move it back to the media closet and nothing happens.
2 Likes
What generated the map image?
I thought the native BE469 driver had fixed my problem, but I just had an issue over the weekend. So thinking some repeaters. Anyone else had issues since implementing repeaters?
Same here no issues since adding 4 range extenders
@mike.maxwell now that there is a dedicated driver for these locks would you consider adding the ability to change some of the extra functions from hubitat. Like turn on off the alarm and the built in auto lock feature?
3 Likes
Just seconding @cwwilson08's suggestion. While not necessary for anything I currently do, it would be nice to control alarm sensitivity and the auto-lock features of these locks.
3 Likes
Yes, my Wink Hub 2 is flawless when it comes to range. I am hesitant to get rid of it
At the moment I'm researching openHab to handle my zwave as I've previously stated that the zwave radio in the C-5 is far inferior to be usable, but only with the "secure" devices inclusion like locks.
Interestingly when reading the openHab zwave binding info the following is posted on their site.
Coincidentally, this gives a very good explanation of the problems most of us have it appears that the C-5 radio on "Secure" pairing is on "Low Power Inclusion" because as many of us know the locks and the hub almost need to be touching themselves to get a successful inclusion, unlike most other platforms that users (myself included) claim to not have the same issues with must be on either High Power Inclusion or Network Wide Inclusion. This is pure speculation on my part as I'm sure we will not be provided the actual cause of our problems.
But this seems highly likely to be the case, in my opinion.
