Understanding: Assa Abloy Keyless Lock App
The Assa Abloy keyless lock app from Lynx works differently from other lock integrations. The Lynx integration connects to your on-premise Assa Abloy server to provide key-less entry using a mobile app that guests download to their phone to activate the lock via Bluetooth. This article provides an overview of features that are supported, as well as some key differences between this technology and other common smart locks.
- Prerequisites & Setup
- Overview of Lynx Integration Steps
- Functionality in the Lynx Portal
- Functionality in the Lynx Guest App
- Troubleshooting & Fallbacks
Requirement: You will need to purchase the keyless-check-in and Native mobile guest app add-ons in your Lynx subscription plan to utilize this integration.
Prerequisites & Setup
Before enabling mobile access, ensure the following prerequisites are met at your property:
- Visionline Software: Must be installed, operational, and connected.
- Hardware: BLE-compatible Assa Abloy locks should be installed and configured.
- Network: Internet connectivity must be available and stable on the Visionline server.
- IT Personnel: Are required to install and configure the Visionline software, ensure the server has network connectivity, connect the lock hardware, and assist with troubleshooting any connectivity or firewall issues.
Overview of Lynx Integration Steps
The system uses your existing Assa Abloy hardware to configure access. This integration must be configured by the Lynx Customer Success and Tech teams (Support does not have access to these configuration tools). Below is a high-level breakdown of the setup process:
| Step | Actions |
| Step 1: |
Reach out to Assa Abloy support for assistance setting up mobile access. A mobile access account should be set up.
|
| Step 2: |
Your Visionline instance must be made publicly reachable by the Lynx server. Please whitelist the following Lynx IP Addresses so we can connect to the on-premise Visionline server:
|
| Step 3: |
Provide the following details for your Visionline server to your Lynx CSM:
NOTE: You may need to configure your HTTP server and/or firewall to allow access from Lynx servers. Be sure to also provide Lynx with the list of all common doors. |
| Step 4: | Add and authorize the connection. |
Note: Common doors in Visionline/Assa Abloy integrations work differently than other technologies. Click here for instructions on how to configure these in Lynx.
Functionality in the Lynx Portal
After integration is complete and locks are added to properties, Lynx can push a "virtual key" to the server for each guest as stays are booked. However, this system works differently than Wi-Fi or Z-Wave smart locks:
- Stays sync strictly via PMS: You cannot add a stay manually.
-
Unique Status Icons: You can view reservations under the "Stays" tab in a property listing as usual, but controls and status icons will reflect the App ecosystem. Key creation icons include:
- Cloud: Indicates the stay/key request has been sent to the Assa Abloy server (NOT your on-premise Visionline server yet).
- Guest downloaded app: Indicates the guest has downloaded the app, triggering key creation on your local server.
- Key created: Indicates the guest's key is generated on your Visionline server and ready to be synced to their phone.
- Key downloaded to app: Indicates the guest's key is active and ready to unlock the door.
- Revoke Access Tool: The "Stays" tab provides a button to revoke a guest's access key. This is highly useful if a guest loses their phone and will log the guest out of the mobile app immediately.
- Strict Access Scheduling: Check-in/check-out dates and times cannot be updated manually in Lynx after syncing from your PMS. Access Buffer settings do not affect access times on the reservation level; however, you can set up an account-level access buffer. Lock access strictly functions between the check-in and check-out schedule.
- Reservation Modifications: The latest key details are pushed to the Guest Portal through notifications. However, for Assa Abloy, reservation modifications made before check-in are not automatically synchronized to the digital key. Validation of these modifications typically requires post-check-in updates.
Functionality in the Lynx Guest App
Instead of a numerical code, guests use a mobile application to receive their key and unlock the door.
Device Compatibility: Android users require a minimum OS of Android 9 (Pie), and the application is supported up to Android 16 (Baklava). The current Assa Abloy Mobile SDK version supported is V9.0.4.- App Download Link: The primary guest automatically receives the app download link via Email or SMS. These communications are driven by your property's configured Lynx automation rules.
- Bluetooth Requirement: Guests must ensure Bluetooth is active on their device.
- 2-Factor Authentication (2FA): Guests pre-check-in using their phone number or email address, receiving a 2FA code via SMS or email. Assa Abloy requires 2FA; it cannot be disabled in Lynx.
- Auto-Lock Functionality: The app unlocks the door, but manual locking via the app is not an option as these locks support auto-lock functionality.
-
Seamless Multi-Room Access: Guests booking multiple rooms for the same stay use one app login and a single key to unlock all doors. The key will unlock whichever door is closest to the guest's phone.
- Note: Each room booking must have access start and end times that exactly match.
- Guests can tap the "i" (Information) button in the app to easily view their accessible doors list.
- Early Check-in Doors: Guests can be granted access to designated Early Check-in doors, allowing them to enter specific common areas even if their primary room is not yet ready.
-
Share Virtual Key: The primary guest can share a link allowing secondary guests to claim a virtual key without disrupting primary access.
- Lynx emails the secondary guest a download link and instructions (you can customize/white-label this email).
- Secondary guests gain access to the same locks as the primary guest.
- The primary guest can set time restrictions for secondary keys (must fall within the primary's access window).
- Auto-Logout: Guests are automatically logged out after their stay concludes.
Troubleshooting & Fallbacks
If an Assa Abloy key status gets stuck on an icon (e.g., stuck on the Cloud icon for 10+ minutes), please follow these troubleshooting steps:
- Verify that the Visionline server is online and running.
- Confirm that the server has an active internet connection.
- Ensure there are no network interruptions or firewall restrictions blocking connectivity.
- If the issue persists despite the server being online and connected, contact Customer Support for further assistance.
Fallback Access Method: If the guest's phone dies, is lost, or Bluetooth fails, a physical key card serves as the fallback access method. The front desk can issue the key card for the duration of the guest's stay. The card should be programmed with the guest's check-in and check-out dates, automatically expiring after the check-out time to ensure secure access.
| Learn/Read Understanding: Assa Abloy Common-Lock Functionality here. |
Comments
0 comments
Article is closed for comments.