Smart Lock Pairing: Complete 2024 Troubleshooting Guide

Quick Pairing Reference

Choose your protocol for specific instructions:

🔧 Protocol Selection Wizard - Not sure which protocol? Find out first

WiFi Lock Pairing

Standard WiFi Pairing Process

Prerequisites:

• ✅ WiFi network (2.4 GHz, WPA2/WPA3)
• ✅ Smartphone with manufacturer app
• ✅ Lock installed and powered (batteries fresh)
• ✅ Within WiFi range (test with phone)

Step-by-step procedure:

1. Install batteries in lock

   • Use fresh batteries (4× AA typically)
   • Verify lock powers on (LED/beep)

2. Download manufacturer app

   • iOS App Store or Google Play
   • Create account if needed

3. Open app and start pairing

   • Tap "Add Device" or "+"
   • Select lock model

4. Scan QR code (most locks)

   • QR code on lock or manual
   • Camera access required
   • OR: Enter serial number manually

5. Enter WiFi credentials

   • Select 2.4 GHz network (NOT 5 GHz)
   • Enter password carefully
   • Verify password before submitting

6. Lock connects to WiFi

   • Lock LED blinks (connecting)
   • Wait 30-90 seconds
   • Success: Solid LED or confirmation beep

7. Test lock in app

   • Lock/unlock via app
   • Verify status updates
   • Configure auto-lock if desired

Typical pairing time: 3-5 minutes

WiFi Pairing Troubleshooting

Problem 1: Lock Won't Enter Pairing Mode

Symptoms:

• No LED response
• No beep when starting pairing

Solutions:

1. ✅ Check batteries are fresh (>80%)
2. ✅ Try factory reset (hold button 10 seconds)
3. ✅ Remove/reinsert one battery
4. ✅ Consult manual for specific pairing button

Problem 2: Wrong Password / Can't Connect to WiFi

Symptoms:

• "Wrong password" error
• "Unable to connect" message
• Lock blinks red LED

Solutions:

1. ✅ Verify 2.4 GHz network (not 5 GHz)
2. ✅ Check WiFi password (case-sensitive)
3. ✅ Disable MAC filtering temporarily
4. ✅ Move router closer during pairing
5. ✅ Restart router and try again

Problem 3: Pairing Times Out

Symptoms:

• Progress bar stuck at 90%
• "Pairing timeout" error
• Lock gives up after 2 minutes

Solutions:

1. ✅ Check signal strength (need -70 dBm or better)
2. ✅ Move lock closer to router
3. ✅ Disable 5 GHz band temporarily
4. ✅ Check router firewall settings
5. ✅ Use phone hotspot as test

RSSI requirement: -70 dBm minimum for pairing

📖 Related: See our battery life optimization guide for how signal strength affects battery consumption.

Zigbee Lock Pairing

Standard Zigbee Pairing Process

Prerequisites:

• ✅ Zigbee hub (Echo, SmartThings, etc.)
• ✅ Hub already set up and online
• ✅ Lock within 15 feet of hub OR powered router
• ✅ Fresh batteries in lock

Step-by-step procedure:

1. Put hub in inclusion mode

   • SmartThings: Tap "+" → Add Device → Scan nearby
   • Hubitat: Devices → Add Device → Zigbee
   • Home Assistant: Integrations → ZHA/Zigbee2MQTT → Permit join
   • Echo: Alexa app → Devices → "+" → Add Device

2. Activate pairing mode on lock

   • Press and hold pairing button (5-10 seconds)
   • OR: Enter master code then press * key
   • Look for: LED blinks rapidly (pairing active)

3. Wait for discovery (30-90 seconds)

   • Hub searches for new devices
   • Lock broadcasts join request
   • Hub acknowledges and pairs

4. Enter install code (Zigbee 3.0)

   • Some hubs require install code
   • Found on lock label or manual
   • Format: 16-digit code

5. Pairing completes

   • Hub shows lock discovered
   • LED stops blinking (solid or off)
   • Lock appears in device list

6. Test communication

   • Send lock/unlock command
   • Verify instant response
   • Check signal strength (RSSI)

Typical pairing time: 1-3 minutes

📖 Need help choosing hubs? Check our Zigbee vs Z-Wave comparison for protocol differences.

Zigbee Pairing Troubleshooting

Problem 1: Hub Can't Find Lock

Symptoms:

• "No devices found"
• Pairing times out after 3 minutes
• Lock blinks but hub doesn't see it

Root causes and solutions:

Cause 1: Weak signal (most common - 40%)

• ✅ Check RSSI if previously paired (should be >-80 dBm)
• ✅ Move lock within 15 feet of hub for pairing
• ✅ Add powered Zigbee router between hub and lock
• ✅ Remove metal objects between hub and lock

Cause 2: Wrong Zigbee channel interference (20%)

• ✅ Check hub's Zigbee channel
• ✅ Change to channel 25 (least WiFi overlap)
• ✅ Keep hub 3+ feet from WiFi router
• ✅ Restart hub after channel change

Cause 3: Network at capacity (15%)

• ✅ Check device count (<100 recommended)
• ✅ Remove unused devices
• ✅ Create new network if needed

Cause 4: Lock not in pairing mode (15%)

• ✅ Verify LED blinks rapidly (not slow)
• ✅ Try alternative pairing method (check manual)
• ✅ Factory reset lock and retry

Cause 5: Hub needs exclusion first (10%)

• ✅ Put hub in exclusion mode
• ✅ Activate lock pairing (excludes old pairing)
• ✅ Then pair normally

Problem 2: Pairing Succeeds But Lock Doesn't Respond

Symptoms:

• Lock shows as "Online" in hub
• Commands don't execute
• "Command failed" errors

Solutions:

1. ✅ Check device type (ensure recognized as lock)
2. ✅ Update hub firmware
3. ✅ Re-pair with factory reset
4. ✅ Verify Zigbee 3.0 compatibility
5. ✅ Check if custom driver needed

Problem 3: Lock Pairs Then Immediately Disconnects

Symptoms:

• Successful pairing
• Shows offline after 1-5 minutes
• Must re-pair frequently

Solutions:

1. ✅ Signal strength issue (90% of cases)
   • Add powered router device
   • Improve RSSI to >-75 dBm
   • Check for metal interference
2. ✅ Power cycle hub (10% of cases)
   • Restart hub
   • Allow network to heal (24 hours)
   • Re-pair lock

Z-Wave Lock Pairing

Standard Z-Wave Pairing Process

Prerequisites:

• ✅ Z-Wave hub (SmartThings, Hubitat, Home Assistant)
• ✅ Know if lock is Z-Wave or Z-Wave Plus
• ✅ Have DSK code ready (on lock label)
• ✅ Fresh batteries in lock

Step-by-step procedure:

1. Put hub in inclusion mode

   • SmartThings: Add Device → Z-Wave
   • Hubitat: Devices → Add Device → Z-Wave
   • Home Assistant: Integrations → Z-Wave JS → Add Node

2. Activate pairing on lock

   • Press and hold pairing button
   • OR: Enter programming code
   • Lock beeps/blinks

3. Select security level (S2)

   • Hub prompts for security class
   • Choose: S2 Access Control (highest)
   • Required for door locks

4. Enter DSK (first 5 digits)

   • Hub displays partial DSK
   • Verify matches lock label
   • Enter first 5 digits of DSK
   • This prevents MITM attacks

5. Pairing completes

   • Hub confirms secure pairing
   • Lock added with S2 encryption
   • Test lock/unlock

Typical pairing time: 2-4 minutes (slower due to security)

Z-Wave Pairing Troubleshooting

Problem 1: Hub Requests DSK But I Can't Find It

Symptoms:

• Pairing process asks for DSK
• Can't locate DSK on lock or box

Solutions:

1. ✅ Check lock body (near battery compartment)
2. ✅ Check original packaging/box
3. ✅ Check instruction manual (may be printed)
4. ✅ Manufacturer website (may list by serial number)
5. ⚠️ Last resort: Skip security (S0 or no security)

Note: DSK is device-specific, can't be calculated or guessed

📖 Security details: Learn more about Z-Wave S2 security in our security analysis.

Problem 2: Pairing Fails During Security Setup

Symptoms:

• "Security negotiation failed"
• Pairing stops at DSK entry
• Lock times out

Solutions:

1. ✅ Verify DSK entry (exactly 5 digits)
2. ✅ Try inclusion again (can take 2-3 attempts)
3. ✅ Ensure lock is Z-Wave Plus (S2 support)
4. ✅ Update hub firmware
5. ✅ Factory reset lock and retry

Problem 3: Lock Pairs But Shows "No Security"

Symptoms:

• Pairing succeeds
• Hub shows lock without encryption
• "S0" or "No security" in device info

Cause: Lock paired without S2 (insecure)

Solutions:

1. ❌ Do NOT use lock this way (security risk)
2. ✅ Exclude lock (remove from network)
3. ✅ Re-pair with proper S2 process
4. ✅ Ensure DSK entry step completes

📖 After pairing: Configure secure settings to harden your lock.

Matter Lock Pairing

Standard Matter Pairing Process

Prerequisites:

• ✅ Matter-compatible platform (HomeKit, Google, Alexa)
• ✅ Thread Border Router OR WiFi network
• ✅ Lock QR code and manual PIN available
• ✅ Fresh batteries

Step-by-step procedure:

1. Choose primary controller

   • HomeKit: Home app
   • Google: Google Home app
   • Alexa: Alexa app
   • Can add secondary controllers later

2. Start pairing in app

   • Tap "Add Device" or "+"
   • Select "Matter" device type
   • OR: Select lock brand if listed

3. Scan Matter QR code

   • QR code on lock or manual
   • Includes setup code
   • Camera access required

4. Verify manual pairing code (backup)

   • If QR fails: Enter 11-digit code
   • Format: XXXXX-XXXXX-XXX
   • Found with QR code

5. Select network type

   • Thread (recommended for battery life)
   • WiFi (if no Thread Border Router)

6. Wait for commissioning (60-120 seconds)

   • Lock connects to network
   • Platform assigns to home
   • Lock appears in app

7. Assign to room and test

   • Choose room location
   • Test lock/unlock
   • Configure settings

Typical pairing time: 3-6 minutes

Matter Pairing Troubleshooting

Problem 1: QR Code Won't Scan

Solutions:

1. ✅ Better lighting (bright white light)
2. ✅ Clean camera lens
3. ✅ Hold phone steady, 4-8 inches away
4. ✅ Use manual code entry instead

Problem 2: "Unable to Commission Device"

Solutions:

1. ✅ Verify Thread Border Router online (if using Thread)
2. ✅ Check WiFi 2.4 GHz available (if using WiFi)
3. ✅ Restart Border Router
4. ✅ Factory reset lock
5. ✅ Update platform app

Problem 3: Pairing Takes Forever (>5 minutes)

Solutions:

1. ✅ Check Border Router proximity (Thread)
2. ✅ Check WiFi signal (WiFi Matter)
3. ✅ Restart pairing process
4. ✅ Update lock firmware first (if possible)

General Pairing Best Practices

Pre-Pairing Checklist

Before starting ANY pairing:

✅ Power check

• Fresh batteries (>80% charge)
• Verify lock powers on
• Test basic operation (manual lock/unlock)

✅ Signal check

• Lock within 30 feet of hub/router
• No metal walls between
• Test with phone at lock location

✅ Hub/app check

• Hub online and responding
• App updated to latest version
• Account logged in

✅ Documentation ready

• QR code accessible
• Serial number noted
• DSK code located (Z-Wave)
• Manual open to pairing section

Pairing Environment Optimization

Ideal conditions for pairing:

1. Distance: 10-15 feet from hub (not too close, not too far)
2. Interference: Turn off other devices temporarily
3. Timing: Avoid peak network usage times
4. Preparation: Read manual pairing section first

When to Factory Reset

Factory reset lock if:

• ⏰ Previously paired to different hub
• ⏰ Pairing fails 3+ times
• ⏰ Lock shows online but doesn't respond
• ⏰ Switching from one protocol to another

How to factory reset:

• Usually: Hold button 10-15 seconds
• Alternative: Remove battery, press button, reinsert battery
• Verify: Lock beeps/blinks confirmation
• Check manual for specific procedure

Signal Optimization for Reliable Pairing

Measuring Signal Strength

Get signal measurement:

Before pairing:

• Use phone at lock location
• Check WiFi strength (WiFi locks)
• Use signal meter app

After pairing:

• Check hub diagnostics
• Look for RSSI value
• Target: >-70 dBm

🛠️ RF Coverage Estimator - Plan optimal router placement

Improving Weak Signals

If signal is weak (<-75 dBm):

For WiFi:

1. Move router closer
2. Add WiFi extender
3. Switch to 2.4 GHz only
4. Update router firmware

For Zigbee/Z-Wave:

1. Add powered router device (smart plug)
2. Place router halfway between hub and lock
3. Ensure 2+ routers in mesh
4. Change Zigbee channel (if applicable)

For Matter/Thread:

1. Add Thread Border Router
2. Add Thread router devices
3. ✅ Improve Border Router placement

🗺️ Plan your network: Use our Mesh Network Planner to optimize router placement.

Protocol-Specific Tips

WiFi Lock Tips

• ✅ Use 2.4 GHz (never 5 GHz)
• ✅ Disable band steering temporarily
• ✅ Static IP helps some locks
• ✅ Disable MAC filtering during pairing

Zigbee Lock Tips

• ✅ Pair close to hub, then move to door
• ✅ Use channel 25 for least interference
• ✅ Keep hub away from WiFi router
• ✅ Allow 24 hours for network optimization

Z-Wave Lock Tips

• ✅ Have DSK ready before starting
• ✅ Choose S2 Access Control (mandatory)
• ✅ Update hub Z-Wave firmware first
• ✅ Exclude before inclusion if pre-paired

Matter Lock Tips

• ✅ Update platform app first
• ✅ Use QR code (easier than manual)
• ✅ Choose Thread over WiFi for battery
• ✅ Can add to multiple platforms after initial pairing

📖 Deployment guides: Check Airbnb setup or enterprise deployment for scale.

Frequently Asked Questions

Do I need to be near the lock while pairing?

Yes, for most protocols:

• WiFi: No (but phone needs to be on same network)
• Zigbee: Yes (within 15 feet)
• Z-Wave: Yes (within 10 feet)
• Matter: Yes (within 15 feet)
• Bluetooth: Yes (within 30 feet required)

After pairing: Can control from anywhere (depending on protocol/setup)

Can I pair one lock to multiple hubs?

Depends on protocol:

• WiFi: No (single cloud account)
• Zigbee: No (one network at a time)
• Z-Wave: No (one controller at a time)
• Matter: YES (multi-admin is the key feature)
• Bluetooth: Depends on lock model

Matter is unique: Can pair to HomeKit, Google, and Alexa simultaneously

What if pairing works but commands fail?

Common issue: Pairing succeeds but lock doesn't respond to commands.

Likely causes:

1. Weak signal (pair near hub, but door location too far)
2. Hub doesn't support lock features
3. Firmware incompatibility
4. Need device driver update

Solutions:

• Improve signal with routers/extenders
• Update hub firmware
• Check manufacturer compatibility list

How do I switch from one hub to another?

Proper procedure:

1. Factory reset lock (removes old pairing)
2. Pair to new hub normally
3. Don't try to "force pair" without reset

Note: Some locks require exclusion from old hub first (Z-Wave especially)

📖 Troubleshooting: If pairing still fails, see our complete troubleshooting guide.

Tools & Resources

🔧 Protocol Selection Wizard - Choose best protocol
📡 RF Coverage Estimator - Plan signal coverage
🔋 Battery Life Calculator - Check expected battery life
🔍 Smart Home Integration Checker - Verify hub compatibility

Related Articles

Protocol & Setup

• Protocol Overview - Understand your lock's protocol
• Zigbee vs Z-Wave Comparison - Protocol differences
• Battery Life Guide - Signal affects battery life

Installation & Configuration

• Installation Guide - Proper installation basics
• Door Compatibility - Ensure door compatibility
• Secure Configuration - Post-pairing security

Troubleshooting

• Connection Stability - Fix ongoing connection issues
• Complete Troubleshooting - Comprehensive problem solving
• Command Timeout Errors - Timeout issues
• Power Outage Recovery - Reconnect after outage
• Emergency Battery Died - Lockout recovery

Use Cases

• Airbnb Setup - STR pairing tips
• Enterprise Deployment - Large-scale pairing
• Long-Term Rentals - Multi-property pairing

Advanced Troubleshooting Scenarios

Scenario 1: Intermittent Pairing Success

Problem: Lock pairs successfully sometimes, but fails randomly.

Pattern Analysis:
├─ Success: 3 out of 7 attempts
├─ No clear error message
├─ Timing appears random
└─ Frustrating "it works sometimes" issue

Root causes:

1. RF interference (70% of cases)

   • Other devices on same frequency
   • Microwave oven nearby
   • Baby monitors (2.4 GHz)
   • Bluetooth devices

2. Low battery during pairing (15%)

   • Lock shows full battery
   • But motor draw during pairing drops voltage
   • Causes pairing to abort mid-process

3. Hub resource exhaustion (10%)

   • Hub is processing other devices
   • Network healing in progress
   • Firmware update running in background

4. WiFi DHCP issues (5%)

   • Lock gets IP but loses it
   • Router DHCP pool exhausted
   • IP conflict with another device

Systematic diagnosis:

Step 1: Eliminate interference
├─ Turn off ALL 2.4 GHz devices temporarily
├─ Move 10 feet away from microwave
├─ Disable Bluetooth on nearby devices
└─ Test pairing (success? → interference confirmed)

Step 2: Battery test
├─ Install FRESH batteries (even if old show 100%)
├─ Use lithium (not alkaline) for testing
├─ Test pairing immediately after battery install
└─ Success? → Battery issue confirmed

Step 3: Hub isolation
├─ Temporarily unpair other devices
├─ Pair lock when hub is idle
├─ Check hub CPU/memory usage
└─ Success? → Resource contention confirmed

Step 4: Network diagnostics
├─ Reserve static IP for lock (DHCP reservation)
├─ Expand DHCP pool if needed
├─ Check router logs for IP conflicts
└─ Success? → Network issue confirmed

Permanent fix: Address root cause identified above.

Scenario 2: Pairing Succeeds But Lock Is Unresponsive

Problem: Lock appears paired in app, but doesn't respond to any commands.

Symptoms:
├─ Lock shows "online" or "connected"
├─ Commands timeout or fail
├─ Sometimes shows battery level correctly
└─ But won't lock/unlock

Common causes:

Cause 1: Phantom pairing (lock not actually paired)

Diagnosis:
├─ Hub shows lock but no real communication
├─ Lock doesn't know it's paired
├─ Usually after failed pairing attempt

Fix:
├─ Factory reset lock
├─ Remove from hub completely
├─ Wait 5 minutes
├─ Pair fresh with correct procedure
└─ Verify bidirectional communication

Cause 2: Paired but out of range

Diagnosis:
├─ Paired successfully near hub (10 feet)
├─ Moved to final location (50 feet)
├─ Too far for reliable communication
├─ Pairing works, commands don't

Fix:
├─ Add mesh router/repeater devices
├─ Move hub closer to lock
├─ Use WiFi extender (WiFi locks)
└─ Target: RSSI better than -70 dBm

Cause 3: Missing device handler/driver

Diagnosis:
├─ Hub doesn't have proper lock driver
├─ Shows as "generic Z-Wave device"
├─ Can't interpret lock-specific commands
├─ Common with newer lock models

Fix:
├─ Update hub firmware
├─ Install manufacturer device handler
├─ Check community forums for custom drivers
└─ Wait for official driver release

Scenario 3: Previously Paired Lock Won't Re-Pair

Problem: Lock worked fine, stopped responding, now won't re-pair.

Situation:
├─ Lock worked for weeks/months
├─ Suddenly became unresponsive
├─ Removed from hub
├─ Now won't pair again
└─ Stuck in "ghost" state

Resolution procedure:

Step 1: Complete factory reset
├─ Remove batteries for 60 seconds (not 10!)
├─ Press lock button multiple times while out
├─ Reinsert batteries
├─ Perform manufacturer factory reset
└─ Wait for confirmation beep/flash

Step 2: Hub-side cleanup
├─ Remove lock from hub
├─ Perform Z-Wave exclude (even if not showing)
├─ Clear hub cache if possible
├─ Reboot hub completely
└─ Wait 5 minutes for mesh to settle

Step 3: Fresh pairing attempt
├─ Start inclusion on hub
├─ Activate pairing on lock within 10 seconds
├─ Watch for DSK prompt (Z-Wave)
├─ Complete security setup
└─ Verify lock responds to commands

Step 4: If still fails
├─ Try different hub/controller temporarily
├─ Update lock firmware if possible
├─ Contact manufacturer support
└─ Possible hardware failure

Multi-Lock Fleet Pairing

Best Practices for 10+ Locks

Scenario: Property manager deploying 50 smart locks across buildings.

Challenges:

• Time-consuming if done individually (50 × 15 min = 12.5 hours)
• Consistency required (all same network, settings)
• Documentation needed (which lock is which)
• Testing at scale

Optimized workflow:

Preparation Phase (2 hours):
├─ Create spreadsheet: Serial # | Location | DSK | Install Date
├─ Label each lock with location code before install
├─ Pre-configure hub with lock zones/rooms
├─ Assign static IPs if WiFi locks
└─ Prepare installation teams

Installation Phase (1 day for 50 locks):
├─ Team A: Installs locks physically (50 × 10 min = 8 hours, 2 people)
├─ Team B: Pairs locks to network (50 × 5 min = 4 hours, 1 person)
├─ Team C: Tests each lock (50 × 3 min = 2.5 hours, 1 person)
└─ Parallel execution: 8 hours total with proper staffing

Pairing Assembly Line:
├─ Station 1: Power on lock, verify battery
├─ Station 2: Start inclusion, enter DSK
├─ Station 3: Assign to location, test command
├─ Station 4: Document completion, QA check
└─ Process 6-8 locks per hour per station

Efficiency gains:
├─ Serial process: 50 × 15 min = 12.5 hours
├─ Parallel process: 50 ÷ 4 stations ÷ 5 locks/hr = 2.5 hours
└─ 5× faster with organized workflow

Quality assurance:

Checklist per lock:
├─ [ ] Physical installation secure
├─ [ ] Paired with S2 security (Z-Wave) or equivalent
├─ [ ] Lock/unlock test successful
├─ [ ] Battery level >90%
├─ [ ] RSSI better than -70 dBm
├─ [ ] Location labeled correctly in hub
├─ [ ] Documented in asset spreadsheet
└─ [ ] Spare physical key stored securely

Performance Optimization After Pairing

Network Health Monitoring

Post-pairing optimization (first 48 hours):

Hour 0-24: Mesh network self-optimization
├─ Devices discover optimal routes
├─ RSSI values stabilize
├─ Battery consumption normalizes
└─ Expected: Some command failures normal

Hour 24-48: Network stabilization
├─ Routes locked in
├─ Performance should be consistent
├─ If still issues → manual intervention needed
└─ Expected: >95% command success rate

Week 1-2: Baseline establishment
├─ Track average response time
├─ Monitor battery drain rate
├─ Document RSSI values
└─ Create performance baseline for future comparison

Performance metrics to track:

When to add mesh routers:

Indicators you need more routers:
├─ RSSI consistently <-75 dBm
├─ Command success <90%
├─ Frequent "device unreachable" errors
├─ Battery drains faster than expected
└─ Locks >50 feet from hub

Router placement strategy:
├─ Place halfway between hub and problem lock
├─ Use always-powered devices (smart plugs)
├─ Target: Every lock has 2+ route options
└─ Overkill is better than underkill for critical locks

Optimizing Pairing for Battery Life

Battery-conscious pairing strategy:

Standard pairing (most people):
├─ Pair lock wherever convenient
├─ Accept whatever signal strength results
├─ Battery life: 8-12 months (Zigbee/Z-Wave)
└─ Acceptable for most use cases

Optimized pairing (power users):
├─ Measure RSSI before final lock placement
├─ Add routers BEFORE pairing if needed
├─ Pair only when RSSI >-65 dBm
├─ Battery life: 12-18 months
└─ Worth it for hard-to-access locks

Why it matters:
├─ Poor signal → lock retransmits messages
├─ Retransmits consume 2-3× power
├─ Compounds over months
└─ 50% battery life difference possible

Measurement procedure:
├─ Install lock (don't pair yet)
├─ Place phone at lock location
├─ Use WiFi analyzer app (for WiFi locks)
├─ OR: Temporarily pair basic Zigbee sensor at location
├─ Measure RSSI for 5 minutes
├─ If <-70 dBm: Add router first
└─ Then pair lock for best battery life

Troubleshooting Decision Tree

Systematic pairing troubleshooting:

Pairing fails?
│
├─ Lock powers on?
│   ├─ NO → Replace batteries (fresh, not rechargeable)
│   └─ YES → Continue
│
├─ Hub sees lock during discovery?
│   ├─ NO → Signal/range issue
│   │   ├─ Move closer (10-15 feet)
│   │   ├─ Check interference (turn off 2.4GHz devices)
│   │   └─ Try different time of day
│   │
│   └─ YES → Continue
│
├─ Pairing starts but fails mid-process?
│   ├─ WiFi lock → Check WiFi password, 2.4GHz enabled
│   ├─ Z-Wave lock → Check DSK entry, try S2 Authenticated instead
│   ├─ Zigbee lock → Check install code, try without security
│   └─ Matter lock → Check Border Router, update platform app
│
├─ Pairing completes but lock unresponsive?
│   ├─ Check RSSI (add routers if <-70 dBm)
│   ├─ Update hub firmware
│   ├─ Factory reset lock and re-pair
│   └─ Check device handler/driver compatibility
│
└─ Pairing succeeds but no security (Z-Wave)?
    ├─ Exclude lock
    ├─ Re-include with S2 Access Control
    └─ DO NOT USE without encryption

Summary: Pairing Success Checklist

Maximize pairing success rate (95%+):

Before pairing:

• Fresh batteries installed (<1 week old)
• Lock powers on and operates manually
• Hub/router within 30 feet of lock location
• Documentation ready (QR code, DSK, manual)
• App/hub firmware updated to latest
• Interference minimized (other devices off)

During pairing:

• Follow manufacturer procedure exactly
• Don't skip security steps (DSK, QR code)
• Allow full time for pairing (don't rush)
• Verify each step completes before proceeding
• Note any error messages for troubleshooting

After pairing:

• Test lock/unlock 3 times minimum
• Check RSSI signal strength (target: >-70 dBm)
• Verify security enabled (S2, encryption)
• Assign to correct room/zone in app
• Document in asset tracking system
• Monitor for 48 hours for stability

If pairing fails:

• Factory reset lock completely
• Remove from hub (exclude if Z-Wave)
• Wait 5 minutes before retry
• Try at different time of day
• Contact manufacturer support if 3+ failures

Bottom line: 90% of pairing issues are interference, low battery, or skipping steps. Systematic preparation and following exact procedures yields 95%+ first-attempt success rate. For large deployments, assembly-line workflow reduces per-lock pairing time from 15 minutes to 5 minutes while maintaining quality.