A smart lock is not finished when the app says “connected.” Accept the installation only after the door closes without force, every approved access method works, removed users stay removed, the lock reports the right state, and the household can still enter during battery, network, hub, and account failures.
Smart-lock acceptance test at a glance
| Area | Pass condition | Do not accept when |
|---|---|---|
| Door and deadbolt | Latch and bolt move freely with the door open and closed | The motor must pull a misaligned door into position |
| Local access | Key, thumbturn, keypad, fingerprint, and approved credentials work as designed | Any resident depends on one untested method |
| Users and codes | Named users have the minimum access and expired codes fail | Shared installer or household codes remain active |
| State and history | Locked, unlocked, open, and closed states and timestamps are accurate | The app shows a secure state when the door is ajar |
| Failures | Battery, internet, hub, phone, and power failures match the written plan | Mechanical entry or recovery is unknown |
| Handover | The owner has accounts, keys, records, support details, and test results | The installer retains undisclosed access |
1. Record the exact installation
Record the lock brand, model, hardware revision, firmware, door and deadbolt type, battery type, hub or bridge, network path, owner account, integrations, installer, installation date, warranty, and support channel. Photograph the inside and outside hardware without exposing codes or serials publicly.
2. Test the door before testing the electronics
- Open the door and extend and retract the bolt by hand.
- Close the door gently and repeat without pushing, pulling, lifting, or slamming.
- Test from inside and outside at least ten times.
- Check weather stripping, hinge sag, strike depth, bolt clearance, and seasonal movement.
- Confirm the inside release remains usable and meets local egress rules.
A motor that strains, reverses, or reports “jammed” is exposing a door-fit problem. Fix the door or strike rather than hiding the fault with stronger batteries or repeated calibration.
3. Verify every promised access method
Test the physical key, thumbturn, owner app, keypad, fingerprint, phone key, watch key, NFC card, Home Key, voice assistant, and remote unlock only when the exact model supports them. Test each method once from a normal state and once after relocking. Record which methods depend on Bluetooth, Wi-Fi, a hub, cloud service, phone power, or a subscription.
4. Audit owners, users, and codes
Keep one clearly named primary owner and a second documented recovery path. Give residents named accounts or codes rather than one shared credential. Test a permanent resident, a scheduled visitor, a one-time code, and an expired or removed user. The removed user must fail locally and remotely. Use the smart-lock access-code audit for offboarding and review dates.
5. Check auto-lock and door-position behavior
Test auto-lock timing with the door fully closed, briefly open, and deliberately ajar. Verify the lock does not confidently report a secured doorway when the bolt is extended into empty space. If a separate contact sensor determines door position, test its alignment, delay, battery, tamper state, and event history.
6. Verify alerts, logs, and privacy
Trigger lock, unlock, jam, low-battery, door-left-open, invalid-code, offline, and tamper events where supported. Confirm the correct named user, action, and timestamp. Decide who can view access history and how long it is retained. Do not expose codes, guest schedules, or household movement in shared screenshots or broad smart-home permissions.
7. Test alarm and smart-home integrations
Test arrival, departure, bedtime, guest, cleaner, and emergency routines one at a time. Verify whether unlocking disarms an alarm, which users can trigger that action, what happens after a forced entry, and whether a voice command requires authentication. Treat the alarm as a separate life-safety and intrusion layer. A smart lock must not silently disarm security because any household credential was used.
8. Run one-failure-at-a-time tests
| Failure | Test | Expected record |
|---|---|---|
| Internet down | Disconnect WAN while keeping local power | Local methods, remote loss, alerts, and recovery |
| Hub or bridge down | Power off the named dependency | Direct local access and integration changes |
| Phone unavailable | Lock the owner phone away | Independent resident and mechanical access |
| Low or removed battery | Use the maker-approved test | Warnings, emergency power, key access, replacement |
| Account recovery | Verify recovery without changing ownership | Owner email, MFA, trusted device, support path |
Keep somebody on the secure side with a tested mechanical key. Follow the battery and outage checklist; never create a lockout to prove a point.
9. Run a security and safety inspection
Check exposed screws, cylinder protection, strike fasteners, door and frame condition, emergency egress, fire-door requirements, rental permission, accessibility, child safety, and whether a visible keypad reveals code patterns. A connected lock cannot repair a weak door, frame, glass panel, or careless key-control process.
10. Complete the handover
The owner should receive all physical keys, primary ownership, recovery methods, user list, code policy, model and firmware, battery type, calibration notes, hub/network map, integrations, warranty, receipt, support case, test record, and next review date. Remove installer accounts and temporary codes while the installer is present. Store the result with the home-security documentation checklist.
11. Schedule follow-up tests
Repeat the door-fit and access test after 24 hours, after a week, and after weather changes, battery replacement, firmware updates, router or hub changes, resident turnover, or door repairs. Use the firmware update checklist before changing lock software.
Where Abode fits
When a smart lock is part of an Abode system, verify the exact supported integration, user permissions, alarm-state changes, automations, event history, hub dependency, and outage behavior. Compare the Abode Lock, Smart Security Kit, and current Abode plans for a sensor-led setup.
FAQ
How many times should a new smart lock be tested?
Test at least ten normal open-close cycles, every promised credential, a removed credential, door-position behavior, and each planned failure without forcing a lockout.
Should a smart lock move a tight deadbolt?
No. The bolt should move freely by hand with the door open and closed. Correct alignment and frame problems before acceptance.
Can the installer remain an account owner?
Only when the property owner knowingly requires an ongoing managed role. Otherwise transfer ownership, remove installer access, and verify recovery during handover.
Does a smart lock replace an alarm sensor?
No. Lock state, door position, intrusion detection, alarm response, and video evidence are separate functions that should be tested separately.
