PUBLIC_LOCK_IS_NOT_ACTIVE

Lock is not active.

The lock exists and belongs to this organisation but is currently marked inactive (e.g. offline, deactivated by an admin, or its TTLock pairing was revoked). Inactive locks reject all passcode and unlock operations until reactivated.

Example Error Response

JSON format

{
  "error": {
    "code": "PUBLIC_LOCK_IS_NOT_ACTIVE",
    "message": "Lock is not active.",
    "description": "The lock exists and belongs to this organisation but is currently marked inactive (e.g. offline, deactivated by an admin, or its TTLock pairing was revoked). Inactive locks reject all passcode and unlock operations until reactivated."
  }
}

Troubleshooting Steps

Follow these steps to resolve this error

Open the lock detail in the admin UI and re-activate it; if the TTLock pairing is broken, re-pair it.

Check the physical lock status — flat battery or lost connectivity will keep the platform record inactive.

System Logs

For detailed system information about this error, check the system logs in your BizKitHub Admin dashboard. We provide transparent access to all system logs including detailed error information, request traces, and debugging data.

Need Help?

If you're still experiencing issues after following the troubleshooting steps, our support team is here to help.

Contact Support

Related Resources

Last updated: May 19, 2026

Back to Error Codes