| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) |
| Lines of code | 2098 |
| Technical Name |
codex_hikvision_attendance |
| License | OPL-1 |
| Website | https://www.code-experts.co/ |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) |
| Lines of code | 2098 |
| Technical Name |
codex_hikvision_attendance |
| License | OPL-1 |
| Website | https://www.code-experts.co/ |
| Versions | 17.0 18.0 19.0 |
HIKVISION ATTENDANCE
Key Features
Automatic Attendance Sync (ISAPI Pull)
Odoo polls the Hikvision device on a configurable schedule via ISAPI REST API. Attendance check-in and check-out records are created automatically in Odoo HR Attendance no push mode or webhook needed.
Complete Device Event Log
Every device event is captured and stored attendance, door open/close, failed recognition, access denied, blacklist, alarm, system, and network events. 9 categories with filters, search, and raw JSON data for debugging.
Employee Mapping & Roster Sync
Sync the full employee roster from the device into Odoo with one click. Map device employees to Odoo HR employees via a simple list view. Auto-detects unmapped users and flags mismatches.
Push & Remove Employees on Device
Enroll a new Odoo employee on a Hikvision device directly from the employee form using the Push to Device button. Remove an employee from the device with a single click and confirmation guard.
Test Connection & Auto-Fill Device Info
One-click connection test fetches the device model, serial number, MAC address, firmware version, enrolled users, and count,all auto-filled into the device form without manual entry.
Clock Drift Detection & NTP Warning
Automatically compares device time with server time. Shows a warning banner if drift exceeds 2 minutes to prevent attendance timestamp errors. Also alerts if NTP is not enabled on the device.
Full Sync History Log
Every sync run (scheduled or manual) is recorded with detailed statistics: events fetched, check-ins created, check-outs matched, duplicates skipped, unmapped employees, errors, and duration.
Multi-Device & Multi-Company
Connect multiple Hikvision terminals simultaneously. Each device has its own credentials, sync interval, and event history. Full multi-company support with company-level record isolation.
Compatible Devices
Designed for Hikvision terminals that support the ISAPI REST protocol with HTTP Digest Authentication. Works with a wide range of Hikvision access control terminals , if your device supports ISAPI, it is compatible. Not sure if your model is supported? Contact us , we provide support to help you get connected.
Detailed Guide with Screenshots
Organisations using Hikvision terminals can sync attendance directly into Odoo HR Attendance , no manual data entry, no CSV imports, no third-party middleware. Odoo polls the device on a schedule and creates check-in / check-out records automatically.
Step 1 , Install & Initial Access
After installation, the Hikvision app appears on the Odoo home screen. Assign Hikvision User (read-only) or Hikvision Admin (full access) to relevant users before proceeding.
Step 2 , Hikvision App Menu
The app provides four menus: Devices, Event Log, Sync History, and Employee Mapping.
Step 3 , Add a Device
Go to Devices and create a new record. Enter the terminal's IP address, port, admin credentials, and the timezone where the device is located.
Step 4 , Test Connection
Click Test Connection to verify connectivity , Odoo auto-fills the device model, serial, MAC, firmware, user count, and clock drift in one step.
Device Dashboard , Stat Buttons
Stat buttons at the top of the device form show Users, Faces, Events, Unmapped employees, and Syncs , click any to jump directly to the related records.
Clock Drift & NTP Warnings
A banner warns if the device clock drifts more than 2 minutes from the server, or if NTP is disabled , ensuring attendance timestamps stay accurate.
Sync Settings
Set the sync interval, first sync start date, log retention period, and whether to auto-create Odoo employees for unmapped device users. Two scheduled jobs run automatically , one for syncing, one for daily log cleanup.
Manual Sync , Sync Now
Click Sync Now to trigger an immediate sync , a notification instantly shows events fetched, check-ins created, check-outs matched, and any errors.
Employee Mapping
Click Sync Employees from Device to pull the device roster into Odoo. Unmapped rows are highlighted in yellow , assign the correct HR employee inline without opening each record individually.
Biometric Device ID on Employee Form
A Biometric Device ID field on the HR Settings tab links each Odoo employee to their enrolled device number , auto-set when mapping or pushing to the device.
Push to Device & Remove from Device
Push to Device enrolls the employee on the selected terminal via a wizard. Remove from Device revokes access immediately , both actions are tracked with timestamps in the mapping record.
Device Event Log
Every device event is stored and colour-coded , green for processed attendance, yellow for unprocessed, red for access denied or alarms, muted for system events. Filter by category, employee, or date.
Sync History
Every sync run produces a history record showing events fetched, check-ins created, check-outs matched, duplicates skipped, unmapped employees, and any errors , with a state of Success, Partial, or Failed.
Sync History Detail , Event Tabs
Each sync record has two drill-down tabs: Attendance Events (only attendance from that run) and All Events (everything the device reported in that window, including door, alarm, and system events).
Smart Anomaly Handling
The sync engine handles real-world device edge cases gracefully , nothing is lost, everything is flagged:
- Double check-in (employee scans check-in twice): the previous open attendance record is automatically closed by setting its check-out to the new check-in time, and a warning is recorded in the event log.
- Check-out without prior check-in (device missed the check-in event): an attendance record is created with check_in = check_out = event time, flagged as an anomaly so HR can review and correct it.
- Unmapped employee (device user not linked to an Odoo employee): the event is stored in the event log with a clear error message , no silent data loss. Map the employee and re-sync.
- Concurrent sync protection: if a sync is already running for a device, the next trigger is silently skipped , no overlapping runs, no database conflicts.
Device Kanban View & Device Photo
The Devices menu opens as a Kanban view showing all terminals at a glance , status, stats, and a photo of the physical unit on each card. Issues like clock drift or unmapped employees are visible without opening each device.
Attendance Gantt View
Because the module creates standard hr.attendance records, all built-in Odoo Attendance views are immediately available , including the Gantt view. You can visualise every employee's check-in and check-out blocks on a timeline, spot gaps or overlaps at a glance, and drill down into individual records directly from the chart. No extra setup needed , just open the Attendances app after your first sync.
Security & Access Control
Hikvision User (Read-Only)
Can view devices, event logs, sync history, and employee mapping. Cannot modify device settings, run syncs, or see device passwords. Suitable for HR staff who need visibility into attendance data.
Hikvision Administrator (Full Access)
Full CRUD on all models , create and configure devices, run manual syncs, push/remove employees, and view device credentials. Admin group implies User group: admins automatically have user-level access too.
Password Field Protection
The device password field is hidden from Hikvision Users at the field level , only Hikvision Administrators can see or edit device credentials. Passwords are never hardcoded, never logged in sync history or error messages.
Company-Level Record Rules
Record rules are enforced on all four models , Devices, Event Log, Sync History, and Employee Mapping. Users in a multi-company setup can only see records belonging to their own company. Complete data isolation between companies.
Why Choose Hikvision Attendance?
Zero Manual Data Entry
Face scans on the terminal automatically become check-in and check-out records in Odoo. No CSV imports, no third-party middleware, no manual punching.
Smart Deduplication
Dual deduplication by serial number and 60-second time window prevents duplicate attendance records even when employees scan multiple times rapidly.
Full Event Audit Trail
Every device event , attendance, door events, alarms, failed recognition, blacklist hits , is stored with full raw JSON data for complete traceability.
No Extra Infrastructure
Pull mode means Odoo initiates all communication. No inbound firewall rules, no webhooks, no public endpoints required on the Odoo server , works with any network setup.
Ready to Get Started?
Connect your Hikvision terminal to Odoo in minutes. Automatic attendance, full event logging, and complete sync history , all in one module.
Frequently Asked Questions
Which Hikvision devices are supported?
Any Hikvision terminal that supports the ISAPI REST protocol with HTTP Digest Authentication. Works with a wide range of Hikvision access control terminals. Not sure about your specific model? Contact us , we're happy to help verify compatibility and assist with setup.
Does this require any special network configuration?
No. The module uses pull mode , Odoo connects out to the device. You only need the device's IP address (or hostname) and port to be reachable from the Odoo server. No inbound ports, no webhooks, and no changes to the device's push configuration are required.
What happens if the device is offline during a scheduled sync?
The sync for that device is logged as failed and the error is recorded in Sync History. Other devices are not affected. On the next sync cycle, Odoo retries automatically. No data is lost because the device stores all events internally with sequential serial numbers , the next successful sync picks up from where it left off.
How does the module handle duplicate scans?
Two deduplication rules apply: (1) Each event has a unique serial number from the device , if that serial number is already in the Odoo event log it is skipped entirely. (2) If the same employee has an attendance event of the same type (check-in or check-out) within 60 seconds, the later duplicate is skipped. This prevents multiple attendance records from rapid scans.
Can I connect multiple devices to one Odoo instance?
Yes. You can add as many Hikvision devices as needed. Each device has its own credentials, sync interval, and event history. The cron job processes all active devices independently one device failing does not affect others. Multi-company is also fully supported with company-level record isolation.
Need Support?
Our dedicated support team is here to help you with installation, device configuration, employee mapping, and any questions about the Hikvision Attendance module.
| hello@code-experts.co |
+973 1722 4488
|
WhatsApp: +973 1722 4488
|
www.code-experts.co
|
© 2026 Code Experts IT Solutions. All Rights Reserved.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module