The following errors can occure during communication with a BLE lock. They can point onto device specific problems, but also towards setup or communication issues.
If you report an error to us, please use the code, which is mentioned as number, to refer to a specific type of an error.
Short name: INVALID ACTUATOR ACTING REQUEST
This error points to an error during development. The BLE stack just indicates, that the request is incorrect.
Short name: INVALID ACTUATOR ACTING REQUEST FORMAT
This error points to an incorrect format of the request. Please check that the payload is in the defined format.
Short name: INVALID CHECKSUM
This error indicates, that there where errors during communication between mobile phone and BLE device. Please retry the request.
_Short name: SERVER_RESPONDED_WITHERROR
When the lock would deny the request, it tries to double check that decision live against the backend. If the backend responds with (validation) errors, they are shown here.
Short name: INVALID SERVER RESPONSE
When the lock would deny the request, it tries to double check that decision live against the backend. If that request fails on the backend, this error is shown.
Short name: NO ACTUATOR FROM SERVER
If there is no valid actuator referenced in the request, this error is raised. Please double check the setup on the backend.
Short name: NO ACTUATOR BY THAT INDEX LOCALLY FOUND
If there is no valid actuator referenced in the request, this error is raised. Please refresh the cache on the lock itself, by restarting it.
Short name: JSON
If there is a general parsing error during the communication between mobile phone, lock or backend, this error is show.
Short name: OTHER
If there is any here not mentioned error occuring, this message is show. It contains the details of the error.