Skip to main content

ZKTeco Integration

The integration with ZKTeco devices enables the use of facial recognition equipment in ACCELERO access control.

Licensing Requirement

This feature requires the ZKTeco module enabled in the license. See Licensing.

Overview​

The ZKTeco integration offers:

FeatureDescription
Facial RecognitionAutomatic synchronization of facial templates to ZKTeco devices
Automatic RemovalAutomatic deletion of visitor templates after exit
Communication StatusReal-time monitoring of communication with devices
Architecture

The integration is done through an ACCELERO/ZKTECO communication gateway (IONGRADE product). The gateway bridges the ACCELERO servers and the ZKTeco devices.

Navigation path: Settings > ZKTeco

Homologated models

The list of approved models, the integration mode of each one (Direct Γ— Neon Controller) and the minimum firmware live in a single place, the Homologated Equipment matrix. It is the official source; a model that is not listed there has not been approved.


Architecture and Requirements​

The integration with ZKTeco devices uses:

  1. ACCELERO/ZKTECO Gateway (IONGRADE product)
  2. ZKTeco Devices for facial recognition
  3. ACCELERO Server with the module enabled

Data flow:

ACCELERO β†’ Gateway β†’ ZKTeco Devices
← Status ←
Supported Types

Currently, only the "Facial" function is available in the ZKTeco integration.


General Settings​

Path: Settings > ZKTeco, Settings tab

Main Parameters​

FieldDescription
Categories that must have facial recognitionDefines which categories will have facial templates generated and distributed.
Example: disable for temporary visitors
Automatically remove templates for the following categoriesCategories whose templates are automatically deleted after passing through controllers with "Automatic visitor removal"
Except if the person has at least one of the following categoriesException categories: people with these categories will never have their templates removed automatically
Device Memory

Automatic template removal is essential to avoid fully occupying the memory of the ZKTeco devices, especially in systems with high visitor traffic.

How to set up the categories: after registering the gateway and devices, go to Settings > ZKTeco and open the Settings tab. Define, according to the client's needs, which categories use facial recognition and which undergo automatic template removal.

Category setup for the ZKTeco integration

Communication Status​

The Gateways tab shows, in the General data column, the data reported by each gateway, including:

  • Communication status with the gateway
  • Communication status with each ZKTeco device individually

This view allows you to quickly identify connection problems.

Proactive Monitoring

Periodically check the communication status to identify and resolve problems before they affect the operation.


Registering Gateways​

The gateway is the concentrator of the integration: it receives the registrations from the ACCELERO server and distributes them to all the facial readers pointed to it. Always start with the gateway configuration, since it is the one that manages the devices.

Physical prerequisites for the gateway

Before registering, make sure the gateway is connected to the internet network and to the power supply.

For the ZKTeco integration, it is mandatory to fix the gateway IP (static IP). Without this, the communication of the devices does not occur correctly.

Step by step:

  1. Go to the Settings > ZKTeco menu and select the Gateways tab.
  2. Click the option to add a new gateway.
  3. Fill in the fields below and save.
FieldDescription
Serial numberSerial number of the gateway, available on the label of the physical equipment.
CRITICAL: The information must be correct or communication will fail
DescriptionName/description of the gateway, at the client's choice

Adding a ZKTeco gateway


Registering Devices​

With the gateway configured, register the facial readers.

Step by step:

  1. Go to the Settings > ZKTeco menu and open the Facial tab.
  2. Click the option to add a new device.
  3. Fill in the fields below and save.
FieldDescription
Type (on the edit screen, Model)Currently, only the "Facial" function is available
DescriptionName/location of the device
Serial numberSerial number of the equipment.
⚠️ CRITICAL: Used as the "key" to recognize the equipment
GatewayGateway configured in the previous step, to which the device is subordinate
ActiveIf disabled, the device will not receive registration/deletion commands

Adding a ZKTeco facial device

No IP per device

Unlike Hikvision/Beward, the ZKTeco facial reader is identified only by the serial number β€” there are no IP, port, or credential fields in the device registration. The static IP is configured on the gateway, not on the reader.

Checking the physical connections

Always check the physical connections of the equipment β€” power, network, and the Wiegand connections on the desired controller β€” before putting the reader into operation.

Critical Serial Number

The "Serial number" field is of extreme importance because it is used as the key to identify the equipment.

Make sure that:

  • The serial number is correct
  • It matches the physical serial number of the equipment
  • There are no duplicates in the system

Incorrect serial number = total communication failure.

Simplified Compared to Other Integrations

The ZKTeco integration is simpler than Hikvision/Dahua/Control iD:

  • No IP/port configuration per device
  • No user/password credentials
  • Identification based on serial number only

The gateway manages the communication with the devices automatically.

Once added, the device can be edited with the Edit button in the list. The Edit ZKTeco device screen shows all the record fields: Description, Active, Model, Serial number, and Gateway.

Edit ZKTeco device screen with Description, Active, Model, Serial number, and Gateway


How Synchronization Works​

Automatic Synchronization​

After the settings, synchronization happens automatically:

  1. When saving a person's registration:

    • The system checks whether the person has a category configured for facial recognition
    • If so, it generates a template from the first photo of the registration
    • It distributes the template to all active devices
  2. Visual indicators on the photo:

    • πŸ”΄ Red icon: Templates not yet fully distributed
    • πŸ”΅πŸ”΅ Two blue icons: Templates distributed successfully
Photo Quality

The first photo of the registration is always used for synchronization. Make sure:

  • βœ“ Good capture quality
  • βœ“ Good lighting
  • βœ“ Frontal framing of the person
  • βœ“ Neutral background (if possible)

Manual Synchronization (Resend)​

Path: Settings > ZKTeco, Synchronize templates tab

When to use:

  • Replacing a device in the field
  • Restoring after a severe failure
  • Bulk update of all templates

How to do it:

  1. Go to the Synchronize templates tab
  2. Select the desired devices in the ZKTeco field
  3. Click Resend templates and confirm
  4. Wait for completion (it can take considerable time)

ZKTeco Synchronize templates tab with one device selected and the synchronization buttons

ButtonFunction
Test template sendingCounts how many templates would be sent, without sending them
Resend templatesResends all templates to the selected devices (asks for captcha confirmation)
Cancel synchronizationCancels the synchronizations in progress
Delete allDeletes all templates from the selected devices. Irreversible action
Processing Time

The send time depends on the number of photos. For large systems (thousands of people), the process can take hours.

During the process:

  • Do not turn off the ACCELERO server
  • Do not restart the gateway
  • Monitor the communication status

Automatic Visitor Removal​

ACCELERO can automatically delete visitor templates after their exit.

When the deletion occurs:

  1. When passing through a barrier with the "Remove visitors" flag:

    • The system checks whether the person has a category from the "Automatically remove" list
    • If the conditions are met, it deletes the template from the devices
  2. When closing/deleting an event:

    • The same check above is performed
    • Templates are removed automatically

Configuration example:

Automatically remove: VISITORS, CONTRACTORS

Result:
- Visitor: template will be deleted after exit βœ“
- Employee: template kept (not on the list) βœ—
Automatic removal exceptions

As in the other facial integrations, the Settings tab has the Except if the person has at least one of the following categories filter: anyone with one of these categories never has their template removed automatically.

Memory Management

Automatic removal is essential to:

  • Avoid exhausting device memory
  • Keep only active registrations
  • Ensure facial recognition performance

Best Practices​

Planning​

  1. Define categories before configuring:

    • Which categories will have facial recognition?
    • Which categories will have automatic removal?
  2. Size the device memory:

    • Check the template capacity per device
    • Plan the automatic removal policy
    • Monitor memory usage
  3. Document serial numbers:

    • Note the serial numbers of all devices
    • Keep the list updated
    • It makes maintenance and replacement easier

Operation​

  1. Photo quality:

    • Train operators on the importance of the first photo
    • Use adequate lighting
    • Always frontal framing
    • Preferably a neutral background
  2. Monitor synchronization:

    • Check the status icons on the photos
    • Investigate synchronization failures quickly
    • Use Resend templates only when necessary
  3. Manage memory:

    • Enable automatic removal for visitors
    • Configure the correct categories
    • Monitor device memory usage
  4. Track communication status:

    • Regularly check the status on the Gateways tab
    • Identify offline devices
    • Resolve network problems promptly

Maintenance​

  1. Check communication status:

    • Gateway ↔ ACCELERO
    • Gateway ↔ Devices
    • Resolve network problems quickly
  2. Back up before changes:

    • Back up before reconfiguring gateways
    • Document configuration changes
    • Test after changes
  3. Device replacement:

    • Note the serial number of the new device
    • Update the registration in ACCELERO with the new serial number
    • Use Resend templates to synchronize
    • Test recognition after replacement
  4. Firmware updates:

    • Consult IONGRADE before updating ZKTeco firmware
    • Check compatibility
    • Test in a controlled environment first

Troubleshooting​

Templates do not synchronize​

Possible causes:

  • Gateway without communication with ACCELERO
  • Gateway without communication with the device
  • Device marked as inactive
  • Person without a category configured for facial recognition
  • Incorrect serial number

Solution:

  1. Check the communication status on the Gateways tab
  2. Confirm that the device is active
  3. Check whether the person has the correct category
  4. Confirm that the serial number is correct (most common cause!)
  5. Use Resend templates if necessary

Device appears offline​

Possible causes:

  • Network problem
  • Device powered off
  • Incorrect serial number in the registration
  • Gateway without communication with ACCELERO

Solution:

  1. Check whether the device is powered on and on the network
  2. Test a ping to the device IP
  3. Confirm the serial number in the registration vs the physical equipment
  4. Check the gateway status
  5. Restart the gateway if necessary

Full list send fails​

Possible causes:

  • Too many offline devices
  • Memory problems on the devices
  • Overloaded gateway

Solution:

  1. Check the status of all devices
  2. Fix offline devices before trying again
  3. Consider sending during low system usage hours
  4. Check the gateway logs

Device memory full​

Solution:

  1. Enable "Automatic template removal"
  2. Configure the correct categories
  3. Use Resend templates to clear and re-synchronize
  4. Perform manual cleanup via the ZKTeco interface (if available)
  5. Consider increasing memory capacity (hardware)

Facial recognition fails​

Possible causes:

  • Poor photo quality
  • Template not synchronized
  • Device memory full
  • Inadequate lighting at the location

Solution:

  1. Check the status icons on the person's photo
  2. Recapture the photo with better quality
  3. Check the device memory usage
  4. Improve lighting at the reading location
  5. Use Resend templates if necessary

Comparison with Other Integrations​

ZKTeco vs Hikvision/Dahua​

FeatureZKTecoHikvision/Dahua
Device configurationSerial number onlyIP, port, user, password
Template resendSeparate "Synchronize templates" tabSeparate "Synchronize templates" tab
Automatic removalList + exceptionsList + exceptions
Available typesFacial onlyFacial + LPR
Photo captureNot availableAvailable (Hikvision)
Complexity⭐ Low⭐⭐⭐ Medium
When to Choose ZKTeco
  • Advantages:

    • Simpler configuration
    • Fewer parameters to manage
    • Good cost-benefit ratio
  • Disadvantages:

    • Facial recognition only (no LPR)
    • No integrated photo capture
    • Fewer advanced features

Ideal for projects that need only basic facial recognition without additional complexity.


Next Steps​

  • Categories - Configure categories for facial recognition
  • People - Register photos for facial recognition
  • Controllers - Configure physical controllers
  • Licensing - Check available modules
  • Hikvision - Compare with other integrations
  • Control iD - Alternative with more features