Recognition devices
Recognition devices are external hardware connected to Vittor. They capture images and compare faces on site. The system synchronizes person information to devices and receives heartbeats and recognition events for management and display.
Device connectivity, completed person synchronization, and correct recognition are three separate checks. Start with one device and one test person, then extend the verified configuration to other devices.
Prepare for integration
Ask the device supplier or implementation team to confirm the following information. Keep authentication details in the controlled site configuration record.
| Item | Information to confirm |
|---|---|
| Hardware and firmware | Model, firmware version, and supported protocol version |
| Device identifier | A unique SID in the system; different devices should not share an identifier |
| Network | Device and service addresses, required ports, and actual reachability in each direction |
| Synchronization | Server-initiated push or device-initiated change retrieval |
| Event destination | Direct upload to the central service or the display's local endpoint |
| Installation role | Building, device group, and entry or exit direction as applicable |
| Authentication | The account, password, or key required by that protocol |
Supported device models and firmware versions are not universally plug-and-play. Select and integrate devices using protocol comparison and on-site verification.
Configure and verify in order
1. Establish network access and heartbeats
Set the agreed upload destination and authentication on the device. Confirm that the receiving system sees a recent heartbeat and that its SID matches the physical device label. If no heartbeat arrives, check power, network, port, address, and protocol configuration first.
The Web System Configuration node list primarily discovers the central service, enrollment terminals, and display terminals. Determine external recognition-device connectivity from the protocol heartbeat on its actual receiving path.
2. Synchronize one test person
Prepare a test person with complete details and a photo in the central service. Confirm the association with the intended device or device group. After synchronization, locate the same person identifier on the device and check that the photo is usable.
Saving person information produces synchronization work. Completion depends on the queue, protocol, and device response. When a device has a heartbeat but lacks the person, inspect the task status and device response.
3. Complete real recognition
Have the synchronized person complete recognition on the device. Check the device result and the event received by the central service or display. The person, device identifier, and time should match.
For entry/exit or unreturned-resident statistics, also verify events in the relevant directions and their effect on person status. A photo appearing on the display alone does not prove that entry/exit statistics are correct.
4. Verify person changes
Update the test person's details or photo as required for acceptance, then verify the device-side result. If deletion synchronization is in scope, validate it with a dedicated test record rather than an active resident.
Acceptance checklist
| Check | Passing result |
|---|---|
| Heartbeats | The receiver continually sees recent heartbeats for the correct device |
| Person creation | The device contains the test person with matching identifier and photo |
| Person update | Updated information or photo takes effect on the device |
| Person deletion, when in scope | The test deletion completes and the device result is verified |
| Recognition upload | The receiver contains the event from the current test |
| Display | The selected mode shows the same person, device, and time |
| Entry/exit status, when in scope | Direction and management-side person status follow the site rules |
Common issues
| Symptom | Check in this order |
|---|---|
| Device never becomes online | Power and network → upload address → port → protocol and authentication |
| Online but no person record | Central person → device association → synchronization queue → device response → local person record |
| Recognition works but no event appears | Device upload settings → receiver logs → event response → display mode or central callback |
| Wrong name or photo | Unique person identifier → existing device record → latest update task |
| Wrong time or entry/exit status | Device clock and timezone → event time → direction configuration → room relationship |
Record the test time, device identifier, test-person identifier, and error message. Do not investigate synchronization by bulk deleting device records or resetting devices.
Person synchronization is processed by the central service according to each device protocol. Devices that support active delivery are handled through a queue; generic HTTP devices retrieve changes and return results. Actual processing speed depends on the deployed network and configuration. UDP 20785 discovers participating system nodes, while recognition-device protocol heartbeats are a separate path and should not be interchanged.