Multiple protocols
Connect compatible devices through TCP, UDP, ADMS/iClock push, or the secured HTTP punch API.
ZKT Biometric Attendance Device Integration (Odoo.sh, Custom Cloud, On-premise)
by Muhammad Mudassir https://mudassir.it.com
Odoo
$ 112.92
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) |
| Lines of code | 5648 |
| Technical Name |
biometric_attendance_bridge |
| License | OPL-1 |
| Website | https://mudassir.it.com |
| Versions | 17.0 18.0 19.0 |
Biometric Attendance Bridge
Biometric devices, attendance punches, employees, and Odoo 19 — connected.
99 EUR ONE-TIME APP PRICE
Bring compatible biometric attendance machines into Odoo Attendances. Download users and punches, map employees, synchronize check-ins and check-outs, and manage device communication from one workspace.
What it does
Employee mapping
Download machine users, match them to Odoo employees, and optionally upload employee users to devices.
Attendance synchronization
Convert raw device punches into Odoo check-ins and check-outs using configurable status codes.
Scheduled automation
Use scheduled actions to retrieve device logs and synchronize pending attendance records.
Timezone aware
Store accurate UTC timestamps while configuring the local timezone independently for every device.
Operational controls
Inspect users, fingerprints, data logs, commands, device information, and safe-clear notifications.
How it works
Create the device
Choose TCP, UDP, or ADMS and configure network, serial, timezone, and status-code settings.
Connect and map
Download machine users and map each device identity to the correct Odoo employee.
Collect punches
Poll the device, accept ADMS pushes, or submit a token-authenticated HTTP punch.
Synchronize Attendances
Transform raw check-in/check-out events into standard Odoo HR Attendance records.
Deployment compatibility
| Platform | Supported | Important notes |
|---|---|---|
| Odoo 19 Community | Yes | Install the Odoo Attendances application first. |
| Odoo 19 Enterprise | Yes | Compatible with the standard Attendances application. |
| On-premise / private cloud | Yes | Recommended for TCP/UDP devices on a private network. |
| Odoo.sh | Yes | ADMS/iClock push is recommended. Direct TCP/UDP requires network reachability to the device. |
| Local development | Yes | The Odoo machine must be able to reach the terminal IP and port. |
| Odoo Online | No | Odoo Online does not allow custom Python modules. |
Installation
Add the module
Copy biometric_attendance_bridge into an Odoo 19 addons path or your Odoo.sh Git repository.
Restart and update
Restart Odoo, enable developer mode, and run Apps > Update Apps List.
Install
Search for Biometric Attendance Bridge and install it.
Configure networking
Permit the required TCP/UDP route or point the ADMS device to the public Odoo URL.
Security and networking
The custom punch endpoint requires a per-device secret in the X-Attendance-Token header. ADMS/iClock devices authenticate operationally through their configured serial number because many terminals do not support custom HTTP headers. Use HTTPS and network allowlists wherever possible.
Device compatibility
TCP/UDP support targets terminals implementing the commonly used ZK attendance protocol. ADMS/iClock support targets compatible push terminals. Features vary by device model, firmware, fingerprint algorithm, and network configuration, so validate the exact device in a staging database before production rollout.
ZKTeco face and hybrid terminals
Common ZKTeco face, fingerprint, RFID, and hybrid attendance terminals.
ZKTeco fingerprint attendance
Popular fingerprint attendance devices using ZK-compatible communication.
iClock and IN series
Widely used ZKTeco attendance terminals for office and site deployments.
MB, uFace and iFace series
Mixed biometric terminals commonly used for employee attendance.
Other ZKTeco attendance models
Additional ZKTeco and ZK-protocol attendance terminals often used on projects.
ZK-compatible and OEM devices
May work when the terminal uses the same ZK attendance protocol or ADMS/iClock push behavior.
Compatibility is not limited to the models above. The list is a practical reference for common ZKTeco/ZK-based attendance terminals; final behavior depends on firmware, enabled protocol, network reachability, and available commands.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) |
| Lines of code | 5648 |
| Technical Name |
biometric_attendance_bridge |
| License | OPL-1 |
| Website | https://mudassir.it.com |
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