TPX-IoT-Flow 1.8.X
1.8.4c
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4169 | Custom drivers not detected if not releated to a system driver. |
1.8.4b
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4167 | Driver Engine – Fixed system drivers not being listed in the API for old catalog. |
1.8.4a
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4161 | Refine Objenious geolocation and payload mapping. |
1.8.4
Release Goals
This release marks a major milestone in driver engine modernisation: the Go Driver Engine is now the primary decoding engine, replacing the JS engine as default. A per-protocol fallback mechanism allows operators to route specific protocol IDs back to the JS engine when needed.
Reliability improvements focus on Bridge smart shutdown — which ensures graceful connection migration during rolling upgrades — and Supervisor High Availability with automatic connection rebalancing. The Kafka Connector gains enterprise-grade security (SASL, OAuth 2.0, TLS 1.3), and the HTTP Connector receives significant throughput optimisations. New processors extend the ecosystem with a LoRaWAN Portal CONNECT processor and a Senet processor.
NEW FEATURES RELEASED
| JIRA Ticket | Description |
|---|---|
TXIF-4096 | HTTP Connector – Significant performance optimizations for outbound HTTP connectors. |
TXIF-4016 | Kafka Connector – Support for SASL/PLAIN, SASL/SCRAM, OAuth 2.0 bearer token, and mutual TLS (mTLS) security protocols. |
TXIF-4072 | All Connectors – TLS 1.3 negotiation enabled to prevent hard-lock on TLSv1.2. |
TXIF-3870 | Bridge – Smart connection shutdown for graceful rolling upgrades without message loss. |
TXIF-4146 | Driver Engine – Go engine is now the primary decoding engine; JS engine kept as a configurable fallback. |
TXIF-4056 | Driver Engine Go – JS driver catalog support. |
TXIF-4057 | Driver Engine Go – Custom driver support. |
TXIF-4071 | Processor – New CONNECT processor for LoRaWAN Portal with configurable message format selection. |
TXIF-4104 | Processor – CONNECT processor extended to support all LoRaWAN Portal connector types. |
TXIF-4075 | UI – Chirpstack processor improvements. |
TXIF-4082 | UI – Abeeway processor is no longer visible in OCP mode. |
TXIF-4132 | UI – New RESTARTING connection state with translations. |
TXIF-4089 | API – Custom HTTP Headers name and value character limit increased beyond 510 characters. |
TXIF-4152 | Core – Improved HTTP error codes returned for downlink failures. |
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4127 | API – Fixed intermittent UNREACHABLE connection state. |
TXIF-4136 | Transformer – Fixed Join Accept transformation failure. |
TXIF-4137 | Transformer – Fixed Notification transformation failure. |
TXIF-4138 | Transformer – Fixed Everynet Alarm message processing issue. |
TXIF-4139 | Transformer – Fixed Everynet Location message processing issue. |
TXIF-4140 | Transformer – Fixed uplink tags not being mapped correctly. |
TXIF-4142 | Azure Event-Hub Connector – Fixed downlink topic not being listened after connection start. |
TXIF-4153 | Processor – Fixed mapping of "group" field for Spot/Objenious processor. |
TXIF-4076 | OPCUA Connector – Additional fix for connection issue after Liquibase migration from tpx-flow-1.8.2. |
1.8.3d
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4076 | TPX-Connection-OPCUA issue after liquibase migration to tpx-flow-1.8.2. |
TXIF-4093 | Flow-hub stopped processing Kafka messages after a restart. |
TXIF-4095 | Events are not recorded. |
1.8.3
NEW FEATURES RELEASED
| JIRA Ticket | Description |
|---|---|
TXIF-3961 | Implementation of a dedicated transformation processor to support Everynet messages. |
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-4033 | Downlink topic in AWS IoT Core is not re-subscribed after client reconnection. |
1.8.2
NEW FEATURES RELEASED
| JIRA Ticket | Description |
|---|---|
TXIF-3714 | Driver-Engine GO – Added support for custom drivers. |
TXIF-3782 | OPCUA Connector – Improved OPCUA Alarm device data quality with more granular states. |
TXIF-3783 | Security update addressing recent CVEs. |
TXIF-3786 | Tpx-Core – Exposes DriverCfg/id after a failed decoding to ease troubleshooting. |
TXIF-3876 | Driver-Engine GO – Added Go driver for Clariane DTN LW-eTRV-C devices. |
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-3679 | Azure Event-Hub Connector – Downlink throughput improved from ~100 msg/min to ~3.5K msg/min. |
TXIF-3727 | API – Fixed errors when updating or deleting flows with many DevEUI in Matched Keys. |
TXIF-3760 | Driver-Engine – Stability and reliability improvements. |
TXIF-3775 | MQTT Connector – Fixed MQTT connection thread leak when connection fails due to timeout. |
TXIF-3778 | MQTT Connector – Ensured MQTT connection timeout is correctly applied. |
TXIF-3780 | AMQP Connector – Fixed AMQP connector so the subscribed topic field is truly optional. |
TXIF-3815 | OPCUA Connector – Fixed tag count limitation issue on the OPC-UA server. |
TXIF-3818 | Thingboard Connector – Fixed intermittent login failures. |
TXIF-3869 | OPCUA Connector – Fixed abnormal CPU consumption issue in specific scenarios. |
TXIF-3875 | AWS Connector – Fixed issue where a malformed downlink could stop the connector. |
TXIF-3907 | OPCUA Connector – Disabled Device & BaseStation cache to avoid outdated information. |
1.8.1b
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-3753 | Supervisor & Bridges are too slow to start connections. |
1.8.1a
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-3752 | TPX-LE Processor could cause issue on uplink if debug mode wasn't used. |
1.8.1
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-3613 | Kafka flow should not be stopped when Driver-Engine return an unexpected format. |
TXIF-3618 | Downlinks that should be encoded and published by the AS are rejected. |
TXIF-3623 | TPW user only - Unable to encode payload using custom drivers forced in the Flow. |
TXIF-3628 | TPW user only - Unable to encode payload using custom drivers forced in the Flow with Generic Device Profiles. |
TXIF-3639 | Tpx-API - Encode downlink doesn't work on a custom driver from UI. |
TXIF-3662 | HTTP Connector - Destination URL extended up to 512 characters. |
1.8.0a
MAJOR BUGS RESOLVED
| JIRA Ticket | Description |
|---|---|
TXIF-3612 | ReconnectionStrategy - Wrong enumeration type. |
1.8.0
Release Goals
This major release is mainly a technical upgrade.
The framework and SDK have been upgraded, and the application now uses Java 17.
We have worked to fix all critical and high CVEs, improved internal mechanisms, reworked the code for optimization, and enhanced monitoring.
A new message counter named "Lost uplinks" has been introduced to track uplinks intentionally skipped due to a filter or an exclusion rule.
Processors
Chirpstack V4 format
In the Output Stream Processors panel of your connection, you can now automatically transform Actility uplinks into the Chirpstack V4 uplink format.
Example of a generated Chirpstack V4 uplink:
{
"devEUI": "JOEkclwSEEA=",
"fPort": 85,
"deviceName": "Milesight - AM103",
"fCnt": 11527,
"adr": true,
"applicationName": "msight:am100-series:1",
"rxInfo": [
{
"rssi": -50,
"loRaSNR": 9.5,
"rfChain": 1,
"gatewayID": "EAAxsw==",
"time": "2025-08-14T08:38:40.821Z"
},
{
"rssi": -105,
"loRaSNR": 8.75,
"rfChain": 0,
"gatewayID": "EAAJqQ=="
},
{
"rssi": -72,
"loRaSNR": 8.25,
"rfChain": 0,
"gatewayID": "EAAANQ=="
}
],
"data": "AXUmA2fuAARodQd9jwI=",
"objectJSON": "{\"battery\":38,\"temperature\":23.8,\"humidity\":58.5,\"co2\":655}",
"txInfo": {
"frequency": 867700000,
"modulation": "LORA",
"loRaModulationInfo": {
"spreadingFactor": 7
}
}
}
Connectors
Disable decoding of uplinks
In the Advanced settings panel of each connection, you can now choose to disable automatic payload decoding.
By default, decoding remains enabled.
New Features Released
| JIRA Ticket | Description |
|---|---|
TXIF-2293 | Major framework and SDK upgrade. |
TXIF-2993 | Migration to Java 17. |
TXIF-3389 | Fix for all critical and major CVEs. |
TXIF-2294 | New processor – Chirpstack V4. |
TXIF-3084 | Azure Event-Hub Connector – Support for TLS 1.3. |
TXIF-2798 | Cumulocity Connector – Support for custom CA certificates. |
TXIF-2924 | All Connectors – DriverEnabled option to disable uplink decoding (enabled by default). |
Major Bugs Resolved
| JIRA Ticket | Description |
|---|---|
TXIF-3104 | Azure IoT-Central Connector – Support for multiple hubs. |
TXIF-3364 | Fixed downlink failure counter issue when a downlink failed via REST API. |
TXIF-3239 | Modbus connectors – Dashes in DeviceEUI are now automatically removed. |
TXIF-2635 | Thingworx connectors – Internal cache synchronized when a Thing is removed on the Thingworx side. |