August Component not authenticating

Configuration
1

Hi everyone, I have the August Lock with an August connect and had the august component working well until the last couple of days where I’m now getting “invalid config” please check your config. I believe it’s probably related to the api key in the august.conf file expiring but nothing I seem to do will allow me to renew it. I’ve tried deleting the file, removing parts of it, rebooting Hassio, rebooting the Pi, nothing seems to work. Has anyone any suggestions on what I can do so that I get the configurator pop back up and let me authenticate again? Assuming that’s the actual issue…

Cheers!

2

facing the exact same issue. Deleted .august.conf file, removed the configuration, but didn’t help.

3

there is an open issue for expired api-key - https://github.com/snjoetw/py-august/issues/6

4

Thanks, thought I was going crazy and had done something wrong. Good to know I’m not a complete idiot!

Cheers

5

Is this resolved ? I still have the same issue, running latest version of hass. have tried deleting conf file, removing component, restarting, readding etc etc but no luck. The links suggest it was due to be fixed in V76. Currently running v77.2 and still no success. If any one has fixed this on hass and has some pointers then I would be forever grateful!

6

It’s certainly resolved for me, was a couple of versions back. I can’t recall exactly what I did but deleting the august.conf and restarting (perhaps a full reboot of the Pi) and I got a new authentication request from August. Once I did that it was back and running well.

7

thanks for responding.
Still no go for me. I am running that function on a windows 10 > oracle virtual box > ubuntu > hass
maybe that has something to do with it
Have deleted the .august.conf from config folder and restarted (a million times)
tried removing and re-adding the august component, just comes back with the same invalid config message
will keep trying stuff :roll_eyes:

8

Perhaps try changing the authentication method from phone to email or vice versa and deleting the conf file too, that may trigger the new authentication request? I may have done that! :slight_smile: __

9

OK, feel a bit stupid, was fixed by putting the password in inverted commas. Didn’t think of this as it never was needed before and even the HASS August component notes don’t show the password in inverted commas. However this is what worked in the end (after a few days of solid work - AAAAARRRRGHHH!) :tired_face:

10

That’s weird, I have mine in the secrets file but no inverted commas…