Thanks.. I don't see 144 on my version to roll back to. You must be on the beta list. I went back to 135 and it didn't go away. I emailed support about it so now I wait.
Nope. That was a very recent, but short lived update. In that other thread I linked above, I think it was .135 that broke it, and .142 that worked for me.
What update are you on, and what do you have available?
I am rooting for you guys. I transferred everything to a C7 and have not seen any more issues. Sometimes the hard part is convincing someone there is a problem to be fixed. I hope you get it all sorted!
1 Like
I have 142 and 135 and 129 ( previous version) on my list to roll back. I tried 142 but didn't fix it.
@mike.maxwell. since this device is not supported anymore I was wondering if you would considering releasing the driver to the public repo
I would like to try to add a few commands supported by these locks. There is no way I could spin up an entire driver but I could likely get a few commands working.
Thanks in advance for your consideration.
2 Likes
which commands?, and to which driver?
I was hoping to enable the toggle for the built in auto lock function. As well as the toggle for the alarm settings built into the lock.
Also I would like to respond to tamper events with notifications through hubitat.
I don't know if I would be able to accomplish it all, but you dont know if you dont try.
Thanks again
3 Likes
It would be super sweet if this could also track a "state" for the last action.
Unlock Person (by name, not code number)
Unlock Physical (i.e., from the inside)
Unlock Digital (i.e. from the hub)
Lock Keypad (i.e., from the outside)
Lock Physical (i.e., from the inside)
Lock Digital (i.e., from the hub)
There are some exceptionally cool things that can be done (auto arming, etc) with the lock, but you really need to be able to tell how the device was last changed.
1 Like
Agreed this lock has much more potential. Initially we used the generic zwave lock driver for it, so staff did not want to add the extra features. Then they spun up the dedicated driver and I asked for these features a few times, but it didnt happen. Now it is officially unsupported so was hoping i could get the code to try and add it myself.
Not sure what you mean by unsupported. By the hubitat team? If so why?
At some point @mike.maxwell had some big issues with the different firmware's of this lock if I recall corectly. From what I understand it was removed form the officially supported list.
Edit. I just realized my c7 hub has decided to quit controlling it again...
2 Likes
ahh thanks.. I'm wondering why we are not seeing any commands/traffic in the log when doing anything to the lock at all. It's like the firmware is not actually talking to the driver.
1 Like
these items are already contained within events, to the extent that the lock is capable of producing all of them.
As an example, most locks aren't capable of determining if the lock was manually unlocked from the inside thumb turn vs the exterior key.
events from a kwikset lock:
I've been using an app/driver that captures these events--haven't totally dug into it though.
It sets some virtual switches that can be checked later by rules to trap those sorts of things.
The point is, there needs to be a way to "IF-THEN-ELSE" this information in automations--the events triggered seem focused at a higher lever (i.e., locked/unlocked/changed).
I see locked and unlocked physically (which means the thumb), locked and unlocked digitally (which SHOULD mean the hub), and locked and unlocked (keypad) which tells you its the outside keypad.
However, I seem to be seeing multiple, conflicting events for a single action.
At some point, I guess I'll need to figure out how to fully write a driver for myself. ??
1 Like
I use a couple of rules that set variables to get announcements based on manually unlocked or a digital code is used. I cannot determine a difference between key or thumbturn. But since I have the only actual key, I know it was not opened with the key lol. I agree it would be nice to gain more control over this.
Edit: We seem to be cluttering up this thread that is requesting support. Any chance a mod can split these topics?
Yeah. A key and thumbknob will be indistinguishable, since those are physically doing the same thing.
I haven't used a key in decades. They are SO 2005. 
1 Like
So when I change the driver to "device" and click on Get Info, I get the response from the lock. It seems there is an issue with S2 code that broke the driver. @mike.maxwell @bcopeland, can you guys take a look at this please?
2 Likes
So I removed the Schlage lock and readded it which went fine but still the same problem. Can't control the lock at all. @bobbyD any words from engineering on my issue yet?
1 Like
@mike.maxwell any thought on this? Either adding these events or releasing the now unsupported driver so that we may try?
I am in the same boat as a lot of you in this thread I think. I have tried everything suggested to no avail.
I have a Z-Wave Schlage BE469 lock that has worked flawlessly since its installation on my Hubitat C-4. I have since upgraded to the C-7 hub and my locks were the last thing added. I have two repeating, beaming repeating devices within 5 feet of the lock and 3 more devices within 15 feet. Heck, the lock is only 25 feet from the hub with an interior wall with a doorway in it between them.
The lock will update codes, instantly report manual locks/unlocks, but will not lock/unlock from a rule or dashboard 30% of the time. If I wait a few seconds and do it again, it will usually work.
I have tried the method @april.brandt suggested earlier in the thread and others too, but it does not work.
I am almost to the point of punting my C-7 and going back to my C-4. Or find the Zigbee version of the Schlage and toss the Z-Wave version. However, bright brass is the only model I can find.
Anything else to try? I did not factory reset it, maybe that would help.....
