Has anyone else encountered this issue with August lock integrations?
2020-02-05 14:18:59 ERROR (SyncWorker_12) [homeassistant.components.august] Request error trying to retrieve door details for Back Door. 429 Client Error: Too Many Requests for url: https://api-production.august.com/locks/xxxx
2020-02-05 14:18:59 ERROR (SyncWorker_12) [homeassistant.components.august] Request error trying to retrieve door status for Kitchen Door. 429 Client Error: Too Many Requests for url: https://api-production.august.com/locks/xxxx/status
2020-02-05 14:19:00 ERROR (SyncWorker_12) [homeassistant.components.august] Request error trying to retrieve door details for Kitchen Door. 429 Client Error: Too Many Requests for url: https://api-production.august.com/locks/xxxx
I found this issue thread as well. I’m not sure what the best way is to get eyes on this, but it might not hurt for you to also chime in on the issue thread.
I wonder if integrating the August lock to the Z-wave network would be a work-around? Does anybody use this lock on the Z-wave network and notice the same issue?
I do but it’s 60/40 at best (works/fails). Most of the time z-wave falls asleep and doesn’t wake up unless done so by bluetooth. I’ve tried everything and just basically default back to bluetooth/august connect.
Thank God, it isn’t just me. I noticed my lock was showing up as “unavailable” yesterday. I made the transition to a NUC with HassIO from my RPI and I cann’t get the lock re-integrated. I was pulling my hair out trying to see if this was an issue on my end? Anyone able to get this to work. My log shows these same 429 errors.
I just started getting the same thing today. I was able to log out and back into the same account on my phone, so it seems like the problem is confined to the HA integration
2020-02-06 22:41:10 ERROR (MainThread) [homeassistant.setup] Error during setup of component august
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/setup.py”, line 174, in _async_setup_component
component.setup, hass, processed_config # type: ignore
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/august/init.py”, line 170, in setup
return setup_august(hass, config, api, authenticator)
File “/usr/src/homeassistant/homeassistant/components/august/init.py”, line 119, in setup_august
hass.data[DATA_AUGUST] = AugustData(hass, api, authentication.access_token)
File “/usr/src/homeassistant/homeassistant/components/august/init.py”, line 182, in init
self._locks = self._api.get_operable_locks(self._access_token) or []
File “/usr/local/lib/python3.7/site-packages/august/api.py”, line 215, in get_operable_locks
locks = self.get_locks(access_token)
File “/usr/local/lib/python3.7/site-packages/august/api.py”, line 210, in get_locks
access_token=access_token).json()
File “/usr/local/lib/python3.7/site-packages/august/api.py”, line 296, in _call_api
response.raise_for_status()
File “/usr/local/lib/python3.7/site-packages/requests/models.py”, line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 429 Client Error: Too Many Requests for url: https://api-production.august.com/users/locks/mine
Same issue. I called August support, at first they said it was a 3rd party problem and that there was nothing they could do. Asked for a manager who was a little more accommodating. I explained that it’s really an issue with the API as it is called by the python client, I also encouraged them to release their own API client so they had control/visibility into their customers implementations. The manager said he would look into it and back to me when he could; he refused to give any communication guarantee stating that he may or may not even look in to this. Unfortunately I have several of their locks, didn’t realize the support was so bad.
If you have this problem I would recommend calling August support to help them understand that they have customers they have negatively impacted.
Same issue, but I have not updated my HA instance to 105.1 so this is almost certainly on August’s end.
Hopefully it’s just an error and not some restriction on API calls that prevents it’s from being useful. I was really liking my lock and it would suck if I needed to get rid of it because it won’t play nice.
