Overview

Controller Continuity is a feature available on Red-series Controllers that allows a local version of the Person Database, Rules, and Auto Open Schedules to be stored on the Controller. This allows Access Control to be maintained for a configured time period when disconnected from the Cloud Node, before switching to Ecard operation. 

This provides operational flexibility, as you don't need a technician to go on-site immediately to resolve an issue. Also, if the cause of the communication disruption is known and accessible, the Controller can remain functional while the cause is resolved.

Quick Reference Guide

The following will continue to function while in Controller Continuity Mode:

• Access Rules
• Cards, PINs, or Bluetooth Credentials
• Auto Open Schedules 

NOTE: Any Access Rules or Auto Open schedules created after the Controller goes offline will not sync and will not function until the connection is restored. 

The following will not function while in Controller Continuity Mode:

• The following types of Person or Group Rules:
  • Elevator Rules
  • Event Rules 
  • Anti-Passback Rules 
• System Events
• Real-time Event Reports 
• Remote Commands through Doors and Devices, System Health, or Mobile Button Credentials (tap to open)
• Live Events 
• Firmware Updates 

NOTE: Once the Controller’s connection is restored, Event Data will populate in an Event Report

Time Validation and System Health

If the Controller is unable to validate the current time while offline, you can pre-configure who will be granted access.

• People with 24x7 Access
• Ignore Schedules
• Ecards Only

You can monitor the model, firmware revision, and the sync status of the Access database for each controller on the System Health page.

For more information regarding configuring Controller Continuity on a system, click here.

For more information about the System Health page and Controller Continuity, click here.