Well, then. You've made it abundantly clear to me and other respected members of this community that you will be the only one with the right answers on this, I might suggest that you take your troubleshooting with bmott0817 off the topic and in to PM so that no one burdens you with any more ideas. I, personally find this thread frustrating as it keeps getting pm'd to me because I've solved this issue on 3 of my own locks and assisted in solving the issue for several other users here. But, I'll bow out and definitely be hands off going forward. Good luck. I hope you find your answers.
In all fairness, there might be two separate issues at play. @bmott0817 did try to pair the lock from 6" away, and it still didn't pair securely (correct?). If so, that indicates an issue with the z-wave module (or with the Hubitat).
But, I agree with you that on the face of it @jonasd1 's issues closely parallel what you described and resolved a long time ago.
First thanks for help and info on all of this!
I understand the extenders etc. I had this issue with my Schlage lock and the extenders fixed it. This is the not the same case.
Heres my thoughts as a “average” consumer. I installed two locks separate brands on the same day. I have issues with the Alfred and none with the Yale. Both should in theory work the same as they are both the same distance from the hub and in fact the Yale actually has zero z wave items around it. Yale works like a champ Without extenders so the average person would assume the Alfred unit just isn’t up to par. I then installed ANOTHER Yale Z wave lock a few days later in another part of the house. Still no issues. At this point 2 Yale’s and even my Schlage work as they should. Makes you wonder. Now my Alfred. Doesn’t report anything. It’s just kind of hanging out. Sure right now I’m controlling it with Alexa and it does what I need but it SHOULD work with hubitat so I can set rules around it. The average customer would just return the Alfred and get another Yale (the Yale is cheaper as well). That’s exactly what I’m going to do if this doesn’t get fixed. Alfred support has been great though so I’m willing to at least try to resolve the issue. I really believe it’s just a bad module based on what I’m seeing in the hub. I like the lock and the features but it needs to work without major hassle And chasing issues. Hopefully the module fixes it and we’re smooth sailing.
About 6 months ago, I replaced my Schlage locks with Yale locks. Couldn't be happier. They've worked out of the box from day 1. One difference is that my Schlage locks were z-wave locks (firmware 6.8 and 5.1), while the Yale locks are zigbee.
There's 2 things happening here. I'm not making anything abundantly clear. I'm saying a new module might be needed based on what bmott has described. Aside from that however, I have my own battery drain issue that i have been dealing with for a while now and talking to the Alfred folks about. I'm not making any assertions that anybody is wrong or right (that happens a lot here with some, but i'm not doing that) I'm simply saying this is what I got from Alfred about my battery drain issue, no more, no less.
Hope this helps...
And I looks like Bmott is having a module issue, but that's been totally rolled over with your troubleshooting. After I looked back, I found that he hadn't successfully paired it close to the hub.
This thread has run out of useful help/suggestions and needs to be closed.
Replaced my module today. Popped the old one out, new one in. My problem is solved. Lock now works with the hub as it should. Lock paired securely even with the hub being "far away". Attached is the before and after device pages showing the difference. Sometimes you just get a bad part.....
Glad this worked out for you!
Exactly this has happened to me, same issue with lock status, happened at the same hub update as you too, only difference is my locks are conexis l1 smart locks from Yale, looks like this issue could be one thing in one of the recent updates, given the similarity in the cases.
Try the generic z-wave lock driver, have same issue and using as a work around and it updates the status flawlessly,
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.