This document details the new features in each version of the IoT Platform device SDK and explains how to enable them.
New features in SDK V1.6.6
To update to the latest version (1.6.6-21), run git pull on the rel_1.6.6 branch.
Version |
Description |
1.6.6-22 |
|
1.6.6-21 |
|
1.6.6-20 |
|
1.6.6-19 |
|
1.6.6-16 |
|
1.6.6-15 |
|
1.6.6-12 |
|
1.6.6-10 |
|
1.6.6-9 |
|
1.6.6-8 |
Optimized the local timer.
|
1.6.6-6 |
|
1.6.6-5 |
|
1.6.6-4 |
|
1.6.6 |
|
New features in SDK V1.6.2
Added support for gateways to batch-request and asynchronously receive sub-device triplets.
Added support for gateways to bring sub-devices online in batches.
Added support for adapting the non-AliOS Things SDK to FreeRTOS.
For more information, see SDK Adaptation Guide for Non-AliOS Things.
Added support for authorized access to on-device sound pickup and rhythm effects for lighting products.
New features in SDK V1.6.0
Support for the global unified activation center
If you set the default_region parameter to SINGAPORE or MAINLAND when you compile the firmware, the device can be used globally.
Optimized device reconnection policy
This feature, enabled by default, optimizes the cloud reconnection strategy after an MQTT disconnection.
Optimized duration for Bluetooth-assisted network configuration
This feature, enabled by default, reduces the total time required for Bluetooth-assisted network configuration and binding.
Offline network configuration and control with Bluetooth assistance
This feature allows devices to complete network configuration even with an unreliable internet connection, and enables the app to control them via Bluetooth.
Device local clock synchronization service
This feature provides a time synchronization mechanism between devices for scenarios such as synchronizing group-controlled lights.
New features in SDK V1.5.0
Optimized local group control
This feature, enabled by default, improves local group control performance and can enhance the synchronization of group control and group rhythm for lighting products.
Device certificate distribution tool
For more information, see Device Certificate Distribution Tool Guide.
Offline factory reset
This feature allows a factory reset to be triggered on an offline device. The device executes the reset after it comes back online.
New features in SDK V1.4.0
Support for the unified activation center for gateways and sub-devices
Version 1.4.0 refactors the gateway reference application to allow sub-devices outside the Chinese mainland to switch data centers. To enable this feature, use the following configurations.
If you are developing with the AliOS version of the SDK, you need to set FEATURE_DM_UNIFIED_SERVICE_POST in the Products/example/linkkit_gateway/make.settings file to y.

If you are developing based on the non-AliOS Things version of the SDK, edit the
make.settingsfile in the root directory and addFEATURE_DM_UNIFIED_SERVICE_POST=y. For more information, see Gateway Development.
Device offline log feature
For devices that support device hotspot network configuration, if the configuration or binding process fails, the app guides the user to run diagnostics. The device sends key logs—such as error codes, cloud-reported tokens, and the time taken to acquire an IP address—to the app. The app then uploads these logs to the cloud. You can view the logs on the device management page in the IoT Platform console to facilitate remote O&M.
To enable this feature, add the configuration item
GLOBAL_CFLAGS += -DDEV_OFFLINE_LOG_ENABLEto your application'smkfile. If you are developing based onlinkkit_gateway, this configuration is already included in thelinkkit_gateway.mkfile, as shown in the following figure.
NoteThis feature uses approximately 4 KB of code space and 3 KB of RAM. The RAM is released immediately after diagnostics are complete. If diagnostics are not run, the RAM is released five minutes after power-on. Evaluate your resource availability before enabling this feature.
Optimized device hotspot network configuration
This default optimization reduces the connection time to data centers outside the Chinese mainland when using device hotspot network configuration.
Optimized Bluetooth-assisted network configuration
This optimization reduces the connection time to data centers in countries and regions outside the Chinese mainland (including Hong Kong, Macao, and Taiwan regions of China) using Bluetooth-assisted network configuration. It also retrieves and displays device self-check information when exceptions occur during the configuration process, allowing detailed error information to be viewed on the mobile app. These features for Bluetooth-assisted network configuration are enabled by default in the comboapp sample application, meaning the following configuration items are enabled in
comboapp.mk.GLOBAL_CFLAGS += -DAWSS_REGION_ENABLE GLOBAL_CFLAGS += -DDEV_ERRCODE_ENABLENoteFor devices that use Bluetooth-assisted network configuration, refer to the comboapp sample application for development.
Diagnostics for device-to-router connection failures
This feature, enabled by default, allows the device to run a self-check and analyze the specific cause of a router connection failure during Wi-Fi network configuration. The detailed error code is then displayed on the mobile app.
Wi-Fi production line testing tool module
Description: This feature is enabled by default as a standalone testing tool module. The application layer can call this module to search for details of a specified router.
The default maximum search time is 3 seconds.
Checks if the router can be found.
Checks if the router's signal strength is too weak.
Returns the result to the application layer when the specified router is found.
Limitations
Cannot be used when the device is in hotspot mode.
Cannot be used when the device is connected to a router.
Cannot be used in network configuration mode.
Sample code:
For usage examples, see the implementation in the
app_entry.cfile of theliving_platformsample application.#define TEST_LINE_AP "ali_product_line_test" #define TEST_RSSI_THRESHOLD (-60) static void handle_apscan_cmd(char *pwbuf, int blen, int argc, char **argv) { int ret = 0; ap_scan_info_t scan_result; int ap_scan_result = -1; if (argc == 0) { // start ap scanning for default 3 seconds memset(&scan_result, 0, sizeof(ap_scan_info_t)); ap_scan_result = awss_apscan_process(NULL, TEST_LINE_AP, &scan_result); if ( (ap_scan_result == 0) && (scan_result.found) ) { aos_cli_printf("AP Info: auth(%d) chan(%d) mac(%02X:%02X:%02X:%02X:%02X:%02X) rssi(%d)\r\n", scan_result.auth, scan_result.channel, scan_result.mac[0], scan_result.mac[1], scan_result.mac[2], scan_result.mac[3], scan_result.mac[4], scan_result.mac[5], scan_result.rssi); if (scan_result.rssi < TEST_RSSI_THRESHOLD) { aos_cli_printf("AP_SCAN AP rssi too low\r\n"); } else { aos_cli_printf("AP_SCAN AP found\r\n"); } } else { aos_cli_printf("AP_SCAN AP not found\r\n"); } } }After powering on a device running the
living_platformapplication, enter the commandapscanto trigger a check for the specified router.If the detected AP's RSSI is too low, the device logs the message:
AP_SCAN AP rssi too low.If the AP is detected and its RSSI is sufficient, the device logs the message:
AP_SCAN AP found.If the AP is not detected, the device logs the message:
AP_SCAN AP not found.
New features in SDK V1.3.0
Batch network configuration for production lines
Device manufacturers can connect devices to a designated production testing router on the assembly line. When this feature is enabled, the device automatically connects to the router within 3 seconds of power-on. This feature is disabled by default. To enable it, follow these steps.
Add the configuration item
GLOBAL_CFLAGS += -DMANUFACT_AP_FIND_ENABLEto the application'smkfile.Change the production testing router's SSID and password in the
app_entry.cfile.The default SSID is
ali_mprov_TEST_AP, whereali_mprov_is a prefix automatically added by the module andTEST_APis a field that developers can customize.The default password is
TEST_PASSWORD.
NoteThis feature will not be enabled if the application-level SSID or router password fields are empty. If a correct SSID and password are set, the device searches for this router upon power-on in an unconfigured state. If found, it connects; otherwise, it proceeds to the standard network configuration mode.
Batch network configuration for end users
Supports quick batch network configuration for multiple devices of the same model by end users via the app. Devices must support device hotspot network configuration or zero-configuration networking. A maximum of 20 devices can be configured in a single batch.
To enable this feature, add the configuration item
GLOBAL_CFLAGS += -DAWSS_BATCH_DEVAP_ENABLEto the application'smkfile. If you are developing based onliving_platform, this configuration is already included in theliving_platform.mkfile, as shown in the following figure.
Error code diagnostics for device hotspot network configuration
This feature displays exceptions that occur while the device is connecting to a router or the cloud via device hotspot network configuration. Exceptions can be viewed in the app's "Error Diagnosis" function.
To enable this feature, add the configuration item
GLOBAL_CFLAGS += -DDEV_ERRCODE_ENABLEto the application'smkfile. If you are developing based onliving_platform, this configuration is already included in theliving_platform.mkfile, as shown in the following figure.
Local group control and group rhythm
This feature enables synchronized rhythm effects for devices within a group of lighting products.
To enable this feature, follow these steps.
Make sure that the local communication feature is enabled, which means that in the make.settings file, FEATURE_ALCS_ENABLED is set to y, as shown in the following figure.

Add configuration items to the application's mk file. If you are developing based on living_platform, add the following configurations to the
living_platform.mkfile.GLOBAL_CFLAGS += -DALCS_GROUP_COMM_ENABLE GLOBAL_CFLAGS += -DDM_UNIFIED_SERVICE_POST
Offline OTA
This feature provides a way to repair firmware with an update if the device fails during network configuration or cloud connection in device hotspot mode. Both standard and secure offline OTA updates are supported.
To enable this feature, add the configuration item
GLOBAL_CFLAGS += -DDEV_OFFLINE_OTA_ENABLEto the application'smkfile. If you are developing based onliving_platform, this configuration is already included in theliving_platform.mkfile, as shown in the following figure.
You can also enable secure signature verification for offline OTA by following these steps.
Add the configuration item
GLOBAL_CFLAGS += -DDEV_OFFLINE_SECURE_OTA_ENABLEto the application'smkfile.Obtain the product's public key. In the IoT Platform console, navigate to the page. Enable the secure upgrade switch for the corresponding product and click Copy.
In the
Living_SDK/framework/uOTA/src/verify/ota_public_key_config.hfile, replace the two lines of data indicated by the red box in the following figure with the public key information you copied.
Optimized token for Wi-Fi device zero-configuration networking
This feature allows the app to generate and transmit a binding token to the device during the zero-configuration networking process, which resolves binding failures caused by a router's AP isolation mode.
To enable this feature, add the configuration item
GLOBAL_CFLAGS += -DAWSS_ZCONFIG_APPTOKENto the application'smkfile. If you are developing based onliving_platform, this configuration is already included in theliving_platform.mkfile, as shown in the following figure.
New features in SDK V1.1.0
Unified activation for devices outside the Chinese mainland
There are three data centers outside the Chinese mainland: Singapore, US, and Germany. Devices outside the Chinese mainland will connect to the Singapore activation center during network activation. When the device is bound, the platform automatically switches it to the appropriate data center based on the app user's region. For more information, see Compile based on V1.1.0 SDK (linkkitapp).
Timer component
Added support for parsing simple product models for countdown, local, periodic, and random timers.
Optimized cloud connection
Improved device-to-cloud connection speed.
Optimized network configuration and binding
Implemented multicast encoding for one-click network configuration to prevent binding failures caused by AP isolation and improve the binding success rate.
Added Bluetooth-assisted network configuration.
Added encrypted password storage.
Added notifications for successful binding and unbinding events.



