ZKTeco Biometric Attendance | ZKteco Biometric Attendance Integration | ZKTeco | ADMS Push Attendance Integration | ZKTeco Attendance Integration | ZKTeco ADMS Integration
by Waqas Mustafa https://www.linkedin.com/in/waqas-mustafa-ba5701209/
Odoo
$ 40.04
-
Community
-
Enterprise
Enterprise
Community
ZKTeco Biometric Attendance Integration for Odoo
Real-time attendance sync via Direct IP/LAN or ADMS Cloud Push
Description
Connect your ZKTeco biometric terminals directly to Odoo. Attendance punches are automatically converted into Odoo HR Attendance check-in and check-out records no manual data entry required.
Supports both Direct IP / LAN (Odoo pulls from device) and ADMS / Cloud Push (device pushes to Odoo in real-time). Works with fingerprint, face, card, and PIN verification methods.
Key Features
Direct IP / LAN Mode
Odoo connects directly to device via TCP/IP using pyzk library
ADMS / Cloud Push Mode
Device pushes punches to Odoo in real-time works over internet, no polling
Employee Mapping
Auto and manual mapping of device users to Odoo employees
Auto Check-In / Check-Out
Punches automatically create or close HR Attendance records
Duplicate Protection
Unique key per punch prevents duplicate attendance records
Live Dashboard
Connected devices, today's attendance, unmapped logs, missing checkouts
After Installation Grant User Access
⚠ Important: After installing the module, users will not see the Biometric Attendance menu until you grant them access from Settings.
Follow these steps to give a user access:
- Go to Settings → Users & Companies → Users
- Open the user you want to give access to
- Scroll down to the Extra Rights section
- Enable one of the following:
- Biometric Attendance User can view dashboard and attendance logs
- Biometric Attendance Administrator full access (devices, mapping, settings)
- Click Save the user will now see the Biometric Attendance menu
Mode 1 → ADMS / Cloud Push
Setup
Requirement: Odoo must be accessible from the internet (cloud server or public IP).
No
pyzk installation required.
Step 1: Configure Device Cloud Server Settings
On the ZKTeco device go to: Menu → Comm → Cloud Server Settings
- Server Mode: ADMS
- Enable Domain Name: Off (use IP directly)
- Server Address: Your Odoo server IP
- Server Port: 8069 (Odoo default port)
Step 2: Get Device Serial Number
On the device go to: Menu → System → Device Info
Note down the Serial Number (e.g. FQQ2252400516).
Note down the Serial Number (e.g. FQQ2252400516).
Step 3: Add Device in Odoo
Go to Biometric Attendance → Devices → New and fill:
- Connection Mode: ADMS / Cloud Push
- Serial Number: Paste the serial number from Step 2
- Timezone: Select your local timezone (e.g. Asia/Karachi)
Step 4: Restart the Device
Turn the device off and back on. It will register with Odoo automatically within 30
seconds.
The device state will change to Connected and Last Seen
will update.
Step 5: Make a Punch
Place your finger (or face/card) on the device. The punch is pushed to Odoo in real-time.
The user will automatically appear in Device Users after the first punch.
Step 6: Map Employees
Go to Employee Mapping. Link the device user to the corresponding Odoo employee.
All pending punches will be processed and HR Attendance records will be created automatically.
✅ Done! From this point every punch on the device creates an instant check-in or
check-out in Odoo no manual sync needed.
Odoo Attendances Calendar All synced punches appear as check-in/check-out records in the standard Odoo Attendances module, fully visible in calendar and list view.
Mode 2 → Direct IP / LAN Setup
Requirement: Odoo server and ZKTeco device must be on the same network. If not, set up port
forwarding on your router for port 4370.
Step 1: Install pyzk on Odoo Server
Run the following command on your Odoo server:
pip install pyzk
Step 2: Add Device in Odoo
Go to Biometric Attendance → Devices → New and fill:
- Connection Mode: Direct IP / LAN
- Device IP: IP address of your ZKTeco device
- Port: 4370 (default)
- Timezone: Select your local timezone
Step 3: Sync Users
Click Sync Users button. All enrolled users from the device will appear under
Device Users tab.
Step 4: Sync Attendance
Click Sync Attendance button. All stored punches are downloaded and raw logs are created
under Attendance Logs.
Step 5: Map Employees
Go to Employee Mapping. Link each device user to the corresponding Odoo employee.
Once mapped, all pending logs will automatically create HR Attendance check-in/check-out records.
✅ Done! Future syncs run automatically via scheduled cron jobs based on your
configured auto-sync interval.
Supported Verification
Methods
Fingerprint
Face Recognition
Card / RFID
PIN
Auto-detected from device punch data â no manual configuration required.
Troubleshooting
Direct IP Connection Failed
- Make sure
pyzkis installed on the Odoo server - Confirm device IP is correct and reachable from the server
- Device and server must be on the same network or configure port forwarding (port 4370) on the router
- Check that no firewall is blocking port 4370
ADMS Device Not Connecting
- Verify Server Address and Port (8069) on the device
- Make sure Enable Domain Name is OFF when using IP
- Serial number in Odoo must exactly match the device's serial number
- Odoo server must be publicly accessible localhost will not work
- Try restarting the device after saving settings
Attendance Logs Showing Wrong Time
- Set the correct Timezone on the device record in Odoo (e.g. Asia/Karachi)
- The module converts device local time to UTC automatically using this setting
Employees Not Getting Attendance
- Go to Employee Mapping and map the device user to an Odoo employee
- Unmapped logs are stored and will be processed automatically once mapped
Contact Us
Support, customizations, and development
+92 305-9175085
linkedin.com/in/waqas-mustafa-ba5701209
Our Expertise
Odoo Development
Customization Services
Module Development
Support & Maintenance
Quality Solutions
Connect with us
Waqas Mustafa | ezcodesolution
Version: 19.0.2.0.1
Module design is reserved | Copyright ©
Waqas Mustafa | ezcodesolution
Changelog
-
19.0.2.0.1 2026-06-22
- ADMS real-time push mode â full support for ZKTeco Push Protocol 3.x
- Fixed device re-registration loop in ADMS mode
- Timezone-aware punch time conversion for correct local time display
- Verified code mapped to Fingerprint / Face / Card / PIN method field
- getrequest heartbeat and command delivery working correctly
-
19.0.1.0.0 2025-12-05
- Initial release â Direct IP / LAN mode with pyzk
- Employee mapping, duplicate protection, cron-based auto sync
- Live dashboard with connected devices and attendance stats
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) |
| Lines of code | 1926 |
| Technical Name |
odoo_zkteco_biometric_attendance |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/waqas-mustafa-ba5701209/ |
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