Link IoT Edge Standard Edition (LE Standard) is available as a self-contained software package.
You can download the self-contained software package for each version from the download page.
The Standard Edition has the following environment requirements:
- x86_64 Linux: Requires Linux kernel version 2.6.32 or later.
- ARMv7 VFPv3 hard-float, Linux: Requires Linux kernel version 2.6.32 or later.
- ARMv8_64 Linux: Requires Linux kernel version 2.6.32 or later.
To learn how to set up the environment and use the Standard 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 series includes all features supported by Link IoT Edge Standard Edition. Compared with the v2.1.x series, this series adds a Java device software development kit (SDK), two edge HTTP APIs, and support for Elliptic Curve Cryptography (ECC) encryption for device connections. It also optimizes the performance of drivers and scripts, and improves the management of Link IoT Edge services. 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 might fail to connect to the cloud if the Domain Name System (DNS) address is changed after Link IoT Edge starts. |
| v2.4.7 | 2020-07-29 | [Fixed] Fixed issues such as incorrect sub-device status at the edge during a network disconnection.
Note To better experience the features of Link IoT Edge, upgrade from v2.4.6 directly to v2.4.7. |
| v2.4.5 | 2020-05-20 | [Fixed] Fixed an issue that caused Link IoT Edge services to fail intermittently on startup. |
| v2.4.4 | 2020-05-08 | [Fixed] Fixed issues such as failures and errors when you enable remote access. |
| v2.4.3 | 2020-04-10 | [Fixed] Fixed an intermittent issue where sub-devices could not go back online after a network reconnection. |
| v2.4.2 | 2020-03-17 | - [Added] Added a Java device SDK.
- [Fixed] Fixed an issue where the Link IoT Edge version, specifications, and CPU architecture were lost when the gateway was restored to its default configurations.
- [Optimized] The iot_gateway_stop.sh script can now purge remote O&M channels.
|
| v2.4.1 | 2020-02-06 | - [Added] Added support for devices to use ECC certificates for mutual authentication when connecting to the cloud.
- [Fixed] Fixed some issues found in v2.4.0.
|
| v2.4.0 | 2019-12-16 | - [Added] Added the `ListThings` and `InvokeFunction` APIs to the edge HTTP API.
- [Fixed] Fixed an issue where devices went offline after their device tags were changed and deployed.
- [Fixed] Fixed an issue where the edge repeatedly reconnected to the cloud after the remote access connection was actively disconnected from the cloud.
- [Fixed] Fixed an issue where the polling time of the official Modbus driver could only dynamically increase and not decrease.
- [Fixed] Fixed a service monitoring timestamp overflow issue that caused display errors in the console.
- [Optimized] Optimized the driver license security protection mechanism.
- [Optimized] Unified the management of Link IoT Edge services through the `linkedged` process.
|
v2.1.x series
This series includes all features supported by Link IoT Edge Standard Edition. Compared with non-LTS versions, this series optimizes the device online mechanism, remote access capabilities, and the architecture and performance of scene orchestration. It also fixes 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 such as failures and errors when you enable remote access. |
| v2.1.3 | 2020-04-10 | - [Fixed] Fixed an issue where an error occurred if the `DeviceName` request parameter of the edge HTTP API contained a hyphen (-), an at sign (@), or a period (.).
- [Fixed] Fixed an intermittent issue where sub-devices could not go back online after a network reconnection.
|
| v2.1.2 | 2019-11-26 | - [Fixed] Fixed an issue where updating and deploying a driver in an edge instance, for example, by updating configurations or adding or deleting sub-devices, affected the status of sub-devices that use other drivers.
- [Optimized] Optimized the traffic consumption of the remote access feature.
- [Optimized] Reduced the reconnection interval for the remote access feature.
- [Optimized] Configured the Link IoT Edge stop script iot_gateway_stop.sh to not stop (kill) the `RemoteTerminalDaemon` process by default.
- [Optimized] Updated the rules for resumable data transfer after a network disconnection. If the cloud returns an unrecoverable error, messages related to that error are not reported when the transfer resumes.
|
| v2.1.1 | 2019-10-11 | - [Fixed] Fixed some issues found in v2.1.0.
- [Optimized] Optimized the deployment flow for edge instances in poor network conditions.
|
| v2.1.0 | 2019-08-30 | - [Fixed] Increased the maximum size of data that can be reported to IoT Platform from 64 KB to 256 KB.
- [Optimized] Added a retry mechanism for sub-devices that fail to go online in poor network conditions.
- [Optimized] Optimized the architecture and performance of scene orchestration.
- [Optimized] Optimized traffic overhead in 4G and LTE environments.
|
Non-LTS versions
The non-LTS versions of Link IoT Edge are shown in the following table.
| Version number | Release date | Version guide |
| v2.9.7 | 2021-01-05 | [Fixed] Fixed an issue where remote O&M might fail to connect to the cloud if the DNS address is changed after Link IoT Edge starts. |
| v2.9.2 | 2020-07-29 | [Fixed] Fixed issues such as incorrect sub-device status at the edge during a network disconnection. |
| v2.9.0 | 2020-06-12 | - [Added] Added an edge gateway console.
- [Added] Scene orchestration now supports calls to Function Compute.
- [Added] Added an integrated cloud-edge alerting center.
- [Added] The Modbus driver now supports the LoRa LAN communication channel.
- [Added] Added support for over-the-air (OTA) updates for LoRa sub-devices.
- [Optimized] Optimized 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 of registers.
- [Fixed] Fixed issues found since v2.4.0.
|