Help. I have tried a half dozen times to get my new August Pro Lock to connect to Hubitat with no success.
The August App says it is connected but the discovery wheel on the Hubitat side never stops spinning and it never shows the August Pro Lock.
I have tried all suggestions on this thread but just can't make it work. I have platform version 2.0.6.112 and still can't seem to get the driver that Maxwell suggested to detect it.
Any other suggestions. Thanks in advance.
Did you have it paired to another hub before? I originally had mine paired to Smartthings v3, and was having a hell of a time pairing it to Hubitat when it was time to make the jump. Turned out that despite being unpaired from ST, the hub kept connecting to when I was trying to pair it to Hubitat. I had to go into the old ST Classic shop and unpair it right after doing so in new ST app, and it finally worked.
Similar process for me. This lock is hard to pair in general. I might have even seen somebody say they had to pair it with S2 enabled.
I have a Ring Alarm which is actually really good for excluding devices. You might want to exclude it again after it's unpaired just for good measure.
No luck here. On the few occasions something shows up during inclusion, it gets stuck at "initializing", and the log shows this:
groovy.lang.MissingMethodException: No signature of method: keyWe-Z-Wave-Lock.installed() is applicable for argument types: () values: []
Possible solutions: uninstalled() (installed)
For some reason it shows up as keyWe, and if I try to interact with it afterwards nothing works. I also tried switching the driver to August and Generic lock, nothing worked.
Any hints?
Thanks!
Maybe they changed the fingerprint for this lock, can you post the fingerprint that's in the data section of the driver?
yes except the device didn't complete the join process at all.
there should be values in the data section.
can you look in zwave details and see if a device with id 06 exists in there?
Device ID and Type being MaxInts can't be a good sign...
I noticed that the keyWe lock is the last item in my driver list, so maybe that's why it got picked here, and it's just a coincidence it's also a lock device?
Just a reminder that if you change drivers (e.g., to the August Pro Driver) you should probably hit the Configure button on the Device page to make sure the driver sends the setup parameters to the lock. This presumes that the hub and lock are communicating . . .
Nope, another indication that pairing didn't finish.
Not sure what's going on other than mesh related problems, I have one of these obviously, and honestly it had paired to my development and production hubs without any mucking around.
As an fyi, the batteries that shipped with mine didn't last but a month, have you tried a fresh set?
I think I am getting optimistic about connecting my August Pro Smart Lock 3rd gen to HE. I have only connected it to the app (not ST or Wink, my previous system). So in order to connect this to HE, do I need to disconnect it from the August app, then try to reconnect to HE first? I am a tad confused about the order, since it sounds like HE is particular about the order for connecting.
As additional info, I just looked at my lock's Z-wave setting, and it says "Your lock is connected to a Z-Wave hub."
I had my August Pro Smart Lock 3rd gen completely setup and working wonderfully via the August Pro app before I got my HE, then added it to HE without having to make any changes at all to the existing setup with the app. I can still use the August app, with all of its features and options, and everything works perfectly fine.
As someone mentioned in the thread above, the August Connect uses Bluetooth to communicate with the lock, so connecting to HE via Z-Wave shouldn't impact your existing setup at all, except that you'll start seeing in the app something along the lines of "unlocked via z-wave".
As a side note, I've noticed that HE doesn't always get the updates from the lock. It could be something particular to my environment/setup and I didn't play around with it too much, but it seemed to happen when the door would auto-lock. If you notice this behavior, you may want to add an app to refresh the lock state after the door closes, with a delay to account for the auto-lock delay. I did that and haven't seen the issue since.
Semi-success! I factory reset it twice, excluded it, factory reset again, and tried to pair/include and it worked! I am sure I did an extra unnecessary step, but finally got it to connect. Now the easy question: can a tile open and close this? I tried setting this up with the generic Z wave lock, but not able to unlock or lock from HE (or set up a tile to see if it is locked or unlocked). Thoughts or advice?
As regards tiles. My device type is "August Pro Z-Wave Lock" which works for me, Make sure you pick the "lock" template and not the "door control" and it should work fine. ( waynespringer79 was kind enough to help me with this.)
Also, a note on my experiences with this lock since there seem to be 2 threads on the topic.
I had found that the lock only worked for a short period of time and then failed to respond but can be woken up with the August wifi app.
A lot of people seem to think it needed a repeater because the Zwave signal strength was too low.
I started out thinking, yes the signal might be low and that I might need a repeater. So, I activated a Zwave light switch, which is just 3 feet from the lock but the thing still sleeps.
Now, I am becoming very confident that this issue is more to do with hibernating for battery preservation than signal strength. From my reading it looks like a beaming device is needed to keep it awake, I have ordered a Leviton switch with beaming capability. I will replace the switch I have that is close to the door with this one, probably Wednesday or Thursday. I hope/expect that this will solve the problem and will report back.
This is the beaming link https://community.hubitat.com/t/august-lock-struggles/14077/51
A repeater should also work as long as it is a beaming repeater.
Welcome to the Hubitat Community! Thanks for sharing your experience and providing some insight. I know this lock is being a real PIA for a number of people. Good to have some tips to help them out. 
I think I have a range issue in mine. Can I use any plug in Z-Wave devices to extend it?
Zwave Plus plug in devices should work as a suitable repeater. Placing them on the opposite wall from the lock as opposed to beside them on the same wall will be a help.
Most lock issues are not range related. In locks, being battery powered, the Zwave radio is off most of the time to save batteries. The Zwave radio is periodically turned on for a few milliseconds to check for any (un)lock commands and if there isn't anything, goes back to sleep, When an (un)lock command is sent from the hub, the message is repeated several times and then the hub goes on about it's business. If the Zwave radio in the lock is awake at the exact time the message is sent out, the lock performs the action. It is almost unlikely that the Zwave radio in the lock would be awake to receive the message directly from the hub.
This is where beaming repeaters come in. A beaming repeater (Zwave Plus line powered devices), will capture the (un)lock command and when the Zwave radio in the lock wakes up and asks "anything for me", the beaming repeater forwards the command.
what do mean lock template vs door control? where is that set?
As I recall, I believe I was talking selecting "door" template in the dashboard setup. This may seem obvious but initially I thought I selected the "door control" template.
Download the Hubitat app
