HikVision / Anviz / Suprema Attendance Connector

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.

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.

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.

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.

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.

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.

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.