Skip to main content

Beward Integration

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

Licensing Requirement

This feature requires the integration module enabled in the license. Check with IONGRADE for availability.

Overview​

The Beward integration offers:

FeatureDescription
Facial RecognitionAutomatic synchronization of facial templates to Beward 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/BEWARD communication gateway (IONGRADE product). The gateway bridges the ACCELERO servers and the Beward devices.

Navigation path: Advanced > System > Integrations - Beward

Homologated models​

TypeModelIntegration mode
FacialFR 1017 (4.3"), FR 1025 (5"), FS 1002 (5")Neon Controller

Explanation of the modes (Direct × Neon Controller) and the complete matrix in Homologated Equipment.

Architecture and Requirements​

The integration with Beward devices uses:

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

Data flow:

ACCELERO → Gateway → Beward Devices
        ← Status ←

General Settings​

Path: Advanced > System > Integrations - Beward > Settings

Main Parameters​

FieldDescription
TypeBeward device model
Categories that must have facial recognitionDefines which categories will have facial templates generated and distributed
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 Beward devices, especially in systems with high visitor traffic.

How to set up the categories: after registering the gateway and devices, go to Advanced > System and navigate to the Integrations - Beward submenu. Define, according to the client's needs, which categories use facial recognition and which undergo automatic template removal.

Category setup for the Beward integration

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. Without this, communication will not be established.

Step by step:

  1. Go to the Settings > Beward menu and select the Gateways submenu.
  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 Beward gateway

Monitoring:

  • ACCELERO ↔ Gateway communication status
  • Gateway ↔ subordinate devices communication status

Registering Devices​

With the gateway configured, register the facial readers.

Step by step:

  1. Go to the Settings > Beward menu and open the Devices submenu.
  2. Click the option to add a new device.
  3. Fill in the fields below and save.
FieldDescription
DescriptionName/location of the equipment
IP addressIP of the facial reader on the network
Communication portTCP port for communication. By default, 80
UserAuthentication user on the device. The Beward factory default is admin; adjust if it was changed on the equipment
PasswordAuthentication password. The factory default is admin; adjust if it was changed on the equipment
GatewayGateway configured in the previous step, to which the device is subordinate
Device IDDevice ID of the equipment, available on the configuration screen of the Beward reader itself (see FAQ)
ActiveIf disabled, the device will not receive registration/deletion commands
Synchronize only these categoriesAdditional filter of categories (in addition to the global filter)

Adding a Beward facial device

Critical Device ID

The "Device ID" field is specific to the Beward integration and is essential for correct operation.

How to obtain it:

  • Access the web interface of the Beward device
  • Navigate to the device settings
  • Locate the "Device ID"
  • Note it down and configure it in ACCELERO

Incorrect Device ID = total communication failure with the device.

Double Category Filter

The category filter works on two levels:

  1. Global (Settings): Defines allowed categories in the system
  2. Per device: Further filters which categories go to that specific device

Only categories that pass both filters will be synchronized.

TODO: Add Screenshot

Include a screenshot of the device registration screen showing all fields, especially Device ID.

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: Advanced > System > Integrations - Beward > Synchronize templates

When to use:

  • Replacing a device in the field
  • Restoring after a failure
  • Bulk update

How to do it:

  1. Select the desired devices
  2. Click Resend templates
  3. Wait for completion (it can take considerable time)
Processing Time

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

TODO: Add Screenshot

Include a screenshot of the template synchronization screen showing device selection and the resend button.

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
    • It checks whether the person does NOT have a category from the "Except if..." 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
Except if the person has: EMPLOYEES, RESIDENTS

Result:
- Pure visitor: template will be deleted after exit ✓
- Visitor who is also an employee: template kept ✗
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?
    • Which categories will be exceptions?

  2. Size the device memory:

    • Check the template capacity per device
    • Plan the automatic removal policy
    • Monitor memory usage

  3. Document Device IDs:

    • Note the Device ID 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 only when necessary

  3. Manage memory:

    • Enable automatic removal for visitors
    • Configure exception categories correctly
    • Monitor device memory usage

  4. Track communication status:

    • Regularly check the status on the gateways screen
    • 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 Device ID of the new device
    • Update the registration in ACCELERO with the new Device ID
    • Use template resend to synchronize
    • Test recognition after replacement

  4. Firmware updates:

    • Consult IONGRADE before updating Beward 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 Device ID
  • Network/credential problems

Solution:

  1. Check the communication status on the gateways screen
  2. Confirm that the device is active
  3. Check whether the person has the correct category
  4. Confirm that the Device ID is correct (access the Beward interface)
  5. Test the access credentials to the device
  6. Use manual resend if necessary

Device appears offline​

Possible causes:

  • Network problem
  • Device powered off
  • Incorrect Device ID 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 Device ID in the registration vs the physical equipment
  4. Check the credentials (user/password)
  5. Check the gateway status
  6. Restart the gateway if necessary

Template resend 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. Configure exceptions appropriately
  4. Use resend to clear and re-synchronize
  5. Perform manual cleanup via the Beward interface (if available)
  6. 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 template resend if necessary

Comparison with Other Facial Integrations​

Beward vs Hikvision/Dahua/ZKTeco​

FeatureBewardHikvision/DahuaZKTecoControl iD
Device configurationIP + Device IDIP + port + credentialsSerial number onlyIP + port + many fields
Specific Device ID✓ Yes✗ No✗ No✗ No
Template resendSeparate tabSeparate tabSingle buttonSeparate tab
Automatic removalList + exceptionsList + exceptionsList onlyList + exceptions
Complexity⭐⭐ Medium-Low⭐⭐⭐ Medium⭐ Low⭐⭐⭐⭐ High
When to Choose Beward

  • Advantages:

    • Relatively simple configuration
    • Device ID allows precise identification
    • Good cost-benefit ratio

  • Disadvantages:

    • Less common in the market than Hikvision/Dahua
    • Device ID adds a configuration layer

Ideal for projects that already use Beward equipment or when specified by the project.

FAQ​

Where to find the Device ID of the facial reader?​

Access the facial reader via a network cable, using the default IP 192.168.2.10, and navigate to the System Info and IP Address tab. The Device ID is displayed on this screen.

System Info and IP Address screen of the Beward reader

What is the equipment's Wiegand reading protocol?​

On the B2002fr model, the Wiegand Mifare 34 protocol is used. For other models, confirm the correct protocol with the manufacturer.

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.

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 facial integrations
  • Dahua - Similar alternative
  • ZKTeco - Simpler alternative