This topic lists the release history of Link IoT Edge Professional Edition (LE Pro). LE Pro is released as a Docker image and currently supports only the x86 platform.
For more information about how to set up the environment and use the Professional Edition, see the User Guide.
Note - If you are a new user, use the latest version of the most recent series.
- If you are an existing user, select a version based on the following guidelines:
- If you use a Long-Term Support (LTS) version, use the latest version of that series.
- If you use a non-LTS version, upgrade to the latest LTS version.
v2.4.x series
This version includes all the features of Link IoT Edge Pro Edition. Compared to the v2.1.x series, this version adds a Java SDK for device access, exposes two edge HTTP APIs, supports ECC encryption for device access, and optimizes the performance of drivers and scripts, along with the management of the Link IoT Edge service. For more information, see the following table.
| Version number | Release date | Version guide |
| v2.4.9 | 2021-01-05 | - [Fixed] Fixed an issue where remote O&M may fail to connect to the cloud if the Domain Name System (DNS) address is changed after Link IoT Edge starts.
- [Fixed] Fixed an issue where the failover with hot replica feature may fail to start after the gateway is restarted due to a power outage.
|
| v2.4.7 | 2020-07-29 | [Fixed] Fixed an issue where the status of a sub-device on the edge is incorrect when the network is disconnected.
Note To better experience the features of Link IoT Edge, upgrade from v2.4.6 to v2.4.7. |
| v2.4.5 | 2020-05-20 | [Fixed] Fixed an issue where an error may occur when the Link IoT Edge service starts. |
| v2.4.4 | 2020-05-08 | [Fixed] Fixed issues where remote access fails to open or an error occurs during access. |
| v2.4.3 | 2020-04-10 | - [Fixed] Fixed an issue where an error occurs if the DeviceName request parameter of an edge-side HTTP API contains a hyphen (-), an at sign (@), or a period (.).
- [Fixed] Fixed an issue where a sub-device may fail to go back online after the network reconnects.
|
| v2.4.2 | 2020-03-17 | - [New] Added a Java device SDK.
- [Fixed] Fixed an issue where the Link IoT Edge version, specifications, and CPU architecture are lost when the default gateway configurations are restored.
- [Optimized] The iot_gateway_stop.sh script can now purge remote O&M channels.
|
| v2.4.1 | 2020-02-06 | - [New] Devices can now use ECC certificates for mutual authentication to connect to the cloud.
- [Fixed] Fixed some issues found in v2.4.0.
|
| v2.4.0 | 2019-12-16 | - [New] Added the ListThings and InvokeFunction APIs to the edge-side HTTP API.
- [Fixed] Fixed an issue where a device goes offline after its device tag is changed and the change is deployed.
- [Fixed] Fixed an issue where the edge side repeatedly reconnects to the cloud after the cloud actively disconnects the remote access connection.
- [Fixed] Fixed an issue where the polling time of the official Modbus driver only dynamically increases and does not decrease.
- [Fixed] Fixed an issue where a service monitoring timestamp overflow causes display errors in the console.
- [Optimized] Improved the security protection mechanism for driver licenses.
- [Optimized] The linkedged process now centrally manages Link IoT Edge services.
|
v2.1.x series
This version includes all the product capabilities of Link IoT Edge Pro Edition. Compared to non-LTS versions, this version optimizes the device onboarding mechanism, remote access capabilities, and the architecture and performance of scene orchestration. It also resolves issues found in non-LTS versions. For more information, see the following table.
| Version number | Release date | Version guide |
| v2.1.4 | 2020-05-08 | [Fixed] Fixed issues where remote access fails to open or an error occurs during access. |
| v2.1.3 | 2020-04-10 | - [Fixed] Fixed an issue where an error occurs if the DeviceName request parameter of an edge-side HTTP API contains a hyphen (-), an at sign (@), or a period (.).
- [Fixed] Fixed an issue where a sub-device may fail to go back online after the network reconnects.
|
| v2.1.2 | 2019-11-26 | - [Fixed] Fixed an issue where updating and deploying a driver in an edge instance, such as updating configurations or adding or deleting sub-devices, affects the status of sub-devices of other drivers.
- [Optimized] Function Compute containers can now run on Kubernetes.
- [Optimized] Reduced the traffic consumption of the remote access feature.
- [Optimized] Reduced the reconnection interval for the remote access feature.
- [Optimized] By default, the Link IoT Edge stop script iot_gateway_stop.sh no longer stops (kills) the RemoteTerminalDaemon process.
- [Optimized] Updated the rules for data resubmission after a network disconnection. If the cloud returns an unrecoverable error, messages related to that error are not reported during data resubmission.
|
| v2.1.1 | 2019-10-11 | - [Fixed] Fixed some issues found in v2.1.0.
- [Optimized] Improved the process of deploying edge instances in weak network conditions.
|
| v2.1.0 | 2019-08-30 | - [Fixed] Increased the maximum length of data that can be reported to IoT Platform from 64 KB to 256 KB.
- [Fixed] Fixed an issue where data reported by drivers developed with the Python SDK contains garbled Chinese characters.
- [Fixed] Fixed an issue where the process may unexpectedly exit when drivers developed with the Python SDK go online concurrently.
- [Changed] The default isolation method for functions in Function Compute is changed from process to container. Each function or driver that you deploy runs in a separate container.
- [Optimized] Added a retry mechanism for sub-devices that fail to go online in weak network conditions.
- [Optimized] Improved the architecture and performance of scene orchestration.
- [Optimized] Reduced traffic overhead in 4G and LTE environments.
|
Non-LTS versions
The following table lists the non-LTS versions of Link IoT Edge.
| Version number | Release date | Version guide |
| v2.9.7 | 2021-01-05 | - [Fixed] Fixed an issue where remote O&M may fail to connect to the cloud if the DNS address is changed after Link IoT Edge starts.
- [Fixed] Fixed an issue where the failover with hot replica feature may fail to start after the gateway is restarted due to a power outage.
|
| v2.9.2 | 2020-07-29 | [Fixed] Fixed an issue where the status of a sub-device on the edge is incorrect when the network is disconnected. |
| v2.9.0 | 2020-06-12 | - [New] Added an edge gateway console.
- [New] Scene orchestration now supports invoking Function Compute.
- [New] Added an integrated cloud-edge alerting center.
- [New] The Modbus driver now supports LoRa LAN communication channels.
- [New] Added support for over-the-air (OTA) updates for LoRa sub-devices.
- [Optimized] Improved message routing configurations. You can now select multiple products and devices as message sources.
- [Optimized] The Modbus driver now supports read-only and bitwise parsing for registers.
- [Fixed] Fixed issues found since v2.4.0.
|