Status 429 error handling

[jlg89]

The console output currently shows "FetchError: Status 429 (undefined): undefined" when August rate-limits a connection. It might be useful to make it read something like, "FetchError: Status 429 (Too Many Requests): The August server has rate-limited the connection. Email support@august.com to inform them that they are breaking things."

[jlg89]

Seems to me we could use the "setTimeout" function in node.js to put an artificial delay between API calls, so (for example) pulling status for multiple locks from the August server could be slowed down to avoid rate-limiting. At least for testing/debugging?

[jlg89]

The issue at hand is that I have a facility with seven August locks, and August has set their rate-limiting such that, when august-api is initialized and pulls initial status for the locks, it only gets through five or six of them before getting locked out. I am running this through August support, but I don't have a lot of confidence that they'll be willing to fix this. It would be helpful to have the ability to impose a rate-limit on august-api so that we could adjust for whatever rate-limiting nonsense August elects to impose on its end.