How to Tie a Smart Lock into the Alarm System

Why this matters

A smart lock tied into the alarm panel can make the system easier to live with: the history shows who came in and when, the door can lock itself when the system arms, and a code at the door can disarm the alarm so the household stops tripping it by forgetting the keypad. That last feature is the one to slow down on. It turns a lock code, typed on a keypad outside the house, into an alarm disarm code, and depending on who holds the codes that can quietly weaken the system the customer paid for. This card pairs and configures the lock, then works the disarm decision with the customer as a decision, not a default.

Door prep, bolt alignment and fitting are in Smart Lock Installation Technique. This card starts with the lock fitted and working mechanically.

Before you start

The lock's model and radio type, the panel or hub's compatibility list, the customer present for the code and disarm decisions, and a plan to put the account on test. Configuring automations that arm, disarm or report openings can send signals to the central station by mistake, so the account goes on test before you start and comes off test only after a signal is confirmed received (How to Put an Alarm Account on Test and Take It Off). The physical work is limited to a battery cover and a screwdriver.

Step 1: Confirm the lock and the panel can talk, and that the panel supports this lock

Smart locks use one of several radios: Z-Wave, Zigbee, Wi-Fi, Bluetooth, or Thread. The panel or hub has to speak the same one, and the same radio is necessary but not sufficient: the panel maker's compatibility list says which lock models it supports and which features (code management, user reporting, lock status) come through. Check the model, not just the radio.

Why first: a lock that pairs on a shared radio but is not on the list may lock and unlock from the app and never report which code was used, which removes most of the reason to integrate it.

Step 2: Clear it, then pair it close to the hub

If the lock has been paired to anything before (a previous owner's hub, a demo unit, a returned box), remove it from that network first: an exclusion on Z-Wave, or a factory reset per the maker. Then pair it within a few feet of the panel or hub. Locks join with secure inclusion; on Z-Wave the current method asks for the PIN printed with the lock's device-specific key, usually on a card in the box or a label on the lock. Keep that card with the job file.

Why close: secure pairing exchanges keys at low power, and a lock pairing across a house often fails partway, leaving a lock that is half joined and will not report. If the panel is not portable, pair the lock on the bench next to the panel before fitting it; a lock already on the door comes off for pairing and goes back on after.

Then check it from where it lives. Once fitted, lock and unlock it from the app and watch the status update. On a mesh radio like Z-Wave, run the panel's network repair or rediscovery after installation so the lock finds its route through powered devices (plug-in modules and wired switches repeat; battery devices generally do not). A lock that reports reliably on the bench and intermittently on the door is a range problem, and the fix is a repeater, not a new lock.

Step 3: Name it plainly

"Front Door Deadbolt," not "Lock 1" or the model number. Names appear in history, notifications and voice assistants, and a customer reading "Lock 1 unlocked at 2:14 pm" while away has to work out which door that was.

Step 4: Decide which codes exist and which the panel sees

Here is what each part holds and what it reports, with the door contact still doing its own job:

 OUTSIDE        |  INSIDE
                |
 [lock keypad]  |
 [lock]<--------+--radio-->[panel or hub]<----[door contact]
  holds the     |   bolt,    disarm rule,     reports the
  codes         |   slot,    lock-on-arm      door, not
                |   battery       |           the bolt
                |                 |
                |          [customer app]
                |          manages codes, if
                |          the platform does

Depending on the platform, the panel either manages the lock's codes (adds, removes and schedules them from the customer's app) or only reports which code slot was used. Either way, set them up so every code belongs to one named person: slot 1 is Pat, slot 2 is Lee, slot 3 is the dog walker. A code shared between people produces a history that says "user 3" and answers nothing.

Keep lock codes different from alarm codes as the shop default. The lock's keypad is outside, in daylight, often in view of the street. A code typed there is easier to observe than one typed at the alarm keypad inside, and if it is the same digits it opens the door and disarms the alarm. The platform may sync them if the customer insists; the risk is theirs to accept once it has been explained.

Step 5: Work the disarm decision with the customer

Most platforms let an unlock disarm the system, and most let you choose which unlocks count. The four kinds of unlock a lock reports are not equal:

• Keypad unlock with a named user code. The strongest case for disarming: a specific person proved a code at the door.
• App or remote unlock. A phone login disarms the house. If the customer's account password is weak, so is the alarm.
• Key or thumb-turn. A manual unlock says nothing about who did it, and a thumb-turn is someone already inside. Neither should disarm.
• Auto-unlock by phone proximity, where the lock offers it. It disarms because a phone came near the door, including a phone in a stolen bag.

The trade-off the customer is making: auto-disarm removes the most common false alarm (coming home and forgetting to disarm inside the entry delay), at the cost of making the outside keypad part of the alarm's security. Neither side is wrong for every household, so the same rule gets applied and the answer depends on who holds codes.

One rule, two households

The rule the shop applies: an unlock disarms the system only if every code that can do it belongs to a person who is also an alarm user, and only on keypad unlock with that person's code.

Household A. A retired couple, no cleaners, no one else with a code. The system went into alarm twice last year when one of them came in the front door carrying groceries and walked past the keypad. Both lock codes belong to people who are alarm users. The rule passes. Configured: keypad unlock with slot 1 (Pat) or slot 2 (Lee) disarms; app unlock, key and thumb-turn do not; auto-unlock off. Their entry delay stays as it was, because coming in through any other door (from the garage, say) still needs the keypad.

Household B. A family of four with a cleaner every Tuesday and a dog walker on weekdays. The cleaner and the dog walker have lock codes. The rule fails, because two codes belong to people who are not alarm users, and if unlocks disarmed, the dog walker's code would disarm the house. Configured: no unlock disarms. The dog walker's lock code is scheduled to weekdays 11:00 to 14:00 and the cleaner's to Tuesdays 08:00 to 13:00. Each of them also received an alarm user code with the same schedule, entered at the inside keypad, so the history shows "disarmed by Dog Walker" rather than a nameless disarm. The family keeps entering their alarm code inside, and the lock's job is to record arrivals and lock the door when the system arms.

What made the difference was the code list, not the family. If Household A hires a cleaner next spring, their configuration fails the rule the day that code is added, and the ticket says so in a line the office can read: "Auto-disarm is safe only while every lock code belongs to an alarm user; adding any other lock code means turning it off."

Two cases where the rule is not enough on its own. A household that relies on a duress code (an alarm code that disarms normally while silently signaling the central station) should not use auto-disarm even if the rule passes: a person forced to open the door will use the lock code outside, and the lock has no duress code, so the silent signal never gets sent. And a short-term rental fails the rule by construction, since guest codes change every few days; there the lock records arrivals and the alarm keeps its own codes.

Step 6: Keep the door contact, and set lock-on-arm if wanted

A lock reports the bolt, not the door. A bolt thrown with the door standing open reads "locked." The door contact stays on the door as the alarm's real sensor, and the lock never replaces it. Where the customer wants the door to lock when the system arms, set that automation, and set the system to tell them if the lock fails to lock (a jammed bolt on a swollen door) rather than arm silently over an unlocked door.

Step 7: Set low-battery reporting and tell the customer what it means

Smart locks run on batteries and report low battery to the panel. Make sure that report reaches the customer's app, and tell them in one sentence what to do: replace the batteries within the week, and keep the mechanical key somewhere outside the house that is not the doormat.

Finish test

With the account on test, run each event and check it in the system history:

• Keypad unlock with each named user code: history shows the lock name and the person.
• Lock and unlock from the customer's app, on cellular: the status updates on the phone and in the history.
• Thumb-turn and key: history shows a manual unlock, with no disarm.
• For a household with auto-disarm (A): arm away, unlock with Pat's code, open the door: the system disarms with "Pat" in the history and no alarm. Unlock with the thumb-turn while armed stay: no disarm.
• For a household without it (B): arm away, unlock with the dog walker's code inside the schedule, open the door: the entry delay starts, and disarming at the keypad with the dog walker's alarm code shows "Dog Walker" in the history. The same lock code outside the schedule does not open the door.
• Arm the system with the door unlocked: if lock-on-arm is set, the lock throws and the history shows it.

Then take the account off test only after the central station confirms receiving a test signal, and write onto the ticket each code's owner by name (never the digits), the disarm decision and the rule it rests on.

References

• See related: Smart Lock Installation Technique
• See related: How to Put an Alarm Account on Test and Take It Off
• See related: The Installer Code and Customer Passcode Handling SOP
• Panel and lock maker compatibility lists and pairing instructions