Skip to Content

HikCentral Attendance Sync

by
Odoo

$ 152.71

v 19.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Attendances (hr_attendance)
• Employees (hr)
• Discuss (mail)
Lines of code 175
Technical Name hikcentral_integration_attendance
LicenseOPL-1
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Attendances (hr_attendance)
• Employees (hr)
• Discuss (mail)
Lines of code 175
Technical Name hikcentral_integration_attendance
LicenseOPL-1
Versions 17.0 18.0 19.0
Demo Info!

Demo Database: hikvision_demo

User: demo | Password: 1234

HikCentral Attendance Sync

Seamlessly integrate HikCentral with Odoo to automate attendance tracking from Hikvision devices in real-time. A versatile solution for businesses of all sizes, from small startups to large enterprises, to streamline HR processes and enhance workforce management.

Supported Systems & Devices

This module connects Odoo with the following Hikvision & HikCentral solutions **via the HikCentral server API** (attendance data is pulled from the server, not directly from the device):

  • HikCentral API (including /artemis and /artemis-web paths)
  • Hikvision biometric devices (face recognition, fingerprint, card readers)
  • Access control attendance (door controllers, turnstiles, barriers)
  • Biometric attendance systems (real-time punch in/out)
  • HikCentral editions (Professional, Enterprise, Connect)

Custom endpoint support: If your system uses a different path (e.g. /ISAPI/...), configure it via hikcentral.api_endpoint.

Important Update – v19.0.1.0

New features added:

  • Now fully supports both /artemis and /artemis-web API paths (auto-detection)
  • Custom API endpoint setting via hikcentral.api_endpoint (default: /api/v1/attendance/records)
  • Improved compatibility with various HikCentral editions

Price update: The module price is now $129.36 (base price). Local VAT or Odoo fees may be added at checkout depending on your country.

Possibilities of use

  • VPN: YES.
  • Internal IP: YES.
  • Public URL: YES.
  • For testing: YES.

Key Features

  • Real-Time Sync: Automatically fetch attendance records from HikCentral every hour.
  • Hikvision Integration: Link employee IDs from Hikvision devices to Odoo HR profiles.
  • Flexible & Scalable: Suitable for small, medium, and large workforces.
  • Easy Setup: Simple API configuration with step-by-step guidance.
  • Reliable Logging: Detailed logs for sync monitoring and troubleshooting.

Installation and Configuration Steps

  1. Add the Module to Odoo:
    • Copy hikcentral_integration_attendance to your Odoo addons folder.
    • Restart Odoo, go to Apps, and install "HikCentral Attendance Sync".
  2. Configure API Settings:
    • In Odoo, go to Settings > Technical > System Parameters and add:
    • hikcentral.api_key: Your HikCentral API Key
    • hikcentral.api_secret: Your HikCentral API Secret
    • hikcentral.api_url: HikCentral server base URL Examples:
      • VPN/Internal: https://192.168.*.*/artemis or https://192.168.*.*/artemis-web
      • Public (if forwarded): https://*.112.8.*/artemis
      • Note: Module automatically adds /artemis if missing.
    • hikcentral.api_endpoint: API path (default: /api/v1/attendance/records) → Change only if your HikCentral uses a different path (e.g. /ISAPI/AccessControl/AcsEvent).
  3. Set Up Employees:
    • Navigate to Employees and enter each employee's Hikvision Employee ID.
  4. Install Dependencies:
    • Run pip install -r requirements.txt on your Odoo server.
  5. Verify Sync:
    • Check the Odoo log file (odoo.log) to ensure attendance data is syncing.
List before Download
Before list
Fill codes in Employees
Download
Download
Download
List after Download
After list

Affordable and powerful automation for businesses of all sizes.

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
There are no ratings yet!
by
Saudi Anfal Group
on 3/2/26, 1:39 AM

this my email odoo.manager@saudianfal.com 
Hikcentral + OODA

Tuesday, March 3, 2026

10:00 AM - 11:00 AM (AST)

Meeting link: Hikcentral + OODA | Microsoft Teams | Meetup-Join

by
Saudi Anfal Group
on 3/1/26, 6:29 AM

we can make a meeting online with it ?

by
J Torbat
on 3/1/26, 9:39 AM Author

Yes of course. Leave here your gmail. I will connect

by
Saudi Anfal Group
on 2/16/26, 3:55 AM

i already check the link with local and public ip it working but it think we are using open api so that why you need to be add - web after the artemis link

https://192.168.3.2/artemis-web           for local 

https://93.112.8.153/artemis-web  ​for public acces 

use the -web in the last i hope its work

by
J Torbat
on 2/16/26, 5:45 AM Author

After checking everything, your api_url should remain with /artemis (not /artemis-web). Changing it to /artemis-web is not correct for the actual API calls – that's only for the web portal.

The reason attendance is not syncing is most likely one of these:

  • VPN connection issue (routing problem – the internal IP 192.168.3.2 is not reachable even when VPN is connected)
  • Firewall / port 443 is blocked on the HikCentral server side
  • The HikCentral server itself is not listening on that IP/port

Please ask your IT team to test:

  1. While VPN is connected → run ping 192.168.3.2
  2. Open in browser: https://192.168.3.2/artemis/api/resource/v1/device

If ping fails or browser times out → the problem is on the VPN/server side, not in the module.

We can continue once the connection is confirmed working. Let me know the ping/browser result when possible.

Best regards,

by
Saudi Anfal Group
on 2/16/26, 12:26 AM

i put all data for api but i can collect attenandance 

by
J Torbat
on 2/16/26, 1:50 AM Author

How to correctly set hikcentral.api_url

Case 1 – You are using VPN

  1. Connect to your VPN first (Endpoint Security VPN or the .dmg file provided).

  2. After connecting, find the internal IP of the HikCentral server:

    • Windows → open Command Prompt → type ping hikcentral or ipconfig
    • Mac/Linux → Terminal → ping hikcentral or ifconfig / ip addr → Look for an IP like 192.168.x.x or 10.x.x.x
  3. Set the parameter like this: hikcentral.api_url = https://192.168.x.x/artemis (replace 192.168.x.x with the real internal IP you found)

Case 2 – You are accessing from outside (no VPN / public access)

  1. Your company’s IT must set up port forwarding or a reverse proxy on the router/firewall.
  2. The external (public) address should point to the HikCentral server.
  3. Example (if IT has already configured it): hikcentral.api_url = https://your_ip/artemis or hikcentral.api_url = https://hikcentral.yourcompany.com/artemis

Important notes for both cases

  • Always include https:// (or http:// if not using SSL)
  • The URL must end with /artemis (not /ISAPI or anything else)
  • Test the URL first in a browser: open https://YOUR_IP/artemis/api/resource/v1/device → If you get 401/403 → URL is correct → If timeout / connection refused → wrong IP or port forwarding not done

After setting the three parameters correctly, run the sync again.

by
Saudi Anfal Group
on 2/15/26, 2:11 AM

thank you working now in this url http://103.168.178.166:4444/odoo/system-parameters?debug=1

i can test our api in your database ? 

by
J Torbat
on 2/15/26, 8:45 AM Author

Yes, of course. It is free to test

still not connected
by
Saudi Anfal Group
on 2/15/26, 12:37 AM

This site can’t be reached

103.168.178.166 refused to connect.

still not connected
by
J Torbat
on 2/27/26, 12:18 AM Author

Module Upgraded. Now you can use `/artemis` and `/artemis-web`. And Improved compatibility with various HikCentral editions

by
Saudi Anfal Group
on 2/11/26, 6:30 AM

hello i try to open  your link 


This site can’t be reached

103.168.178.166 refused to connect.

by
J Torbat
on 2/12/26, 9:23 AM Author

Now available

The demo is now live for v19
by
J Torbat
on 1/27/26, 9:44 PM Author


need demo
by
Saudi Anfal Group
on 1/26/26, 1:56 AM

hello

i need demo for this module 

need demo
by
J Torbat
on 1/26/26, 3:56 AM Author
Hello! 
The v18 demo is currently live and fully operational. 
You're welcome to test your API immediately at: 
URL : http://103.168.178.166:7676/web/login?redirect=%2Fodoo%3Fdb%3Dhikvision_demo
Database: hikvision_demo

User: demo
Password: 1234

Note: The API implementation is identical between v18 and v19, so results will be the same on either version.