NeoEdge X Apps Release Notes

V2.2.0

Release Date
  • 2026-08-24
New Feature
  • Support custom payload configuration for MQTT and AWS IoT Core forwarder nodes.
  • Add subscribe mode to the MQTT and AWS IoT nodes to receive inbound broker messages.
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V2.1.0

Release Date
  • 2026-08-10
New Feature
  • Improve AWS IoT Core node data transfer with a compact binary format.
  • Fix stored messages so a replayed message carries the same content as one published immediately.
  • Improve Store & Forward diagnostics with deduplicated disconnect alerts and forwarding progress logs.
Bug Fix
  • Fix Store & Forward to persist messages during a broker outage.

V2.0.1

Release Date
  • 2026-05-04
New Feature
  • Add store-and-forward delivery for offline message queuing.
Improvements
  • Standardize runtime error messages.
Bug Fix
  • Fix duplicate event delivery on reconnect.

V2.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish
  • Optimize Store and Forward behavior
Bug Fix
  • Store and Forward related

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Send telemetry from gateway to AWS IoT Core
  • Auto-reconnect
  • Store and Forward
  • Authentication Mode: X.509

V2.2.0

Release Date
  • 2026-08-24
New Features
  • Support custom payload configuration for MQTT and AWS IoT Core forwarder nodes.
  • Add subscribe mode to the MQTT and AWS IoT nodes to receive inbound broker messages.
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V2.1.0

Release Date
  • 2026-08-10
New Feature
  • Improve MQTT node data transfer with a compact binary format.
  • Fix stored messages so a replayed message carries the same content as one published immediately.
  • Improve Store & Forward diagnostics with deduplicated disconnect alerts and forwarding progress logs.
Bug Fixes
  • Fix Store & Forward to persist messages during a broker outage.

V1.1.4

Release Date
  • 2026-08-10
Bug Fixes
  • Fix unexpected application termination when the secret service is unavailable. The application now reports an appropriate error instead of terminating unexpectedly when the required secret service is unavailable.

V2.0.1

Release Date
  • 2026-05-04
New Feature
  • Add store-and-forward delivery for offline message queuing.
Improvements
  • Standardize runtime error messages.

V2.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish
  • Optimize Store and Forward behavior
Bug Fix
  • Store and Forward related

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Send telemetry from the gateway to the MQTT Broker as a publisher
  • Auto-reconnect
  • Store and Forward
  • Authentication: None, Password, X.509

V1.1.4

Release Date
  • 2026-03-16
Bug Fix
  • Slave ID Inputs Validation: Corrects the validation logic to prevent the system from accepting invalid Slave IDs.

V1.1.3

Release Date
  • 2026-03-02
Bug Fix
  • Tag Configuration: Resolved an issue where Swapping settings were not correctly applied to String type tags.
  • Write Functionality: Fixed a bug that prevented writing to a Single Register when the Swapping configuration was enabled.

V1.1.2

Release Date
  • 2026-02-09
Bug Fix
  • Modbus Communication: Resolved an issue where the Modbus TCP Client used a fixed Slave ID regardless of configuration; dynamic Slave ID assignment has been restored.
  • Connection Stability: Fixed a critical bug where full buffers in Modbus applications caused permanent connection loss; the system now correctly handles buffer limits to maintain continuous communication.
  • Data Integrity: Corrected the data type configuration for “Raw” type tags within Modbus applications to ensure accurate data processing and prevent type-related errors.

V1.1.1

Release Date
  • 2025-09-30
Bug Fix
  • Logic error resolved: Resolved a logic error in Modbus applications when processing write-type commands, preventing invalid commands or abnormal data

V1.0.3

Release Date
  • 2025-03-03
Bug Fix
  • Raw values could not be parsed into string values.

V1.0.2

Release Date
  • 2025-02-03
Bug Fix
  • The devices and profiles registered by other OT applications were deleted after ‘device-neoedgex-modbustcp’ initialization.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Send telemetry from the gateway to the MQTT Broker as a publisher
  • Auto-reconnect
  • Store and Forward
  • Authentication: None, Password, X.509

V1.1.4

Release Date
  • 2026-03-16
Bug Fix
  • Stop Bit Configuration: Fixes a bug where changes to the stop bit settings were not being correctly applied to the communication interface.
  • Slave ID Inputs Validation: Corrects the validation logic to prevent the system from accepting invalid Slave IDs.

V1.1.3

Release Date
  • 2026-03-02
Bug Fix
  • Tag Configuration: Resolved an issue where Swapping settings were not correctly applied to String type tags.
  • Write Functionality: Fixed a bug that prevented writing to a Single Register when the Swapping configuration was enabled.

V1.1.2

Release Date
  • 2026-02-09
Bug Fix
  • Connection Stability: Fixed a critical bug where full buffers in Modbus applications caused permanent connection loss; the system now correctly handles buffer limits to maintain continuous communication.
  • Data Integrity: Corrected the data type configuration for “Raw” type tags within Modbus applications to ensure accurate data processing and prevent type-related errors.

V1.1.1

Release Date
  • 2025-09-30
Bug Fix
  • Logic error resolved: Resolved a logic error in Modbus applications when processing write-type commands, preventing invalid commands or abnormal data

V1.0.3

Release Date
  • 2025-03-03
Bug Fix
  • Raw values could not be parsed into string values.

V1.0.2

Release Date
  • 2025-02-03
Bug Fix
  • The devices and profiles registered by other OT applications were deleted after ‘device-neoedgex-modbustcp’ initialization.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Support Function Code
  • Support invocation via RESTful API
  • Max 2048 tags per slave device
  • Maximum 64 slave devices per gateway
  • Multi-threaded software architecture for high performance and throughput

V2.2.2

Release Date
  • 2026-09-07
Bug Fixes
  • Fix bool tag writes that failed when using the Write Multiple Coils function.

V2.2.1

Release Date
  • 2026-08-24
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V2.2.0

Release Date
  • 2026-08-10
New Feature
  • Improve Modbus node data transfer with a compact binary format.
  • Fix Modbus write commands to report an error instead of writing a value that does not match the tag type.
  • Support the node name prefix option for Modbus tag keys in published data and write commands.

V2.1.0

Release Date
  • 2026-07-13
New Features
  • Support bulk-read aggregation of adjacent Modbus read tags to reduce device polling requests.

V2.0.1

Release Date
  • 2026-05-04
Improvements
  • Standardize runtime error messages.

V2.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V1.1.2

Release Date
  • 2026-03-16
Bug Fix
  • Timestamp Accuracy: Fixes a bug where tags were recorded with incorrect timestamps.
  • Slave ID Inputs Validation: Corrects the validation logic to prevent the system from accepting invalid Slave IDs.

V1.1.1

Release Date
  • 2025-11-03
Bug Fix
  • Fixed an issue where the application was unable to correctly publish non-all-domain tags, ensuring that data publishing behavior is consistent with configuration.

V1.0.2

Release Date
  • 2025-02-03
Bug Fix
  • The devices and profiles registered by other OT applications were deleted after ‘device-neoedgex-modbustcp’ initialization.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Support Function Code
  • Support invocation via RESTful API
  • Max 2048 tags per slave device

V2.3.0

Release Date
  • 2026-08-24
New Features
  • Support custom payload configuration for HTTP client forwarder nodes.
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V2.2.0

Release Date
  • 2026-08-10
New Feature
  • Improve HTTP Client node data transfer with a compact binary format.
  • Fix stored messages so a replayed message carries the same content as one sent immediately.

V2.1.0

Release Date
  • 2026-05-18
New Feature
  • Add store-and-forward for offline message queuing.

V2.0.1

Release Date
  • 2026-05-04
New Feature
  • Add concurrent request handling.
Improvements
  • Reduce memory consumption under load.
  • Standardize runtime error messages.

V1.1.1

Release Date
  • 2026-05-04
Improvements
  • Enhance HTTP forwarding resilience by processing outbound requests with 8 workers and implementing a 30-second request timeout. This approach mitigates the impact of slow or unresponsive downstream endpoints.
  • Add bounded input cache behavior that keeps up to 1024 readings and prioritizes the latest data when forwarding falls behind.
  • Add StoreForward fallback for input cache overflow so the oldest cached readings can be preserved when StoreForward is available.
Bug Fix
  • Fix outbound HTTP requests to consistently send request bodies with them Content-Length instead of unexpectedly using Transfer-Encoding: chunked.
  • Fix unbounded input cache growth that could contribute to high memory consumption when HTTP forwarding cannot keep up with incoming data.

V2.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-11-29
Bug Fix
  • Data in the memory queue is not stored when the application is terminated

V1.0.0

Release Date
  • 2024-11-01
New Feature
  • Support POST and PUT methods
  • Support public and private TLS connections
  • Support ignoring TLS verification
  • Support Store & Forward
  • Support Client Authentications: None, X.509 Certificate
  • Support custom HTTP headers

V1.0.0

Release Date
  • 2025-03-31
  • Technical Doc: https://www.ecloudedge.com/gateway-metrics-%e8%aa%aa%e6%98%8e/
New Feature
  • Capability to fetch gateway metrics results via NeoEdgeX Agent, and send the metrics to EdgeX Core Data.

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-11-29
Improvements
  • Determine whether empty event should be inserted to the endpoint database

V1.0.0

Release Notes
  • 2024-11-18
New Feature
  • Send telemetry from the gateway to MS-SQL
  • Support TLS connection
  • Auto-reconnect
  • Store and Forward
  • Authentication Method: username/password

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-11-29
Improvements
  • decide if an empty event should be added to the endpoint database

V1.0.0

Release Date
  • 2024-11-18
New Feature
  • Send telemetry from the gateway to MySQL.
  • Support TLS connection
  • Auto-reconnect
  • Store and Forward
  • Authentication Method: username/password

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-11-29
Improvements
  • decide if an empty event should be added to the endpoint database

V1.0.0

Release Date
  • 2024-11-18
New Feature
  • Send telemetry from the gateway to PostgreSQL
  • Support TLS connection
  • Auto-reconnect
  • Store and Forward
  • Authentication Method: username/password

V2.2.0

Release Date
  • 2026-08-24
New Features
  • Support custom payload configuration for Azure IoT Hub forwarder nodes.
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V2.1.0

Release Date
  • 2026-08-10
New Features
  • Improve Azure IoT Hub node data transfer with a compact binary format.

V2.0.1

Release Date
  • 2026-05-04
Improvements
  • Standardize runtime error messages.

V2.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V1.0.2

Release Date
  • 2025-03-03
Bug Fix
  • Duplicate messages were sent to the endpoint.

V1.0.1

Release Date
  • 2024-10-08
Improvements
  • Live Monitor Publish
  • Optimize Store and Forward behavior
Bug Fix
  • Store and Forward related

V1.0.0

Release Date
  • 2024-09-09
New Feature
  • Send telemetry from a gateway to Azure IoT Hub as a client device
  • Auto-reconnect
  • Store and Forward
  • Authentication: symmetric key, X.509

V1.0.2

Release Date
  • 2026-03-16
Improvements
  • License Quantity Validation: The app no longer performs validation checks on the License Quantity field during the license verification process.

V1.0.1

Release Date
  • 2025-12-15
Improvements
  • Add support for configuring the location field in the PRiSM process.

V1.0.0

Release Date
  • 2025-12-02
New Feature
  • Automate the PRiSM app process by integrating it into the NeoFlow system for streamlined execution and monitoring.

V1.2.1

Release Date
  • 2026-08-24
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.

V1.2.0

Release Date
  • 2026-08-10
New Features
  • Improve OPC UA node data transfer with a compact binary format.
  • Fix OPC UA write commands to report an error instead of sending a value that does not match the tag type.
  • Support the node name prefix option for OPC UA tag keys in published data and write commands.

V1.1.2

Release Date
  • 2026-06-29
Bug Fix
  • OPC UA secure connections are no longer rejected by servers that strictly validate the client certificate. The gateway now generates and renews its own OPC UA-compliant certificate.
  • OPC UA connection and tag-read errors now explain the likely cause and suggested action instead of raw protocol codes.
  • Long lists of failing tags in OPC UA error messages are now truncated for readability.

V1.1.1

Release Date
  • 2026-05-18
New Feature
  • Self-sign and persist the OPC UA application certificate automatically.
Bug Fix
  • Improve OPC UA error messages.

V1.1.0

Release Date
  • 2026-05-04
New Feature
  • Add per-node authentication mode (none, password, X.509) and transport security selection.
  • Support legacy security policies (Basic256, Basic128Rsa15).
Improvements
  • Standardize runtime error messages.
Bug Fix
  • Accept all configured security policy values, including mixed-case wire strings.

V1.0.0

Release Date
  • 2026-04-08
New Feature

Welcome to NeoEdge 4.0: A Whole New Experience

  • NeoEdge 4.0 Compatibility: To support the transition to NeoEdge 4.0, we have introduced the dedicated connector application to ensure full compatibility with the NeoEdge 4.0 ecosystem.

V2.1.1

Release Date
  • 2026-08-24
Bug Fixes
  • Improve NeoFlow message timestamps to millisecond precision in UTC.
  • Change numeric tag values in forwarded payloads to fixed-point decimal notation.

V2.1.0

Release Date
  • 2026-08-10
New Feature
  • Improve Processor node data transfer with a compact binary format.
  • Change Condition node evaluation so a tag the upstream node never sent counts as not existing.
Breaking Changes
  • Change NeoFlow formula validation and gateway execution to the unified double-brace tag and function syntax.
Upgrade Notes
  • Re-enter NeoFlow tag and function references after upgrade; the previous forms are no longer recognized.

V2.0.1

Release Date
  • 2026-05-04
Bug Fixes
  • Fix floating-point precision loss in formula calculations.
  • Fix tumbling window drift between processing passes.
Maintenance
  • Standardize runtime error messages.