This section outlines the supported hardware, capacity and features in this integration.
Supported Hardware Components
ICT has only validated this integration with the Allegion hardware and versions listed below. It may be possible to use other Allegion models and firmware, but ICT cannot directly support them without a sample being supplied for testing.
Allegion AD Series Locks
|
Device |
Model |
Firmware Version |
|---|---|---|
|
Hardwired lock |
AD300/301 |
N/A |
|
Wireless lock |
AD400/401 |
N/A |
|
Panel Interface Module |
PIM400-485 |
N/A |
|
Handheld Device with Schlage Utility Software |
BM170 R2 |
6.6.3 |
Allegion ENGAGE Series Wireless Locks
|
Device |
Model |
Firmware Version |
|---|---|---|
|
Wireless lock |
LE Networked Wireless Lock |
3.8.6 |
|
NDE Networked Wireless Lock |
3.8.6 |
|
|
Gateway |
ENGAGE Gateway |
1.60.8 |
Supported Capacity
AD300 Series Hardwired Locks
- Maximum number of AD300 locks supported: 64
- Maximum number of AD300 locks supported per reader port: 32
AD400 Series Wireless Locks
- Maximum number of AD400 locks supported: 128
- Maximum number of AD400 locks supported per PIM400-485: 16
- Maximum number of PIM400-485 panel interface modules supported: 64
- Maximum number of PIM400-485 panel interface modules supported per reader port: 32
ENGAGE Series Wireless Locks
- Maximum number of LE/NDE locks supported: 128
- Maximum number of LE/NDE locks supported per ENGAGE gateway: 10
- Maximum number of ENGAGE gateways supported: 64
- Maximum number of ENGAGE gateways supported per reader port: 32
Door Functionality
The Allegion locks perform the reading and locking part of the integration, while Protege programming defines access control. The following Protege functionality is supported:
- Users, access levels and credential matching (card and/or PIN, custom credential types, custom formats)
- Granting or denying access based on doors, door groups and schedules
- Unlock on schedule, by area and by calendar action
- Holiday groups for schedules
- Pre-alarm, left open, forced open alerts
- Manual door commands (lock, unlock and lockdown commands)
Any programming features not explicitly listed here may not be supported by this integration. It is the installer's responsibility to validate that features work as expected before implementation.
Supported Allegion Functionality
The following Allegion features and functionality are supported by this integration.
Remote Lock / Unlock and Remote Lockdown
This functionality is supported via Protege manual door commands.
Because the REX function is mechanical, Allegion locks always allow exit even when the door is locked down. Super users can access locked down doors as normal.
Deadbolt Function
When the Allegion deadbolt is engaged no user will be granted access. This is a manual lock function that requires no Protege programming.
A Door Not Allowed event will be generated for each access attempt.
Inside Handle REX
Because REX is controlled mechanically rather than electronically it is always allowed for Allegion locks, including when in lockdown.
When the inside handle of an Allegion lock is turned, an Unlocked by REX event will be generated for that door.
Lock Schedules and Holidays
When a door unlock schedule becomes valid:
- The lock allows free access without a credential
- A Door Unlocked By Schedule event will be generated
- The door status will change to Unlocked by Schedule - Closed
When the door unlock schedule becomes invalid:
- The lock requires a credential for access
- A Door Locked By Schedule event will be generated
- The door status will change to Locked - Closed
Apartment Mode
When the lock is in apartment mode, the door can be toggled between locked and unlocked states by pressing the inside push button, actuating the deadbolt, or badging a card while the door is closed. Using the inside handle and opening the door will cause it to latch unlock.
Office Mode
The office mode lock function is not supported by this integration. Please ensure that this function is not selected during lock commissioning as it will result in unexpected behavior.
Privacy Mode
When the interior push button (IPB) is pressed on a lock with the privacy function configured, privacy mode is activated. Access to the door will be denied until privacy mode has been deactivated either by pressing the IPB or using the inside handle to open the door. Users with super rights can access doors in privacy mode.
Storeroom Mode
In storeroom mode, the door can be locked or latch unlocked by presenting a valid credential.
-
When a user is granted access the door status will change to Unlocked by User Latched - Closed. The door can now be opened without a credential.
- When a user is next granted access the door status will change to Locked - Closed
Door Left Open
When a door with an Allegion lock is left open:
- A Door Pre-Alarm event will be generated after the configured pre-alarm delay time
- The door status will change to Not Locked - Open Alert
- A Door Left Open event will be generated after the configured left open alarm time expires
- The Door Left Open trouble input status will change to open
When the door is closed the corresponding events will be generated and statuses updated accordingly.
Door Forced Open
When a door with an Allegion lock is forced open:
- There is a delay of 4 seconds. This ensures that the forced door is not a false alarm.
- A Door Forced Open event will be generated
- The door status will change to Not Locked - Forced Open
- The Door Forced Open trouble input status will change to open
When the door is closed the corresponding events will be generated and statuses updated accordingly.
Interior Cover Tamper - Lock Enclosure
When an Allegion lock enclosure is opened:
- A Reader Unit Tamper Alarm event will be generated
- The associated door's Reader Tamper trouble input status will change to open
When the enclosure is closed the events and status will be updated accordingly.
Interior Cover Tamper - PIM/GWE Enclosure
When an Allegion PIM or GWE enclosure is opened:
- A Reader Unit Tamper Alarm event will be generated
- The Reader Tamper trouble input of the first lock associated with the PIM/GWE will change to open. This is the lock with the lowest Configured Address.
When the enclosure is closed the events and status will be updated accordingly.
Gateway BLE Tamper
When somebody connects to an Allegion GWE Gateway using the ENGAGE app:
- A Reader Unit Tamper Alarm event will be generated
- The Reader Tamper trouble input of the first lock associated with the PIM/GWE will change to open. This is the lock with the lowest Configured Address.
Upon disconnection, the events and status will be updated accordingly.
Communication Loss
When an Allegion ENGAGE Series lock loses communication with the GWE:
- A Reader Unit RF Loss Alarm event will be generated
- The RF Loss trouble input status will change to open
When the lock regains communication with the GWE the events and status will be updated accordingly.
When an Allegion PIM, GWE or AD Series hardwired lock loses RS-485 connection with the reader port:
- The Reader 1/2 Tamper / Missing trouble input status will change to open
- An Allegion 485 Reader Offline event will be generated
When the device regains communication with the reader port:
- The Reader 1/2 Tamper / Missing trouble input status will change to closed
- An Allegion 485 Reader Online event will be generated
Power Loss
When an Allegion PIM or GWE loses power:
- An Allegion 485 Reader Offline event will be generated
- No door events will be generated (or cached) while the Allegion interface module is offline
When power is restored to the Allegion PIM or GWE:
- An Allegion 485 Reader Online event will be generated
- Door events will resume as normal
When the Protege controller loses power:
- No events will be generated (or cached) while the controller is offline
When power is restored to the Protege controller:
- An Allegion 485 Reader Online event will be generated
- Door events will resume as normal
Battery Status
The Allegion lock monitors its battery status and alerts the controller when it drops below a prescribed range.
When an Allegion lock's battery drops to 4.5V:
- A Reader Unit Battery Low Alarm event will be generated
- The Battery Low trouble input status will change to open
When an Allegion lock's battery drops to 4V:
- A Reader Unit Battery Critical Alarm event will be generated
- The Battery Critical trouble input status will change to open
When an Allegion lock's battery restores to 4.5V:
- A Reader Unit Battery Critical Restore event will be generated
- The Battery Critical trouble input status will change to closed
When an Allegion lock's battery restores to 6V:
- A Reader Unit Battery Low Restore event will be generated
- The Battery Low trouble input status will change to closed
Notes on Battery Status
For AD Series locks, the default heartbeat is 10 minutes and the Allegion algorithm requires 6 reads before confirmation of battery status. As a result, it may take up to 1 hour before low/critical battery events are generated and trouble input statuses are updated.
For ENGAGE Series locks, the default heartbeat is 2 hours and the Allegion algorithm requires 6 reads before confirmation of battery status. As a result, it may take up to 12 hours before low/critical battery events are generated and trouble input statuses are updated.
This behavior is by Allegion design, to preserve battery life and maintain lock access functionality.