Latch’s access products (M, R, T and C lines) are all designed to be installed and usable offline i.e. without ethernet or wifi connectivity. This is a major benefit to our solution as it means property managers/developers can install our products without having to run internet to all of the devices. There are certain pieces of vital information that do need to be transmitted between the device and our backend in order to ensure devices are performant and that the user list is accurate/secure. There are many of these pieces of information, however for the purpose of this document we will attend to the major ones below.
Time Stamp
In order to ensure that daily doorcodes adhere to prescribed windows, scheduled access times are active, and photo/activity logs are active, we need to sync a time stamp down to the device regularly.
Battery Info
In order for managers to understand how much battery is left on their devices and for emails to be triggered for their staff, the backend needs to receive battery info from the device.
User List
The user list is composed of all permanent credentials for all users. It identifies each user, and contains their BLE, NFC, doorcode and Weigand credentials, as well as the credential start/end time. Note: Temporary credentials are daily doorcodes and are not included in this User List.
Activity Logs/Photos
These are the photos and activity logs of all unlocks performed.
System Logs
These are logs taken by the device. They live on the device and need to make their way to the backend. These logs will enable triage of support tickets/investigations.
Note: While we do fully support our products in offline mode, it is recommended that there be cellular service or building wifi near each device in order to ensure that these pieces of information are consistently relayed in a timely fashion. If a device is located in a cellular or wifi deadzone, a user can sync their own credentials by opening their app in an area where they have connectivity, however this will not solve for time stamp, battery info, activity logs/photos or system logs which will create issues.
Sync Types
Update
This is a full update of every sync type. Manager App and Latch App do perform slightly different updates however from a user facing perspective they function the same. This is done by opening either app, selecting the door and pushing Update.
Passive Sync
Passive Sync is not a user facing feature. It is initiated after each BLE unlock from within the app and performs in the background. It syncs the battery info, time, activity logs/photos, and system logs.
Setting Up
If a user tries to unlock a door for the first time and they are not on the device’s user list then we need to perform a sync in order to add them to it. We do this through Setting Up. Prior to the unlock completing in the latch app, the UX switches to Setting Up. This is a sync type that updates the user list, and time on the device.
Connected Update
If a device is connected to the internet via ethernet/wifi/hub then the device is automatically updated on every change to the user list or every 24 hours (whichever is more frequent) remotely without any sync type intervention necessary.
Use Cases
Move In/Move Out
Adding permanent users to a device
To add a user to a device, the manager needs to invite them via Mission Control. They will add their name, email and assign them a key as well as a start time and an optional end time. The type of sync most useful for getting this user added to the device depends on their access to credentials.
App User
They will add themselves to the device using Setting Up, or if another user sets up/updates the door before arrival they won’t even have to do Setting Up.
Doorcode
Doorcode only users are not recommended as the only way to get the doorcode is via the app.
Keycard
Keycard only users will need to have someone i.e. a manager or roommate update the door for them. Only an update, or a setting up will add them to the door.
Note: Connected locks will remove users automatically without need for intervention.
Removing users from a lock
There are a few ways to remove a user from the device.
End Time
If the manager adds an end time to the user upon invitation, or afterward then the user will automatically be removed from the door once that end time is hit. This works with BLE, doorcode and keycard credentials.
Note: Any updates to the end time will require the user list be updated. This means app users will have to go through a Setting Up sync if their end time has been changed. For keycard or doorcode users, someone will need to manually perform an Update on the door.
Delete
If a manager removes a user’s key or deletes the user entirely then they will no longer see the devices in their Latch App. This means they will be entirely unable to use their app to unlock the door. However, if they’ve been granted a doorcode or keycard, those credentials will still live on the device until the device has been updated via an Update or Setting Up sync.
Note: Connected locks will remove users automatically without need for intervention.
Installation
Activating a device
Onsite Activation
This is the product preferred installation pathway as it ensures the device is on the latest firmware when installed and that an update has occurred in order to set the device’s time stamp.
Offsite Activation
This is an acceptable installation pathway so long as the installer is tasked with performing a Manager App update on the device itself once physically installed. This is to ensure the battery, and time are in sync as the device is live.
Note: Connected locks do not require the manual update at physical installation as they are automatically updated via IP or Hub.
Maintenance
Due to the need to care for and ensure the functionality of offline devices, it is recommended that building staff always check for firmware upgrades, and perform updates/battery checks when entering a unit. This will ease the need to have to perform these functions outside the normal building cadence.
Playbook
Standard Latch Building
At a Latch building that wants to give credential optionality to it’s users but also wants to ensure reasonable security at each door, we recommend that property staff not have access to all units all the time. When a unit is vacated it can be added to a maintenance/management key. When added to that key it will be added to each maintenance person’s list. Since they are not currently on the device they will perform a Setting Up when they go to unlock the door. This will fully remove all expired users and add on any users that need to have access during the turnover until a new resident arrives.
Once a new resident leases, the device should be removed from the maintenance/management keys so the resident will go through a Setting Up sync, removing all expired users and adding themselves and their roommates, ensuring that all expired credentials are removed. New residents can be assured that only the right people, per building policy, have access.
Fully Remote Management
Some properties are trying to eliminate all need for onsite staff intervention at the doors. There are a few ways to accomplish this.
End Time
Adding an end time for each user and updating on lease renewal. A building will still need to update doors for keycard/doorcode primary users as there is no other link between the backend and the door if the app isn’t being utilized.
Limiting Credentials
Since the app will remove a user’s BLE credential when that user is deleted, the only gap in credentials that requires syncing is doorcodes or keycards. A building can choose to not distribute keycards and disable doorcodes on their residents or on all keys. This will ensure that updates do not need to occur for the user list.
Hubs
Connected hubs for each device fully empower the building to utilize all credentials and keep all the locks healthy and up to date in real time without need for intervention from management.