HikVision / Anviz / Suprema Attendance Connector

Name: HikVision / Anviz / Suprema Attendance Connector
Brand: ECOSIRE
SKU: odoo-multivendor-biometric-connector

核心功能

HikVision face + card terminal support via ISAPI event-listening / event ISAPI push, with vendor SDK fallback for firmware that requires it

Anviz fingerprint and multi-modal reader integration (TCP/IP polling or SDK subscription) mapped to normalized punches

Suprema controller / BioStar integration for fingerprint, face and access events pulled into Odoo HR Attendance

Convoy and other generic TCP push-log devices handled through a pluggable device-adapter layer — add new vendors without core changes

Unified punch normalization: every vendor event becomes a single hr.attendance-ready record (employee, device, direction, verify method, corrected timestamp)

Auto employee mapping — biometric enrollment ID / card number / device user-ID resolved to the correct hr.employee, with an admin screen for unmatched punches

Direction resolution logic (check-in vs check-out) via device role config or alternating-punch inference, computed with @api.depends and configurable per device

Duplicate and bounce suppression — same-employee punches within a configurable window are collapsed so double-swipes don't create phantom attendance

Per-device timezone handling so a mixed-site fleet across regions posts correct local check-in/out times into Odoo

Multi-company and multi-site isolation enforced with ir.model.access.csv plus record rules so each branch only sees its own devices and logs

Scheduled polling and device health monitoring via ir.cron (automated actions) — offline or silent devices raise an alert instead of silently dropping punches

Raw-log audit trail: every original device event is retained alongside the normalized record for dispute resolution and payroll defensibility

Backend management UI (list/form views + OWL/QWeb dashboard) for devices, live punch feed, unmatched queue and per-device status

Optional XML-RPC / JSON-RPC exposure so external HR or door-access systems can read normalized attendance from Odoo

Native write-through into hr.attendance — Payroll, Timesheets, Presence and existing attendance reports keep working with zero rework

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Odoo 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Most Odoo biometric connectors assume ZKTeco. If your fleet runs HikVision face/card terminals, Anviz fingerprint readers, Suprema controllers, Convoy panels — or a mix of all four across sites — you are stuck exporting CSVs and reconciling them by hand every payroll cycle.

ECOSIRE builds you a vendor-agnostic biometric attendance connector that speaks each vendor's native protocol and normalizes every event into a single, clean stream inside Odoo's HR Attendance app. HikVision terminals push events over ISAPI / event-listening (with SDK fallback where firmware requires it); Anviz and Suprema devices are polled or subscribed via their respective SDK/BioStar interfaces; Convoy and other TCP push-log devices are handled through a pluggable device-adapter layer. Whatever the source, each raw punch lands as a normalized record: employee, device, direction (check-in/check-out), timestamp (timezone-corrected), and verification method.

This is a build-to-order engagement, not an off-the-shelf apps.odoo.com download. We architect the module against your exact device models, firmware versions, network topology and Odoo edition, then build, install, test and support it. Under the hood it ships as a proper Odoo addon: a versioned __manifest__.py, models.Model classes for devices and raw logs with @api.depends computes for punch normalization and duplicate suppression, ir.model.access.csv plus record rules for multi-company / multi-site isolation, backend list/form views and OWL/QWeb dashboards, ir.cron scheduled actions for polling and health checks, and clean write-through into hr.attendance so Payroll, Timesheets and Presence all work unchanged.

Delivered for Odoo 17, 18 and 19 (Community or Enterprise), with source code you own, deployment on your server or Odoo.sh, admin documentation, a training session, and a post-launch support window. No proprietary lock-in — the adapter layer is documented so new device models can be added later.

你得到什么

Complete Odoo addon source code (models, views, security, cron, adapters) — you own it, no per-seat or runtime license fee

Versioned module packaged for your target Odoo 17, 18 or 19 (Community or Enterprise) with a proper __manifest__.py and upgrade-safe migrations

Device onboarding and configuration for your actual HikVision / Anviz / Suprema / Convoy models and firmware, done with your team

Auto employee-mapping setup: enrollment/card/device-user IDs matched to hr.employee, plus the unmatched-punch admin workflow configured

Installation and deployment on your infrastructure (self-hosted server or Odoo.sh), with network/firewall and device-connectivity validation

Admin + operator documentation: architecture notes, device-config runbook, adding-a-new-device guide, and troubleshooting playbook

Live training session for HR/IT staff on daily operation, the unmatched queue, and device health monitoring

Acceptance test pass across your real devices — verified punches flow end-to-end into hr.attendance and Payroll

这是给谁的

IT / Systems Administrator at a multi-site enterprise

Manages a mixed fleet of HikVision, Suprema and Anviz terminals across branches and is tired of stitching per-vendor exports together. Wants one connector, one normalized stream into Odoo, device health alerts, and multi-site data isolation — without maintaining brittle scripts.

HR / Payroll Manager

Runs monthly payroll on Odoo and needs attendance they can trust. Cares that every punch maps to the right employee, that double-swipes don't inflate hours, timezones are correct, and there's a raw-log audit trail to settle disputes — so payroll stops being a manual reconciliation exercise.

Odoo Partner / In-house ERP Lead

Rolling out or supporting Odoo for a client whose existing biometric hardware is non-ZKTeco. Needs a maintainable, documented addon with a clean adapter layer and standard hr.attendance write-through, so it survives Odoo upgrades and can be extended to new device models later.

HikVision / Anviz / Suprema Attendance Connector 如何比较

标准	伊科西尔	定制建造	竞争对手
Non-ZKTeco vendor support (HikVision, Anviz, Suprema, Convoy)	Native adapters for all four, plus a pluggable layer for more	Whatever you scope and can maintain in-house	Usually ZKTeco-only; rare add-ons per single vendor
Mixed / multi-vendor fleet in one normalized stream	Unified punch normalization across all vendors into hr.attendance	Possible but you build and maintain the normalization	Rarely — most modules bind to one protocol
Auto employee mapping + unmatched-punch queue	Built in, with an admin screen for unresolved IDs	You design and build it	部分支持
Duplicate suppression & timezone-correct posting	Configurable window + per-device timezone handling	Depends on your implementation effort	部分支持
Device health monitoring via scheduled ir.cron	Offline/silent devices raise alerts instead of dropping punches	Only if you build and schedule it	部分支持
Multi-company / multi-site data isolation	ir.model.access.csv + record rules configured to your org	You implement the security model	部分支持
Fit to your exact devices, firmware & Odoo edition	Built and tested against your real hardware at discovery	包含	Generic; hope your model/firmware is covered
Source ownership & documented extensibility	You own the code; adapter layer documented for new devices	包含	Vendor-controlled; extension often blocked or paid
Delivery model	Build-to-order, installed & supported (2-4 wk lead time)	Full in-house project, indefinite timeline	Instant download, integration is on you

关于HikVision / Anviz / Suprema Attendance Connector的常见问题

How long until it's delivered, and what's the process?

This is a build-to-order engagement with a typical lead time of 2 to 4 weeks after kickoff — it is not an instant apps.odoo.com download. We start with a short discovery to capture your exact device models, firmware versions, network topology and Odoo edition, then build against those specifics, install on your environment, run acceptance tests on your real devices, and hand over. Timeline depends on the number of distinct vendors, sites and device quirks; we confirm the schedule at kickoff.

What support and updates do I get after launch?

You get a post-launch support/warranty window (scope agreed at kickoff) covering bug fixes and compatibility with Odoo minor updates on your target version. Because you receive the full source with a documented adapter layer, your own team can add new device models or extend behavior without depending on us. We also offer ongoing support and 'add a new device vendor' extensions as a separate engagement if you prefer we handle it.

Which devices and vendors are supported?

HikVision face/card terminals, Anviz fingerprint/multi-modal readers, Suprema controllers (BioStar-family), and Convoy plus other generic TCP push-log devices via the pluggable adapter layer. If you run a specific model we haven't listed, tell us at discovery — the architecture is designed so a new vendor is a new adapter, not a rewrite. Mixed fleets combining several of these are the core use case.

Which Odoo versions and editions does it work with?

We build for Odoo 17, 18 and 19, on Community or Enterprise. The module writes into the standard hr.attendance model, so it works with the free HR Attendance app on Community as well as Enterprise Payroll, Timesheets and Presence. We target the single version you're on; a multi-version build can be scoped if you're mid-migration.

How does it connect to the devices technically?

HikVision terminals are integrated via ISAPI event-listening / event push (with vendor SDK fallback where firmware requires it); Anviz and Suprema via their SDK/BioStar interfaces (subscription or polling); Convoy and similar via TCP push-log parsing. An ir.cron scheduled action handles polling and device health checks, and each raw event is normalized through @api.depends computes into an hr.attendance record. Real-time push is used where the device firmware supports it; otherwise near-real-time polling is configured.

Will double-swipes, wrong employees, or timezone drift mess up my attendance?

No — these are exactly what the module is built to prevent. Duplicate/bounce suppression collapses repeated punches within a configurable window, auto employee-mapping resolves each device ID to the right hr.employee (with an admin queue for anything unmatched), and per-device timezone handling posts correct local times. Every original device event is also kept as a raw-log audit trail, so any payroll dispute can be traced back to the source punch.

Is my data isolated if I run multiple companies or branches?

Yes. Access is controlled with ir.model.access.csv and record rules so each company or site only sees its own devices, logs and attendance. This is standard Odoo multi-company security applied to the connector's models, configured to match your org structure during the build.