Resources / FAQ

A clearer starting point.

Answers to common questions about product selection, device integration and development.

Clear filters

19 answers · Integration

Integration

Does registering a person automatically grant access?

Not necessarily. Identity enrollment and access permission are separate steps in many systems. Confirm that the person, credential, target device, schedule and permission group have been linked and that the authorization was delivered successfully.

Is a network connection the same as a connection to the management platform?

No. A device can have local network access without maintaining its platform or messaging connection. Check the physical network, IP settings and service connection separately, using the indicators or logs available for the selected system.

What should we check when a controller receives no reader data?

Compare the RS485 wiring, polarity, grounding and communication settings with the instructions for both devices. Then confirm the reader output mode and controller input configuration; a correct cable cannot compensate for mismatched communication settings.

Why might a successful credential check not open the door?

Identity verification, access permission and the physical control output are separate parts of the workflow. Have a qualified installer check the operating mode, permission result, relay timing, controller output and lock wiring against the installation instructions.

What should we check if a device appears online but commands fail?

Confirm the overseas model and device identifier registered in the platform, including letter case and similar-looking characters. Then check connection stability, the expected firmware and whether the command is intended for that operating mode.

Why might an unregistered card or code still activate the door?

The controller may be in a commissioning or test mode that bypasses the normal permission decision. Stop the test, verify the configured operating mode against the manual and repeat the check with a known authorized and unauthorized credential before putting the door into service.

What should we collect when a device repeatedly goes online and offline?

Check the cable or wireless signal, local network stability, power and service connection rather than looking only at the platform status. Record the times of each disconnect and include the device model, firmware and relevant network logs when asking for support.

What should we check when a remote command has no effect?

Check the service connection and device identifier first. Confirm the expected firmware and operating mode. If the command reaches the device but nothing moves, check the controller, relay and wiring against the installation reference.

Does FCS525 use Wiegand or OSDP?

FCS525 documents Wiegand 26/34 output. Feocey supports OSDP only on the reader or client side, not as an OSDP controller, and this site does not state OSDP support for FCS525 itself. Confirm with Feocey before specifying it for an OSDP installation.

OSDP is a communication standard for access-control panels and readers. A connector labelled RS485 identifies an electrical interface, not the protocol running on it, and Wiegand is not RS485. Match the Wiegand 26/34 format to the external controller, and have the integration path confirmed before choosing a controller and reader as a pair.

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.

← All resources