I can imagine that would be challenging and a pain waiting for someone else to test for you and hope they updated everything correctly and get the logs you need. Seems really challenging.
Waiting doesn't really bother me as I can just start working on stubing out the next section... I think it's actually a good experience, makes you think about how the code will work... but it sucks when bugs escape that you just can simulate/think about.
1 Like
Do I use the same links you just sent earlier today?
It looks to be in a loop still. I had turned on debug logging too soon so now it's logging a ton each time it loops. I disabled the app and rebooted to try to get it to stop logging again then I'll try to pull some logs for you.
Disabling the app then rebooting is enough to stop the logging as the app remains disabled on reboot so any schedules or runs the app sets up never get started after the reboot and should prevent having to re-signin after the code gets updated.
tterk1, thank you for putting this together. Opened up my lock last night, found this thread, and had everything working within an hour. Great job on this.
Glade to hear it's working for you... I am finalizing a new version which should be published in a few days. It will add battery support (where relevant) and at least part of the KeyPad support (specifically getting pins).
1 Like
This is great! Thanks! Cannot wait until I see last build.
I am going to try and finish testing and push out the next version today... The last couple days where a lot busier than I had expected...
No problem. We get it. Thank you for the update.
I just pushed the new version. This has basic keypad support, it should discover them and allow you to get codes at least, adding/deleting codes requires more reverse engineering of the august API which really would require someone to with a keypad (I don't have one) and the extra fun of dealing with SSL pinning and a proxy.
It also has battery support :).
Thanks for the update I got the following error in the logs from the app:
2020-12-28 05:56:10.520 pm errorjava.lang.IllegalArgumentException: Command 'updateKeypad' is not supported by device. on line 611 (updateLockDeviceStatus)
But otherwise it looks like it's working correctly.
Thanks.
I think I see the problem, when I revised all the drivers they got marked as not required... So they didn't get an update. I just updated the manifest and pushed a new version, hopefully that forces the drivers to update.
It looks like you will have to change your existing devices to use the new driver after it pulls them down and then delete the old driver code (sorry, I guess that was a side effect of the change 
).
Hi,
The Discover button is not listing any devices, while the logs confirm the API call successfully (200) returns a payload with the device info. Here's the relevant lines of log (redacted to remove PII):
app:2612020-12-30 23:58:15.703 debugreHeader: Server: openresty/1.15.8.3
app:2612020-12-30 23:58:15.700 debugreJson: [LockName:Front Door, Type:2204, Created:2020-10-03T18:30:35.333Z, Updated:2020-10-03T18:30:35.333Z, LockID:redacted, HouseID:redacted, HouseName:redacted, Calibrated:false, timeZone:America/Los_Angeles, battery:0.8241744663773716, doorStateOpenTimeout:60, supportsEntryCodes:false, remoteOperateSecret:redacted, skuNumber:ST2_2020.04, macAddress:redacted, SerialNumber:redacted, LockStatus:[status:locked, dateTime:2020-12-31T07:42:13.054Z, isLockStatusChanged:false, valid:true, doorState:closed], currentFirmwareVersion:2.1.7-1.1.2, homeKitEnabled:false, zWaveEnabled:false, isGalileo:false, Bridge:[_id:redacted, mfgBridgeID:C5W02004EA, deviceModel:august-connect, firmwareVersion:2.2.15, operative:true, status:[current:online, lastOnline:2020-12-31T07:42:13.442Z, updated:2020-12-31T07:42:13.442Z, lastOffline:2020-11-05T05:33:46.108Z], hyperBridge:true], OfflineKeys:[created:[], loaded:[[created:2020-12-18T19:44:21.713Z, key:redacted, slot:1, UserID:redacted, loaded:2020-12-22T01:30:12.158Z]], deleted:[], loadedhk:[[key:redacted, slot:256, UserID:redacted, created:2020-10-03T18:30:35.343Z, loaded:2020-10-09T16:48:40.163Z]]], parametersToSet:[:], users:[redacted:[UserType:superuser, FirstName:Greg, LastName:redacted, identifiers:[phone:redacted, email:redacted]]], pubsubChannel:redacted, ruleHash:[:], cameras:[], geofenceLimits:[ios:[debounceInterval:90, gpsAccuracyMultiplier:2.5, maximumGeofence:5000, minimumGeofence:100, minGPSAccuracyRequired:80]]]
app:2612020-12-30 23:58:15.681 debugreCode: 200
app:2612020-12-30 23:58:15.544 debuggetLock-params [uri:https://api-production.august.com/locks/redacted, headers:[Accept-Version:0.0.1, x-august-api-key:79fd0eb6-381d-4adf-95a0-47721289d1d9, x-kease-api-key:79fd0eb6-381d-4adf-95a0-47721289d1d9, Content-Type:application/json, User-Agent:August/2019.12.16.4708 CFNetwork/1121.2.2 Darwin/19.3.0, x-august-access-token:redacted
Any ideas what the problem could be?
Thanks in advance 
interesting... do you see a set of debug traces to the effect of:
"LockID: xyz"
"LockName: Front Door"
"macAddress: xyz"
"HouseID: xyz"
"HouseName: xyz"
The other major possibility is that driver didn't get installed - there should be three drivers "August Lock with DoorSense", "August Lock", "August Keypad" but if it can't find the driver there should also be an error logged.
1 Like
Success here. I have the Yale w/August module. Took a bit of doing to get the 2FA to work properly. I had to run with the debug log on in another window to ensure that I was actually getting the verify message sent to August. Seemed to require two clicks on the verify, but it worked in the end. Thanks @taylor!
Yes, that was the issue. To fix it, went in Hubitat Package Manager, selected Modify, the August package, and the 3 drivers. No idea why they were not installed in the first place.
After that, discover properly worked.
Thanks a lot for your prompt reply!
Taylor, thank you for the amazing app. it works perfectly on my Gen. 3 August Lock pro + connect bridge. I have one question, Am I correct to presume that the only way to shorten the dashboard tile refresh time is to shorten the app refresh interval? if so, will it taxing the hub if I set the refresh time to one minute?
Thanks.
Yeah, its a polling model today. I have mine set for 5 min and that seems to be ok, I suspect 1 min wouldn't be terrible (Roku does it).
Yes, unfortunately there isn't a documented API so I can't figure out how there event subscriptions work (or even if I can get them to work with Hubitat). Hopefully someday we can figure out how it works or better yet they will document the API.
