Technology & smart home · 4 min read
The Intercom Call Works, but the Gate Will Not Open
Visitor calling and gate release use different paths; test each stage before replacing the whole system.
YKCA Journal · Sources reviewed October 4, 2026
Explore the guideCompare three conditions: call works but no release; old control also fails; app says command sent. Each requires its own verification.
Intercoms & gates service ↗All service guides ↗
The key decision
Verify release authorization, the output type and the operator or lock interface separately from the call. A dry relay switches a circuit; it does not supply lock power, and an app confirmation does not prove gate movement.
A successful conversation proves only part of the chain
Video and speech can work while the gate-release path fails. Start by identifying whether the command controls a motorized operator, an electric gate lock or both; their interfaces are not interchangeable.
A Reddit installer reported a working Hikvision call and video, an audible output click, and no expected 12-volt power for a gate lock. This directly illustrates confusion between a switched contact and a powered output. The forum wiring suggestions are not adopted as instructions for another device.
Identify the exact station, controller, gate operator, existing approved controls, and intended release behavior. A contact output labeled relay is not a universal invitation to connect it to any operator terminal.
Source: Help with Gate Release: call and video work, relay heard but lock not powered
A dry contact and a powered output do different jobs
A dry relay opens or closes a contact without supplying the controlled load’s power. A powered output supplies a specified voltage/current as well as switching. Ubiquiti’s documentation distinguishes these outputs, and its Gate Hub specifications list dry gate-operator outputs. Those facts explain why an audible click alone does not establish usable lock power.
NO means normally open, NC means normally closed and COM is the relay’s common terminal. The installer must match the intended contact behavior, voltage/current limits and approved external supply where required. Do not apply voltage to a contact-only operator input or copy terminal connections from a different model.
Source: Ubiquiti: Access Hub input and output terminals · Ubiquiti: choosing an Access Control Hub, Gate Hub dry outputs
Check the command and its duration
Have the qualified installer compare the supported operator input with the intercom’s output behavior. A momentary pulse, a maintained hold and a dedicated open command are different. A cycle or step input may change state on successive requests rather than always opening. Verify the selected operator manual; repeated test clicks can create unintended movement.
For an electric side-gate lock, verify the supported unlock duration and lock power. Ubiquiti documents model-specific trigger-duration controls, including the Gate Hub side-door output; that setting should not be mistaken for a universal motorized-gate timing rule. Keep safety circuits and the approved closing sequence intact during testing.
Source: Ubiquiti: configuring Access Control Hub terminals · Ubiquiti Gate Hub: supported gate input and closing modes
Illustrative scenario: calls arrive after a retrofit
Imagine a new entry station calls both residents successfully, but neither can release the gate. The existing approved local control still operates it normally. That points toward the new command/interface path and configuration, while preserving the possibility of intermittent gate issues.
The technician should document the observed command and operator response, then correct the supported interface. If the old control also fails, gate diagnosis becomes a separate priority. Replacing the intercom would not necessarily address that failure.
Acceptance includes confirmation after movement
Test authorized release, the intended pulse or command behavior, gate opening, and the approved closing sequence. If the app displays gate status, verify what sensor actually supplies it. A sent command is not proof that the gate is physically open or closed.
Record which contractor owns the intercom, network, power, operator, and mechanical work. A clear responsibility boundary prevents the owner from being passed between vendors while an unresolved release path remains.
Put it into practice
A decision table to keep handy
| Observed condition | What it distinguishes | Evidence or next action |
|---|---|---|
| Call works, no release | Command/interface path can fail separately | Record models and the exact release action |
| Old control also fails | Gate/operator issue may be shared | Arrange operator diagnosis rather than app-only changes |
| App says command sent | Physical position remains unproved | Verify the status sensor and actual movement |
Bring this to the conversation
Your next-step checklist
Common questions
Why can I answer the intercom but not open the gate?
Calling and release are separate functions. The release command, interface, operator, or a safety condition may be responsible. Verify the approved command path and actual gate response through qualified service.
Check the original guidance
Sources & review date
Primary guidance and available source excerpts reviewed October 4, 2026. Requirements and program terms can change; verify the current instructions for your property and project before committing to work.
- Ubiquiti: Access Hub input and output terminals
- Ubiquiti: choosing an Access Control Hub, Gate Hub dry outputs · Search excerpt reviewed
- Ubiquiti: configuring Access Control Hub terminals
- Ubiquiti Gate Hub: supported gate input and closing modes
Reader discussions behind this guide
These discussions illustrate reader problems; they are not technical instructions or a measure of how common a problem is. The guidance above draws on the primary sources listed here.
Continue with the next decision
Related guides
Ready to discuss work at your property?
Discuss this service with YKCA ↗