Integrator, developer

Driver manifest (for integrators)

How to connect a new series of readers via gateway provider without editing the EAS core.

1. 1

   Architecture

   The native driver of the new series is located in the gateway provider slot: the protocol is in a separate module, the EAS kernel is not rebuilt. See the EAS_NATIVE_DRIVER_PACKAGE documentation in your distribution.

2. 2

   Manifest provider

   The JSON manifest describes the provider id, version, Python dependencies, and entry point. The file is placed in the gateway/providers/ directory and registered during hub-update.

3. 3

   Site installation

   After publishing to hub, update from node or copy bundle. The install-eas-driver-module.sh script connects the module to eas-gateway-native.

4. 4

   Examination

   In the admin panel “access control → Controllers → master” the new type should appear in the list. Test controller - probe and the first event in the log.

   Tip: For ZKTeco C3, use the built-in native driver - no separate manifest is needed.