Understanding: Dormakaba Saflok/Ambiance Digital Key Error Codes
This article details the error codes that may be encountered by guests when attempting to use a digital key synced to the Lynx mobile app to unlock a door with a Dormakaba Saflok model lock on the Ambiance platform.
When to use this guide
- When a guest using a Dormakaba Ambiance or Saflok digital key issued by Lynx encounters an error message in the Lynx mobile key app
Note: While some error codes indicate a condition that can be addressed via guest education, others may require assistance from the device manufacturer. For these errors, please reach out to the Dormakaba Support team at +1 (800) 999-6213 and select the "Saflok" option when prompted.
List of Specific Error Codes and Troubleshooting Steps:
| Error Code | Detailed Error Message | Steps to Troubleshoot |
| 113 | Key/Lock Conflict: The lock is in an unusual setting and doesn't accept this key right now. Please notify the front desk. | Contact Dormakaba Support |
| 117 | Too Many Tries: Too many incorrect keys were used. The lock is temporarily shut down. Please refresh the key or contact the front desk. | Contact Dormakaba Support |
| 122 | Wrong Lock: This key is not programmed to open this specific lock. Please check your room number. | If guest is confirmed attempting to unlock the correct door and within the stay access window, clear app data/cache and reinstall our app. Otherwise, contact Dormakaba Support. |
| 123 | Wrong Room: The key is not available for this lock. Check your room number. | Guest is trying the wrong lock. Check that the stay is on the correct room. If guest is confirmed attempting to unlock the correct door and within the stay access window, clear app data/cache and reinstall our app. |
| 127 | Missing Code: The key is missing a necessary internal code for this lock. Please get a replacement key from the front desk. | Contact Dormakaba Support |
| 128 | Old Key [date]: Your key is expired. Please refresh key or get a new key from the front desk. | Guest is trying the wrong lock. Check that the stay is on the correct room. |
| 129 | Old Key [time]: Your key is expired. Please refresh key or get a new key from the front desk. | Guest is trying the wrong lock. Check that the stay is on the correct room. |
| 134 | Old Key Sequence: Your key is too old for the current lock settings. Please refresh key or get a new key from the front desk. | Contact Dormakaba Support |
| 135 | Key Too New: Your key is too new for the current lock settings. The system needs to be updated. Please contact the front desk. | Contact Dormakaba Support |
| 136 | Key Used Up: This key was only meant for a limited number of uses and has expired. Please get a new key. | Contact Dormakaba Support |
| 137 | New Key/Room Occupied: This key is new, but the door is dead bolted. If you're checking in, the room may still be occupied. Please see the front desk. | Contact Dormakaba Support |
| 141 | Key Expired: The key is expired based on the lock’s clock date and time. | Replace key with a duplicate key with a later expiration date and time. If the issue persists, contact the Dormakaba Team. |
| 149 | Key Disabled: This key has been temporarily disabled by the system. Please refresh key or get a new key from the front desk. | Contact Dormakaba Support |
| 150 | Key Disabled: This special-access key has been temporarily disabled. Please refresh key or get a new key from the front desk. | Contact Dormakaba Support |
| 152 | Key Level Locked Out: The key's access level is temporarily disabled by the system. Please contact the front desk. | Contact Dormakaba Support |
| 154 | Either the Privacy Mode is active on the lock or the dead bolt is engaged. The key cannot override these settings. | Contact Dormakaba Support |
| 178 | This key will only be active at your scheduled check-in date and time. | Advise the guest that they are trying to use their key before their scheduled check-in time. |
| Learn more about configuring Ambiance/Saflok integration at our article on How to: Dormakaba Ambiance (Saflok) here. |
Comments
0 comments
Article is closed for comments.