Remote Operation Error Codes

HTTP Error Code	Error Category	What likely happened?	User Message in August App
408	LOCK UNAVAILABLE	Some sort of timeout, usually a request was sent to Connect to send to the lock and the server didn’t receive a response in a timely manner. There might be multiple reasons behind this, one of them is if the lock stop functioning (for example no power at all)	Lock Unavailable
409	CONFLICT	In the case of GET /locks/:lockID/status, this indicates the lock has no bridge.
412	PRECONDITION FAILED	Check the error text for the exact precondition that failed, e.g. Lock does not have a bridge associated with it.
422	CONNECT UNAVAILABLE	Connect hasn’t connected to our services in a while (usually 3-5 minutes), means that the Connect is offline.	Connect Unavailable
423	BRIDGE IN USE	The bridge is currently communicating with the lock	Connect Unavailable
460	LOCK BUSY	The lock is busy talking over bluetooth to something else like a keypad or August App.
500	LOCK UNAVAILABLE	Some server error	Connect Unavailable
530	LOCK UNAVAILABLE	There was a mechanical timeout, usually indicates a jam	Lock Is Jammed
531	LOCK UNAVAILABLE	There was a problem detecting the mechanical position of the lock, either an uncalibrated lock or a jam.	Lock Calibration Failure
550	LOCK UNAVAILABLE	Low battery, usually will return when there isn’t enough power to either Lock or Unlock the door.	Low Battery Failure
551	LOCK UNAVAILABLE	High temperature	Lock Overheated Failure
560	LOCK UNAVAILABLE	Unexpected disconnect during communication: while processing a command (status/lock/unlock) the lock disconnected abruptly from Connect.	Lock Disconnected

💡 Click for full sequence diagram.

Besides those codes you may also receive: 532, 533, 534, 540, 541, 562, 563, 564 and 565. These are internal error, which you can interpret similarly to a 500.

Lock Must be Upright

The August Smart Lock has a lot of sensors in it, including a sense of orientation. If the lock is not mounted on a door or other vertical surface then it can behave in unexpected ways.

We will look into why the lock disconnects in this case and I'll update this note if we make any changes. A 531 might make more sense.

Other errors I've been able to produce because the lock was not mounted:

530

{
    "code": 30,
    "message": "Mechanical Timeout"
}

560

Error Code 560 JSON payload looks like this:

{
    "code": 60,
    "message": "Unexpected Disconnect"
}

563

{
    "code": 63,
    "message": "packet error"
}

These were in response to /remoteoperate/:LockID/unlock and afterwards I would often get

{
    "code": 97,
    "message": "Bridge in use"
}

Waiting about 2 minutes would usually free up the bridge again.