Resources / Access Control Hardware Integration

Access control hardware integration.

Connect your platform to matching device firmware, or build a JavaScript application on supported DejaOS hardware. Compare models, development paths and the references to request.

Clear filters

Resources for your device

FCV5005

8-inch face authentication terminal

Two ways to connect your access-control platform.

Choose standard-device protocol integration when your platform needs to exchange commands and access events with an existing device application. Choose DejaOS when your team needs to develop the application running on supported hardware.

01 / Standard-device protocol

Connect your platform to device firmware.

Your SaaS, membership or visitor platform communicates with the selected device application through its matching protocol. MQTT references are available for specific device and firmware families; message formats and supported commands differ.

Your team develops
The host-side connection, access rules and event processing.
Confirm first
Public model, application firmware, protocol revision, credential flow and network conditions.
Device application
Keep the matching application where it meets the project requirements. Host integration does not by itself require a new on-device app.
Request a matching protocol ↗
02 / DejaOS device development

Build your device application in JavaScript.

Develop the interface and business logic on supported DejaOS hardware. Select the exact SDK target, firmware and available modules for your application, then validate on the evaluation device.

Your team develops
The on-device application, interface and connection to your services.
Confirm first
Supported model, SDK target, development firmware, required hardware modules and deployment process.
Device application
A development device can have no business application installed. A production device normally ships with an application preinstalled.
Discuss DejaOS development ↗

These routes can both connect to a customer platform. The difference is whether your team integrates with an existing device application or develops that application. Ethernet, RS485 or an available DejaOS module alone does not confirm a standard-firmware API.

Integration references for FCV5005.

Hardware interfaces, a published protocol reference and DejaOS support describe different things. Confirm the supplied firmware before selecting an approach. A manual is an installation or operating reference; it does not establish protocol compatibility.

Standard protocol evidence, development targets and documentation by model
ModelStandard-device protocolFirmware conditionDejaOS developmentManuals & next step
FCV5005 →Model / firmware match to confirm

Request the matching face-terminal protocol reference for the supplied application.

Confirm the protocol family and application firmware for this exact model. A DejaOS example does not establish the stock application protocol.

Supported development hardware

SDK target: VF105_V12

Confirm DejaOS firmware, SDK and required modules for the application.

The SDK target is an exact development identifier, not the public product name or a promise that one application works across every firmware. The linked official source is a fixed historical revision; confirm the current target and firmware before development. Official model-to-target reference (archived source) ↗

Plan one complete access-control exchange.

Use this sequence to describe the required integration, then confirm which steps are supported by the selected protocol and application. Local validation and online validation can have different responsibilities.

  1. Read the credential

    The configured reader or terminal captures a supported credential. Confirm the actual reader hardware and how the application delivers its event.

  2. Apply the access rule

    Your platform makes an access decision where online validation is enabled. Some firmware checks a local permission list first; do not assume every credential is sent online.

  3. Execute the decision

    The device application or connected controller carries out the permitted action. Confirm the physical output and the connected door or gate control sequence.

  4. Record the result

    Process the applicable response and access event. Distinguish a command acknowledgement from a confirmed physical outcome.

Evaluate DejaOS with the actual development target.

Start with the supported model and its exact SDK target, choose the application modules, then verify the interface, peripheral behaviour and service connection on real hardware. DejaOS development references describe an application runtime; they do not make the same capabilities available in every standard device application.

FC6820 / Reference application

HTTP Access

A published DejaOS application with NFC, PIN and QR access, a browser administration interface and an HTTP API. Its application API is a reference implementation, not a protocol promised for every FC6820 firmware.

Explore the HTTP Access reference ↗

FCV5005 / Reference application

Connected face locker

A published DejaOS reference separates on-device recognition and cabinet control from central management. The project still needs the integrator’s service deployment, configuration and hardware acceptance.

Explore the face-locker reference ↗

These are development examples, not claims about a customer deployment or the application preinstalled on an ordered device.

Prepare a project we can evaluate.

Use this checklist to connect your SaaS, membership or visitor workflow to the actual entrance. Include what is known and mark what still needs confirmation; the same model name does not establish an identical application or wiring configuration.

Model & configuration
FCV5005 and its selected hardware options, plus the connected lock, controller or gate model. If undecided, describe the required credentials and installation.
Firmware & application
The supplied firmware, device application and protocol revision, if known. For DejaOS development, include the exact SDK target and required modules.
Credential & permission flow
How credentials are issued, where membership or visitor permission is checked, what grants access, and which events your platform needs to record.
Door or gate control
The reader output, controller input, electrical interface and required action sequence. Include the available door-contact or gate feedback and the wiring reference.
Network failure & recovery
Required behaviour for local permission checks, lost connectivity, authorization timeouts, late responses and reconnection. These conditions need validation on the actual firmware.
Quantity & rollout
Evaluation units, planned device and entrance quantities, and whether the project is a new installation or an extension of an existing system.
Deployment market
The country or market and any project-specific requirements that the selected configuration must be checked against.
Site conditions
Indoor or outdoor placement, mounting and passage layout, power, cabling and network conditions. A diagram or measured installation photograph helps identify what to confirm.

Include these details in your inquiry message. Do not send passwords, access tokens or personal biometric records. We publish English capability summaries here. Full protocol references are provided by model and configuration so your team can work from the applicable version.

Documents for FCV5005.

Browse documents for FCV5005 →

Common questions for FCV5005.

What is the difference between standard-device integration and DejaOS development?

Standard-device integration connects your platform to the supplied device application. It exchanges commands and events through the matching protocol. DejaOS lets you write an on-device application in JavaScript.

DejaOS requires supported hardware and the modules available for that target. Confirm the exact model, application firmware and workflow before choosing either path.

Do we need to rewrite the device application to connect our platform?

Not necessarily. Keep the supplied device application if its matching protocol supports your workflow. Your platform can implement that protocol.

A custom interface or device behaviour may need application development. Consider DejaOS only on a confirmed supported configuration. Validate the workflow and firmware before deciding.

Can devices with the same model use different integration protocols?

Yes. Devices with the same model can use different application firmware, operating modes and hardware options. These affect the commands, events and interfaces available.

A network or serial port does not prove support for a protocol. Request the reference for your actual configuration. Check offline and timeout behaviour for that protocol family.

What should we provide to request integration documents?

Send the overseas model, device application and firmware version, if known. Describe your platform, connection method and credential-to-door workflow.

Include offline and timeout requirements, deployment market and expected quantity. If the model is undecided, start with the project requirements. Do not send passwords, access tokens or personal biometric data.

Can our existing SaaS or membership platform use Feocey access hardware?

Your platform can be evaluated with the selected device application and matching protocol. Describe how it issues credentials, checks membership or visitor permission, grants access and records events.

Agree on where each decision runs. Confirm the commands and events supported by the supplied firmware. A network connection or app pairing alone does not prove platform integration.

For a custom device interface or logic, review DejaOS only on a confirmed supported configuration.

What happens if the network is unavailable or an authorization request times out?

Behaviour depends on the device application, operating mode and protocol. Different models need not admit or reject users in the same way.

Check local permission rules, online validation, response timeout and late replies. Confirm whether events are stored and resent after reconnection.

Agree on the required behaviour. Test network loss, rejected credentials, late responses and recovery on the supplied firmware.

Does a successful command acknowledgement prove that the door opened?

No. A successful command acknowledgement does not by itself prove that the door moved or a person passed through. Interpret the response using its matching protocol reference.

Check the authorization decision, device response and control output separately. Confirm which door-contact or gate feedback signals the hardware and firmware expose. Test the complete sequence with the connected lock or gate.

How do we match a QR reader or face terminal to a turnstile?

Match the reader output to the gate controller input. Use the supplied wiring and protocol references.

Check power, electrical interface, contact behaviour or serial protocol, signal timing, direction and reset sequence. Agree on rejected credentials, sensor responses and emergency behaviour.

A matching connector or successful credential read does not prove compatibility. Commission the reader, controller and gate together.

Does Feocey provide API or MQTT documentation for our software?

Yes. With the standard access application, Feocey provides the full MQTT protocol documentation. It covers event reporting, remote permission push and face enrollment. Confirm the matching model and firmware revision before you build against it.

Feocey does not state a REST API for door-strike control. For output to a controller, Wiegand and RS485 are supported. Request the reference for your configuration through an integration inquiry.

Can we use third-party readers with Feocey controllers and terminals?

Usually yes, if the third-party reader supports a protocol that the Feocey device also supports. Confirm the reader protocol with Feocey before ordering. Feocey does not publish a list of tested third-party reader models, and a matching connector such as RS485 does not by itself prove compatibility.

OSDP is supported only on the reader or client side. Feocey does not offer an OSDP controller, so do not specify a Feocey device as the OSDP panel.

What programming languages can I use to develop apps on DejaOS?

The primary supported language is JavaScript. We also provide a native C/C++ SDK for low-level driver and performance-critical development.

What hardware peripherals can DejaOS expose to developers?

Face camera, NFC / RFID reader, relay, Wiegand, RS485, GPIO, screen, audio, speaker, microphone, ethernet, Wi-Fi and BLE are all exposed via APIs.

Is there an emulator or simulator for DejaOS development?

We provide a PC simulator for early application logic development. Hardware-related functions need real devices for testing.

Can DejaOS work without connecting to the Feocey cloud?

Yes. It can run fully offline or connect to your own private cloud or server, without mandatory dependency on our cloud service.

Browse questions & answers →
← All resources