Same here, nothing discovers and I have a 401 at the end.
I'm completely new to HE and app dev in there, but here's what I found:
The various 409 errors are due to some HE UI/values not refreshing issues. That explains the need to click twice on the Login button (the first click sends the request with a null username), and the Validate button for MFA (same thing, the code is empty).
Easy fix: just add ", submitOnChange: true" at the end of the line starting with "input name: "twoFAcode"". Same thing for the line starting with "input name: "username"". For instance input name: "twoFAcode", type: "text", title: "Two factor auth code", description: "AuthCode", required: true, submitOnChange: true
With that fix, I'm able to proceed past the authentication. Looking at the code, we get a first token from the first request, which is sent along the mfa code, and in return we get a final access token from August. That token is then used to request the devices, and that's where I'm stuck with connectToAugust failed -- status code: 401, reason phrase: Unauthorized: [code:InvalidCredentials, message:access token not associated with a user]
I'll try looking further later, but chances are I won't be able to figure it out, I'm a total newb on this platform. Hopefully someone more knowledgeable will figure something out!!
I have installed the app and drivers. However, I can only get the lock with a bridge to connect. My 2 other locks are discovered but do not appear to function. Is the bridge necessary or is there a setting that I need to set?
PS I am a true newbie.
Did you do anything in particular to manage to get your devices to discover? I keep getting that same error "Access Token not associated with a user"...
Just set this up. The lock itself works great. However, I noticed the following error message from the App when I hit refresh:
2022-11-25 04:18:36.261 PMerrorjava.lang.IllegalArgumentException: Command 'updateKeypad' is not supported by device 313. on line 619 (method updateLockDeviceStatus)
I'm stuck trying to install this. I have my username (my phone number), same one I use to login to the app and the correct password - I do not receive an authorization code on my phone, my email or anywhere else.
I have also tried to login using the email address associated with my account as well.
Hello Guys, I am facing the below error after I successfully log in with the app. I enter my email and password then I receive the verification code. I verify and hit done. When I try to discover August:
I see the below in the logs:
errorconnectToAugust failed -- status code: 401, reason phrase: Unauthorized: [code:InvalidCredentials, message:access token not associated with a user]
@taylor is the driver still working? I am planning to purchase a 3rd gen August lock (the long one, not the round one) with a wifi bridge. And if its working - can you help me and explain as simple as possible on how to install this driver?
For anyone having trouble after migration to Yale Home (I think this applies only to non-US locks), you can change the this line: @Field static String global_apiURL = "://api-production.august.com"
to: @Field static String global_apiURL = "://api.aaecosystem.com"
(remove the <>)
Also worth re-mentioning @MathD's fix which improves our quality of life:
just add ", submitOnChange: true" at the end of the line starting with "input name: "twoFAcode"". Same thing for the line starting with "input name: "username"". For instance input name: "twoFAcode", type: "text", title: "Two factor auth code", description: "AuthCode", required: true, submitOnChange: true
I am trying once again to integrate my I think Gen 1 August Pro Door Lock with Zwave to Hubitat. Finally got the August app connected to lock via bluetooth. I have tried with security, without security, and cannot get it to show up in devices. Right now, in Zwave settings it shows up.
I have tried multiple times to exclude with August app, but it never goes away. Should I do My Hub is no longer working or will that break something, since hubitat does know about it.
We need to get the headers and API key correct too
Someone with a rooted Android phone who knows what they are doing would be able to get that information
I believe HomeAssistant & OpenHAB have working code
Currently, I have Yale Home connected to ST and then pulled to HA via HubiThings Replica
I will switch back to Z-Wave if it's not good enough, I have 3 L1 locks so I've had to spend 150ish to be able to edit keyfobs etc In the future after July 31st the app will stop working completely. I would feel better if I could move away from Z-Wave, I only have the locks and a few power plugs most of my stuff is ZigBee
The L1 on Z-Wave is officially supported by Hubitat, or is supposed to be.
It did work ok for a while but over the past year or so became very unreliable. It was suggested to me on the forum here that I use the Generic Z-Wave lock driver instead.
It worked better, but get a 6pm message every day that the locks have opened (6pm is when the locks send out battery status).
Then with Yale announcing their app is going away, and no means of managing key fobs unless you migrate to Yale Home I thought I might as well give it a try.
