$ 93.34
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 5887 |
| Technical Name |
connector_biotime |
| License | OPL-1 |
| Website | https://demo18.domiup.com |
| Versions | 16.0 17.0 18.0 |
BioTime Connector
Synchronize employee attendance and HR data between Odoo and BioTime effortlessly.
The BioTime Connector enables seamless integration between Odoo HR modules and BioTime biometric systems. This module supports both push and pull operations, automated synchronization, and real-time attendance logging.
ð¥ Watch Demo: BioTime Connector
See how to install, configure, and sync data between Odoo and BioTime.
Click the image to watch on YouTube
Demo Accounts
| Role | Login | Password |
|---|---|---|
| Demo User | demo | demo |
Key Features
- Two-Way Integration: Push employee data, departments, work locations. Pull transactions
- Real-Time Attendance: Convert BioTime punch logs to
hr.attendancerecords - Queue Job Support: Reliable and retryable background sync via
queue.job - Sync Modes: Choose to sync all employees or only those assigned to a specific server
- Retry & Failure Handling: Intelligent retry logic and logging for failed pushes/pulls
Supported Models
hr.employeehr.departmenthr.work.locationhr.attendance(generated)
Ideal For
- Companies using BioTime biometric devices
- Teams needing centralized HR data in Odoo
- IT admins wanting configurable API automation and reliability
Screenshots & Setup
Below is an example configuration for a BioTime Server. This form allows you to define the API connection, punch state mapping, and employee sync mode.
- Host/IP: URL or IP address of your BioTime server (e.g.,
biotimedxb.com). - Port: The API port used for connection (e.g.,
8007). - Timezone: Used to convert punch times from BioTime into Odoo's local time.
- Punch State In: Indicates what state (e.g., "Check-In") should be treated as an entry time.
- Punch State Out: Indicates the corresponding exit time state (e.g., "Check-Out").
- Employee Push Mode:
- All Employees: All employees will be synchronized to BioTime.
- Only Assigned Employees: Only employees with the
Biotime Serverfield set will be pushed.
Push Actions
The Push Actions tab in the BioTime Server form lists the entities that can be pushed to BioTime, including Departments, Work Locations, and Employees.
- Each row represents a push action for a specific model, such as
hr.department,hr.work.location, andhr.employee. - You can click the Push Now button to immediately synchronize data with BioTime.
- This is especially useful after the first install or when going live, to push initial master data.
- The system ensures only active actions will run, and only eligible records (e.g., assigned employees) will be sent.
Pull Actions
The Pull Actions tab allows you to fetch data from BioTime into Odoo, such as transaction logs (punch times). It is especially useful for updating Odoo attendance records based on employee activity in BioTime devices.
- Pull Create biotime.transaction is used to import punch logs from BioTime.
- The system only pulls transactions where the
punch timeis newer than the recordedSync Last Date. - Click Pull Now to fetch the latest transactions manually.
- The records are stored in the
biotime.transactionmodel, and automatically converted intohr.attendanceif valid.
Transaction to Attendance Conversion
Each transaction pulled from BioTime is saved in biotime.transaction and linked to an employee. A scheduled job processes these transactions and creates hr.attendance records based on punch-in/out patterns.
- Each transaction includes raw punch data like:
- Employee Code
- Punch Time
- State (Check-In / Check-Out)
- Verify Type and Terminal Info
- The scheduled job pairs valid IN/OUT punches and generates corresponding
hr.attendancerecords. - Linked attendance entries are shown clearly for traceability.
- Failed or incomplete transactions are retried automatically (up to a configurable limit).
Need Help?
Contact the developer or system integrator team for setup assistance, custom mappings, or troubleshooting.
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