The following are release notes for Tetra Metrohm OMNIS Connector versions 1.0.x. The Tetra Metrohm OMNIS Connector is a standalone, containerized application that receives analysis results from Metrohm OMNIS by using a webhook and uploads them to the Tetra Data Platform (TDP) with full metadata. A background loop automatically detects and retries failed uploads.

v1.0.0

Release date: 5 June 2026

What's New

TetraScience has released its first general availability (GA) version of the Tetra Metrohm OMNIS Connector. The Connector integrates Metrohm OMNIS laboratory systems with the Tetra Data Platform (TDP) by receiving analysis results pushed from OMNIS by using a webhook and uploading them to the TDP.

Here are the details for what's in Tetra Metrohm OMNIS Connector v1.0.0.

Prerequisites

Tetra Metrohm OMNIS Connector v1.0.0 requires the following:

• Tetra Data Platform (TDP) v4.0.0 or later
• A Metrohm OMNIS system configured with the CALL WEB API command in an Operating Procedure to push analysis results to the Connector
• Linux OS with Docker installed; for a standalone deployment, a Linux host
• Deployment on a Tetra Hub or as a standalone deployment

For more information, see the Tetra Metrohm OMNIS Connector User Guide (v1.0.x).

New Functionality

New functionality includes features that were not previously available.

• Webhook-Based Ingestion: The Connector exposes a local endpoint that receives JSON payloads from the Metrohm OMNIS CALL WEB API command.

• Automatic Retry with Failed Upload Recovery: A background loop automatically detects uploads that did not reach the TDP and re-attempts them.

• TDP Connector Files Panel Integration: Upload history, status, and failure reasons are visible in the TDP connector files panel.

• TDP UI Configuration Support: You can configure OMNIS credentials, webhook settings, and retry options directly in the TDP user interface.

• Configurable Webhook Port: The webhook server defaults to port 9000 and is configurable on Standalone deployments. The Connector logs an actionable error if the configured port is already in use.

• Tetra Hub and Standalone Deployment: The Connector supports deployment on either a Tetra Hub or as a standalone Docker container deployment.

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

• There are no enhancements in this initial release.

Bug Fixes

There are no bug fixes in this initial release.

Limitations

The following are known limitations of the Tetra Metrohm OMNIS Connector v1.0.0:

• The OMNIS Integration API commands (such as creating samples and executing sample lists) are not exposed through TDP commands in this release. Bidirectional orchestration through TDP pipelines is planned for a future release.

Deprecated Features

There are no deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

• The Connector keeps uploading webhook data to the TDP while in IDLE mode. Switching the Connector to IDLE correctly stops the retry / polling loop (no more OMNIS Integration API calls, no more retry attempts), but it does not stop the webhook listener: any data OMNIS sends through CALL WEB API is still accepted and uploaded to the TDP. To fully stop uploads, Disable the Connector in the TDP UI. Fix planned in a future release: while the Connector is in IDLE, webhook payloads are buffered to disk and then uploaded when the Connector returns to RUNNING.

Upgrade Considerations

This is the initial release of the Tetra Metrohm OMNIS Connector. Future release notes will include upgrade instructions when applicable.

To install and configure the Connector, see the Tetra Metrohm OMNIS Connector User Guide (v1.0.x).

Other Release Notes

To view other release notes for Tetra Connectors, see Tetra Connector Release Notes.