23102020-12-09 10:55:01.743 am errorjava.lang.NullPointerException: Cannot get property 'id' on null object on line 123 (createChildKeypad)
dev:23102020-12-09 10:55:01.737 am infoHome - Back Door createChildKeypad(id:xxxxxxxxxxxx; lockId:xxxxxxxxxxxx)
Fixed - the change is in the lock driver. Thank you!
2020-12-09 06:55:01.018 pm infoKeypad Found
app:20652020-12-09 06:54:45.095 pm infoKeypad Found
app:20652020-12-09 06:54:43.779 pm infoInitializing August Home.
app:20652020-12-09 06:54:36.712 pm errorjava.lang.IllegalArgumentException: Command 'createChildKeypad' is not supported by device. on line 630 (updateLockDeviceStatus)
What should happen after the keypad driver install? Do I need to do anything else? BTW, I have several Gen2 locks with Connects and Keypads. Will the keypads be discovered (or added) with these models? The locks do appear and I can control them. No battery info showing on locks or keypads (duh).
I have the keypad object now despite the error in discovery, what should we expect to be able to do with it? The lock code manager doesn't show this keypad as an option to program.
Excellent! I’ll check out that error tonight/tomorrow (it was a busy work day so might not get to it today)
Now that the device is populating I can start adding actual support to it... first on my list was just basics like battery and name.
The keypad should have a batteryLevel attribute that get's updated along with the lock status. from the screen grabs that doesn't look like it's showing up? if you enable debug on the lock device and keypad device and do a refresh do you see "updateLockDeviceStatus-KeyPadBatt: xyz"?
I see this error from the app:
The keypad log just shows RefreshCalled when I try to refresh that
The lock log shows only RefreshCalled and createChildKeypad(id:xxxxxx;xxxxxx)
Ok I think I know what's happening... or at least partly 
thank you!
Polling helps a lot. Battery level works great. This may work work with Yale Wifi/bluetooth locks too. Yale bought them last year I think. What stinks z-wave on the August isn't great but I'm keep seeing issue with the gears giving out. Yale my be the best option. This may help with that.
Did you update the driver code as well? That seems to be the problem - the keypad is actually a child device of the lock and you have to create the child device from the parent.
I'm not sure which ones to use are they all updated on github?
I'm still working out of the fork... so it's these versions:
App: https://raw.githubusercontent.com/thecloudtaylor/hubitat-augustlock/driversplit/augusthomeapp.groovy
Lock w/Door Sense: https://raw.githubusercontent.com/thecloudtaylor/hubitat-augustlock/driversplit/drivers/august_lock_doorsense.groovy
Lock w/out Door Sense: https://raw.githubusercontent.com/thecloudtaylor/hubitat-augustlock/driversplit/drivers/august_lock.groovy
I tried removing all devices and deleting the app but it was still detecting the keypad over and over and slowing my hub down so I'm rebooting now to see if it will stop.
The reboot stopped it.
I see the bug... let me put a fix in - as is it will just keep recursively calling
I pushed a fix... It's entangled with the next phase of getting keypads actually working... So you will need to update the app and drivers but hopefully it fixes the recursion bug.
If so it would also be really helpful to run the "Request Lock codes from all existing devices" from Lock Code Manager with debug tracing on for the august app. There should be a "getPin-params [uri:https://api-production.august.com/locks/xxxx" thats followed by "reJson: [created:[], loaded:[], disabled:[], disabling:[], enabling:[], deleting:[], updating:[]]". Hopefully that line actually has stuff in it. I'd love to get a snip of that (obviously redact the PINs/Names/LockIDs etc...
This building features w/out a test device is an interesting experience
Use these links again?
Download the Hubitat app
