UniFi Access - FAQ

You can use a UA Card to unlock locations deployed only on the same UniFi Console. 

A UA Card stores one set of encrypted keys and tokens when it is assigned to the locations of the UniFi Access application deployed on a UniFi Console. Because each console comes with a different key, a UA Card assigned to one console cannot be used to unlock the locations deployed on another console. 

When a user attempts to unlock a location by holding their UA Card to a reader, the reader's key reads the UA Card's token, and then encrypts and transfers the token to the Access Control Hub to verify the location unlock request.

Note: Identity Enterprise Door Access does not have such a limitation because the encrypted key of a deployed reader is generated on the workspace level. This means you can use the same UA Card to unlock locations deployed on different sites of your Identity Enterprise Workspace.

• Access Hub (UA Hub): Support a single location.
• Door Hub (UA-Hub-Door): Support a single location.
• Enterprise Access Hub (EAH-8): Support up to 8 locations.
• Elevator Hub (UA Elevator): Support up to 18 floors and digital inputs for car status and emergency.
• Gate Hub (UA Hub Gate): Support up to two driveways and one pedestrian door.
• Access Ultra (UA Ultra): Support a single location.

The number of PoE ports determines the number of readers and cameras that can be connected to the hub. While the Access application itself does not limit the number of readers and cameras, it's recommended to stay within the PoE port count for optimal performance.

How Do I Set Up an EAH-8 with 8 Doors, Each with Two Readers, If There Are Only 8 PoE Ports?

UniFi Access supports electric strikes, electric bolts, and magnetic locks with dry and powered (12v, up to 1A) relays. Integration with locks from external vendors is also supported, but ensure they support 12V powered relays (up to 1A) or use a dry relay with an external power supply.

We recommend using UniFi Access' Magnetic Lock (UA-Lock-Magnetic-270kg and UA-Lock-Magnetic-540kg) and Electric Lock (UA-Lock-Electric) as they have been vetted. Some lower-quality third-party locks have been known to struggle at longer distances. 

UniFi Access Readers must be directly connected to UniFi Access Control Hubs. The direct hub-to-reader connection:

• Utilizes proprietary communication to provide a robust defense against potential hacking risks.
• Plays a pivotal role in maintaining uninterrupted functionality during console outages or network disruptions. Even in adverse conditions, the UnFi Access Reader remains operational, contributing to a reliable and resilient access control solution.

See Unlocking Reliability: Security with UniFi Access for details.

UniFi Access supports both manual and hard-wired emergency mode (Lockdown and Evacuation) activation. 

• Lockdown: Lock one or all locations immediately.
• Evacuation: Unlock one or all locations immediately.

Admins can activate emergency mode on Access web-based applications, and iOS and Android apps. By connecting a fire panel to an Access Control Hub, admins can configure a default emergency mode, which will be automatically activated when a fire signal is sent from the file panel.

See Activating Emergency Lockdown or Evacuation for details.

Yes. UniFi Access can remain operational during a power outage. This requires a battery-back power supply, such as a Switch Mission Critical or a UPS on your switches. Note that access rights are synchronized with the Access Control Hub, so if a UniFi Console goes down, door access will remain. Alternatively, you can manually configure locks as fail-safe or fail-secure, allowing them to be locked or unlocked, respectively, during a power outage.

Backup power for the Enterprise Access Hub (EAH-8) can be provided by connecting a 36V lead-acid battery to its 32-48V DC power supply. The battery should have a capacity of at least 10Ah. At full load, the maximum power consumption is 240W, with a current draw of 7.5A at 32V and 6.67A at 36V.

What to Do If Access Devices Are Connected but Not Found by the Access Application?

If your UniFi Access devices are connected to the Access Control Hub but are not detected by the Access application, follow these troubleshooting steps:

1. Ensure you are the UniFi Console Owner or a Super Admin.
2. Ensure the UniFi Access devices are installed correctly, connected properly, and powered on.
3. Ensure the status LED on your Access devices is steady white.
4. Ensure that the Access devices are on the same physical network as the UniFi Console running the Access application.
5. On your Access application, do either of the following:
   • For device adoption issues during the initial setup, click Manage Network to confirm that your Access devices are on the same network as your Access application, then click Retry.
   • For device adoption issues after completing the initial setup, go to Settings > Advanced > Network and confirm that your Access devices are on the same network as your Access application.
6. If the above steps do not resolve the issue, manually reset your Access devices by pressing and holding the RESET button with a pin until the LED blinks white. The devices will be ready for adoption after 2–3 minutes.

What Is the Access System Log Storage Limit in UniFi OS?

For UniFi OS 4.0

In UniFi OS 4.0, Access system logs are stored on an internal SSD with 3.5 GB of space. When this storage is full, the oldest logs are deleted automatically. This limit is typically only reached when system log retention is set to Never Delete Logs in UniFi OS > Settings > General > Advanced > System Log Retention.

If you set the log retention period to 30 Days, 90 Days, 180 Days, 1 Year, 2 Years, or 3 Years in System Log Retention > Custom, the oldest logs will be deleted once the specified retention period is reached.

For UniFi OS 4.1 and Later

Starting with UniFi OS 4.1, Access system logs are migrated to external storage if available. After migration, only the most recent three months of logs remain on internal storage, while logs older than three months are stored on external storage according to your settings in System Log Retention.

If Never Delete Logs is selected, logs will be stored on external storage until it reaches a 32 GB limit. If external storage is full, migration will not be possible, and logs will continue to be stored within the 3.5 GB limit of the internal storage.