I'm looking for a solution for integrating door access with pool lockers on a building and can't find one.

Is there such a solution? - I'd like to manage lockers at the pool/beach for customers, one reader for every 100 lockers. How can I achieve this?

if so what did you use.

My research shows that Windows requires a FIDO2/WebAuthncredential

I can not confirm if the Unifi card has this.

Really would like to be able to use the Unifi Card for Windows MFA login

so my users do not have to use 2 cards

i get the cloudkey with the acces software

doorhub and g4 door access

there a 3 users

one is admin on cloudkey

one is admin with an android cellphone

one is a user with an adroid cellphone

all function well

but an external doorbellbutton ist correct wired to the hub

and if someone push the button ist rings only if i have the cloudkey access software open in my browser

i want it that my android cellphone also rings if someone push the button

i don´t find a "caller manager" or something like this

where must i look?

thank you

I'm facing the same difficulties as many other customers with G6 entry + intercom at home. Ringing for 60 seconds at home sounds like madness. @UI-Team is there at least approved plans to add an option in settings to change the ring duration?

I found multiple similar posts, but all of them are closed. Does that mean that it will not be implemented?

The most popular post in the community about same problem is 2 years old, but there is still no solution

Here is the link on it https://community.ui.com/questions/Feature-Request-Intercom-Viewer-Shorter-Ring-time/a1590871-37d6-4cbf-acd3-309bc26360fb

The marked ones in the picture.

Is it possible to order them from Unifi? Or at least get the size of the screws.

We need to get some new ones when some gone missing.

Thanks for your help

Marty

I am designing an access control project for entrance and elevator control in a residential building. The planned equipment is:

UA-G3-SK-Gate (main entrance)

UA-G3-SK-Elevator (elevator control)

UniFi Access Intercom Viewer in each apartment

I would like to know whether the UA-G3-SK-Elevator supports calling the elevator from the Intercom Viewer. Specifically:

@UI-Team

Can a resident call the elevator to their own floor directly from the Intercom Viewer?

Thank you!

Hardware/configuration:

• UniFi Access Application: 4.3.12
• UA-G2 Reader firmware: 3.18.21
• Two separate UA-G2 Readers tested — identical behavior
• Genuine Ubiquiti UA-Cards

Existing authorized cards continue to unlock normally. Unauthorized cards are correctly rejected.

However, using:

Settings → Card Inventory → Add New → Add NFC Card → select UA-G2 → Continue

and presenting the card causes the reader to generate:

"An unauthorized user attempted to access [door] with an unknown NFC card..."

rather than registering the card.

Important diagnostic: The same card can be registered successfully using the Android UniFi Access application's NFC registration function. After registration via Android, the card works normally at the UA-G2.

Therefore the issue appears isolated to the Access application → UA-G2 reader NFC enrollment workflow, rather than the card, reader hardware, reader firmware, or access permissions.

Two UA-G2 readers running the same 3.18.21 firmware reproduce the problem.

For Ubiquiti Support - Support files have been uploaded. Time of failures ~ 7:28 am through 7:31 am (IT) room and (Server) room entry readers. Successful Android registration was ~8:40 am.

When a LPR camera detects a plate and shows up in Find Anything, there should be a quick action button to add this license plate to an existing account or create a new one. I often open 2 tabs, one to go into account settings and one to look at the license plate i want to add.

I am looking to replace an aging Brivo system with Unifi Access but I want to run something by the collective first. This is a larger property that will have three cloudkeys on site due to three separate internet connections coming in. My question is, can I run an instance of Access on each CloudKey and then use the same NFC fobs on all three locations?

For example:

Person living in Unit A gets one Fob. That one Fob will work at Pool A, Pool B, and an exit gate to a shopping area. All three locations will need to have their own CloudKey unfortunately due to the way the property is.

Thanks for any guidance on this one.

Thanks!

-Ben

I use a UniFi Gate Hub with a BFT Deimos BT A600 (standard version, not Ultra; HAMAL control board) and Home Assistant. Gate control works, but I’m trying to get License Plate Unlock working. The Gate Position input is currently unconnected. Access warns that, with manual gate closing, License Plate Unlock requires the sensor to report the gate as closed. The physical installation does not allow me to run an additional cable from the gate operator to the Gate Hub.

I’m considering two options:

1. Bridge the Gate Position input

Could I bridge the two terminals and select Open Active (NC) so the hub always considers the gate closed? Would this enable License Plate Unlock, and what side effects would it have?

The BFT appears to be connected through 60/61 (START), so I’m particularly concerned that repeated “open” commands could stop a moving gate or close an already open gate. Would using 60/62 (OPEN) help?

2. Relay-based position feedback over Wi-Fi

Could I read the existing BFT closed-limit-switch signal (41/42, SWC) through a suitable Wi-Fi input module, send its state to Home Assistant, and use a potential-free relay near the Gate Hub to reproduce the actual gate position at its input?

Has anyone implemented this with Shelly or similar devices, ideally without adding a separate gate sensor? Which hardware and electrically isolated interface would you recommend for reading the BFT signal without interfering with its end-stop circuit?

I’d appreciate any proven setups or wiring examples. Thanks!

Can I have my G6 Entry connected to my UDM pro on Port1. I can then have my Door Hub Mini connected to my UDM Pro on Port 2. As long as the G6 Entry and the Door Hub Mini are pared in Access then they can work together and the G6 Entry will appear in Access.

So there is NOT a need for the G6 Entry to by physically connect to the Door Hub Mini then to my UDM Pro. They can just be on the same network and system

I'm using the Gate Hub to control my garage as well the side door. The side door is equipped with a door sensor connected to the Gate Hub and the entrance is controlled by the G6 pro entry.

Basically, the setup works fine with one limitation. Even when the side door is recognized as open, the face id triggers continuously the door lock.

What settings do i need to change, that the door lock will not be triggered when the side door is open?

G6 pro entry firmware: 5.4.132

Door Hub firmware: 2.6.8.0

BR

Thomas

I’d like to suggest two usability improvements for the UniFi Endpoint mobile app, specifically for the camera/door Live View page.

Currently, when users open the camera view, the interface is mainly focused on video thumbnails/streams, while the actual door or gate control is separated from the video feed.

It would be very useful to add the following:

Add an “Unlock / Open” button directly on the corresponding camera stream.

For example, if a camera is associated with a UniFi Access door, gate, or driveway, the video tile could include an Unlock/Open button.

This would allow a resident to:

1. see who is at the entrance;

2. verify the situation visually;

3. immediately unlock the door or open the gate without leaving the Live View page.

4. Ideally, the button should respect the same Access permissions already assigned to the user in UniFi Access/Endpoint.

Open cameras directly in actual Live View instead of showing thumbnails/snapshots first.

When the user opens this page, the cameras should immediately start displaying the live stream, instead of initially showing static thumbnails or requiring additional interaction to get to the live feed.

For residential installations this would make Endpoint much more convenient as a video intercom / access control interface.

A typical workflow should be:

Open Endpoint → Live View starts immediately → see visitor/car → tap Unlock/Open directly on the camera tile.

This would remove unnecessary navigation and make the experience much closer to a dedicated intercom/access-control application.

I’ve attached a screenshot of the current Live View screen for reference.

It would also be great if admins could configure which door/gate action is associated with each camera, especially in installations where several cameras cover the same entrance or driveway.

Thanks!

Attachments:

• Screenshot_20260926_060103_UniFi Endpoint.jpg

On the intercom's idle screen, a visitor must first press the Directory button. Only then does the resident list appear, from which they can place a call. For buildings whose primary intended interaction is browsing

 the resident directory and calling, this extra tap is an unnecessary step and confuses first-time visitors, who often don't realize they must press the button first.

Requested behavior

 A setting (ideally per device, configurable in the UniFi Access app under the intercom's settings) to choose the default home screen:

 - Standard — current behavior (call/doorbell home screen with a Directory button), or

 - Directory first — the resident Directory list is shown directly as the idle/home screen.

 When "Directory first" is selected, returning to idle after a call should also land back on the Directory list.

Use case

 Multi-tenant residential entrance (resident directory is the main way visitors reach people). Showing the directory by default removes a step, reduces visitor confusion, and matches how classic building intercom

 directories work.

Suggested implementation (from firmware analysis)

 In the on-device app com.ubnt.fr.da.entry, the default/home screen is produced by createDefaultScreen (returns com.ubnt.fr.da.entry.ui.main.MainScreen). The Directory list is already implemented as

com.ubnt.fr.da.entry.ui.directory.DirectoryScreen (the same screen opened today from the Directory button in IntercomBottomButtons). A configuration flag that makes createDefaultScreen return DirectoryScreen when "Directory first" is enabled would achieve this cleanly, reusing existing screens. Exposing that flag as a device config key pushed from UniFi Access would make it configurable without any UI redesign.

This currently cannot be achieved by end users: there is no such setting in UniFi Access, and the default screen is hardcoded in the

signed firmware (Verified Boot / dm-verity + update_engine payload signing prevent user-side modification). So it needs to be an official, signed feature.

Should be an easy fix @UI-Team or at least let people upload their own patched firmware