The Allegion IP Gateway allows you to send immediate updates to your locks following any database change. This eliminates the need to physically go to the locks to update them with new cardholder information. As well as immediate system updating, you can also use the device to immediately unlock any door from any PC that is connected to the internet and to retrieve audit information from the locks.
Note: The Allegion Gateway and all Allegion devices should be connected to a 2.4GHZ Wi-Fi network. They are not compatible with a 5GHz network.
To clear any possible configuration that may be programmed into the Gateway, you should first perform a factory reset. A Factory Default Reset (FDR) will return the ALLEGION Gateway settings to the original settings as shipped from the factory. If you have been using the Gateway on a different site you will also need to log in to that site and delete it - so it can then be recommissioned to a new site:
Status LED | Meaning | Type of LED User Interface |
Solid amber | Gateway is booting up | State |
Long flash amber, repeating | Gateway Wi-Fi access point is active | State |
Fast flash x2, repeating for 1 minute | Factory default reset did not complete successful | Status Code |
Fast flash x3, repeating for 1 minute | Power on self test failure | Status Code |
Solid blue | Gateway is commissioned, normal operation | State |
Long flashing blue | Mobile application is connected to Gateway | State |
Fast flash blue, repeating | Gateway is in link mode - connected and linking to new lock | State |
Alternating long flashing blue and red | Gateway is in link mode - searching for new lock | State |
Solid red | Factory Default State / Uncommissioned | State |
Fast flash red x4 | Linking to lock was not a success | Status Code |
Alternating green and red long flashes, repeat | Gateway firmware is updated | State |
Solid green | Gateway is in process of resetting to default settings | State |
Fast flash green x2 | Gateway will begin a factory default reset | Response to User Action |
Fast flash green x3 | Linking to lock was a success FW upgrade succeeded | State |
IMPORTANT: These steps must be followed exactly. If the device is not setup correctly you will need to delete it, factory reset it and begin the setup process again from the start.
The first step when setting up the Gateway is to capture it to your site using the ALLEGION ENGAGE app.
Now that the device has been added to your ENGAGE account you can now add it to your registered site in the Web Portal:
Note: For detailed instructions about setting up a new site and registering it to the web portal, refer to the Allegion No Tour - Full Reference Guide (P/N: 02321-001)
or you can view the knowledge base article here: Allegion - No Tour Full Reference
Paste the following URL into your browser: (http://www.keri-kb.com/#Allegion_NO_TOUR/Allegion_No_Tour.htm)
To check the gateway is online, click the device name and the device status screen will appear. The status should be showing as 'Online'. You will also see firmware details and the time of the last connection.
The following steps explain how to pair your locks with the gateway. Once locks have been paired to the Gateway you will be able to update the locks via the Web Portal. Locks can be paired to the gateway using the Allegion ENGAGE app or from the Keri Web Portal. The following steps explain how to pair the locks using the web portal.
Notes:
If no locks are linked, you can click the + icon, and the gateway will scan for locks that are in range and not already linked. Select the lock(s) you want to link from there.
Certain database changes will require a 'door file update', for example, changes to access rights or removing access rights from a cardholder. The following steps explain how to update the locks via the Gateway:
Part of the initial setup is to synchronize the clock on the locks (this is a separate action to updating the locks:
The audit data are the events that are generated by the locks; access granted, access denied, door opened, door closed, etc and these are stored in the locks memory until they are retrieving using the Mobile app or the Web Portal (using the IP Gateway) or the NDE and LE can be configured to send their event information automatically. In order to provide privacy there is the option (per gateway), to select whether or not to automatically upload audits or not (the Edge devices selection). So if the building owner was concerned about privacy issues, they could put all the Control locks on gateways that have the selection to manual and the NDE/LE on gateways that are uploading in real-time.
The daily event collection option is a balance between the two...So the building owner is not seeing events inreal time but does not have to manually get audits.
When set to manual, all the event download options are off. The following steps explains how to manually retrieve all the events from a lock:
Notes:
- Control BE467 and FE410 locks will hold 1,000 events in memory.
- NDE and LE locks will hold 2,000 events in memory
You can configure the system to download all the lock event information once a day from each of the locks..
You can subscribe to events and this will automatically download all events as they happen (in real time). This settings is enabled on the gateway settings screen via the Manage drop-down list >> Edit >> Download Audits Daily).
When a lock is paired with an IP Gateway it is very easy to do a status check on the lock. The status check will allow you to retrieve information such as: whether the lock is locked or unlocked, the battery status, door position, deadbolt position, if the tamper lid is open or if the real-time clock is incorrect:
Note: If a lock is paired with an IP Gateway you MUST ensure the IP Gateway is online when the lock is deleted. Failing to do so will mean the lock will not be correctly deleted from the Allegion database and the lock will still be listed in the ENGAGE app as a linked device. The lock will also be listed in the firmware details page. If a lock is accidentally deleted while the gateway is offline you will need to connect to the gateway with the ENGAGE app, select Linked Devices, select the lock and remove it from linked list (swipe left in iOS).
To remove a lock:
When using the Allegion Gateway in IP mode you can perform a temp unlock on doors via the web portal.
There is a Lockdown devices broadcast message that can be sent to all NDE and LE locks on the system (when you are using the Allegion Gateway). When actioned, this will immediately lockdown all locks that support this feature - all locks will be put into 'frozen secure' mode and will only allow access for credentials of 'passage type'. Any doors which are unlocked or auto-unlocked will be immediately locked.
To take the locks out of 'Lockdown' mode you can either present a Freeze credential or you can use the Manage drop-down list again and select Commands >> Clear Lockdown - when a Freeze credential is presented the reader LED will alternatively blink red/green/red/green for a few seconds. A few seconds later the padlock will then not be displayed next to the lock.
You can update the IP Gateway firmware by doing the following:
Note: This will take a few minutes to update the Gateway and also allow 10-15 minutes to update the firmware on each connected lock.
You can upgrade firmware from the ENGAGE app or from the web portal. If the lock requires a new firmware version you will see an icon next to the lock, as highlighted:
The following steps explain how to upgrade the firmware on the locks. The firmware file is sent via the gateway over Bluetooth - but in the ENGAGE app you can configure the lock to communicate over Wi-Fi and then the update will be much quicker.