Traceability of data sent to the Lucca connector
With Ubiqod, your time clocks and QR codes (trackers) send their data to Lucca via a connector.
The platform includes a data traceability system that allows you to:
- View data received by the trackers
- See which data has been sent to the Lucca connector and view the connector's response
- Replay failed data when necessary
- Acknowledge failed data
In the event of a data error, an alert email is sent to the account administrators.
This "technical" data is intended for expert users. It is retained for 45 days before being deleted.
Traceability of data sent to the Lucca connector (logs)
To view the list of data sent to the Lucca connector, click the "View logs" button located in the connector list (under the "History" column). All data from the trackers associated with this connector will then be displayed:
Viewing transmitted data and Lucca's response
The logs list features a colored dot indicating the status of the sent data:
- Green: Data was successfully transmitted.
- Red: The server returned an error.
- Grey: Data was not sent to the connector due to configured filtering settings.
- Orange: Data is currently being processed.
You can view the content of the sent data by clicking View details and selecting the Payload tab:
The Lucca server response is also available and includes an error code to help identify the origin of the problem:
Data with a green dot status has been successfully transmitted to the connector.
In this case, the server will return the following messages:
- Ubiqod - User clock-in successfully registered: The arrival was successfully recorded in Lucca.
- Ubiqod - User clock-out successfully registered and sent to Lucca: The departure was recorded. The arrival/departure combination was recorded in Lucca.
Error Codes
The possible error codes for the Lucca connector are as follows:
Error Code | Meaning |
Ubiqod - No pre-existing clock-in set | Two possibilities:1. The user pressed the Clock-out button without pressing the Clock-in button earlier.2. The user pressed the Clock-out button after exceeding the clock-in retention time. |
Ubiqod - Dropped in favor of a more recent clock-in | Double Clock-in detected. The error appears on the oldest Clock-in (based on the data timestamp, not the log date).The valid Clock-in for the employee can be found in the history. |
Ubiqod - Inputted user code or badge isn't defined in the interface's codes list | PIN code or Badge unknown to the interface.Two possibilities:1. No badge was scanned on the IoT tracker.2. The entered badge / PIN code does not exist in the list used by the QR / IoT tracker interface. |
Ubiqod - Clock-out time is set earlier than saved clock-in time | The Clock-out time appears before the Clock-in time. / Due to the client timer setup. |
Ubiqod - Invalid Lucca User ID. It should be an integer set in the code's or badge's external references list | The PIN code or badge used is not associated with any Lucca employee, or the Lucca employee ID defined in the PIN code / badge is invalid. |
You can replay failed data or acknowledge the alert so that it no longer appears in the error data list:
For the Lucca connector, we do not recommend using the replay function. Doing so may cause errors, such as replaying a clock-out before a clock-in.
Traceability of data received by the trackers (logs)
To view the list of data received from a tracker, click the "View logs" button located in the actions column of the tracker list.
Each received data point has a status: green when the data is valid and has been transmitted to the connector(s) associated with the tracker, and red otherwise.
Checking data details is very useful for verifying that data sent via trackers is correctly routed to the Ubiqod platform. A Red status does not necessarily indicate a malfunction: it may be due to a user scanning the QR code without submitting a form, or indicate that the account is out of credits.
An Orange status indicates that data is currently being processed.
A Grey status indicates utility data that is not intended to be sent to the connector(s).
Try Ubiqod
Get 100 free credits to start building with Ubiqod: sign up here
Related Articles
Traceability of data received from trackers and sent to connectors (logs)
The "build" interface of the Ubiqod platform allows you to configure trackers (connected devices, QR codes...) to send their data to third-party systems via connectors. The platform includes a data traceability system allowing: To view the data ...Lucca Connector: Employee management in Ubiqod
The Ubiqod connector for Lucca allows you to link a badge (which has a unique identifier) or a personal code (called a PIN code on the platform) to an employee in Lucca. Badges are used with clocking terminals such as TaqtOne or Clock S, and PIN ...Getting events and data from Ubiqod: using the webhook
The Ubiqod platform lets you send the data received from your trackers in real time through webhooks. In this article, you’ll learn how to set up this dispatch. The Ubiqod REST API gives you access to configuration data for trackers, badges, and ...Setting up the connection between Lucca and Ubiqod: Testing and moving to production
Once your hardware is set up, you can perform a series of test swipes. All data is collected in your test connector, which is linked to your Lucca sandbox instance. When you have finished testing, you must disable the test connector and enable the ...Visualize data with View
The Ubiqod platform enables you to configure QR codes and connected devices (called trackers) to monitor field activity. All configuration tools are centralized in a workspace called Build. To visualize data, you must access the View workspace. It ...