Device Management Client 4.13.2 General Availability

Device Management Client example

Changes

• Extend the lifetime from 3 minutes to 2 hours. Default lifetimes that are too frequent can deplete battery-operated devices. It needs to be adjusted according to the specific usage scenario of the device.

Release notes can be found here:
https://developer.izumanetworks.com/docs/device-management/current/release-notes/device-management-client.html

Device Management Client 4.13.1 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. The default DNS setting was changed to synchronous DNS.

Changes

• Updated mbedTLS from 2.28.1 to 2.28.2 for Linux targets and updated GitHub domain for it (from ArmMbed to Mbed-TLS).
• Updated libcurl from 7.85.0 to 7.87.0 for Linux targets.

Release notes can be found here:
https://developer.izumanetworks.com/docs/device-management/current/release-notes/device-management-client.html

Device Management Client 4.13.0 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
  • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
  • For Zephyr devices, set the DNS API selection to POSIX.

Changes

• [Mbed OS] Add DISCO_L496AG board. The cellular settings are for example only.
• Enable EST flow for LWM2M_COMPLIANT mode.
• Enable server certificate verification in LWM2M_COMPLIANT mode.
• [Mbed OS] New feature for migrating the bootstrap server URI to another URI.
  • This allows moving a device from one Device Management region to another, for example from the US to the EU.
  • Works only with KVStore-based storage.
  • More details in PDMC Migration Tutorial document.
• Updated libcurl from 7.76.0 to 7.85.0 for Linux targets.
• Updated mbedTLS from 2.27.0 to 2.28.1 for Linux targets.
• Branding changes to Izuma.
• Add the following files to .gitignore:
  • mbed_cloud_client_user_config.h
  • mbed_cloud_dev_credentials.c and
  • update_default_resources.c to minimize the risk of leaking credentials/private configs.
  • You can still update these files if you wish, but you have to use git add -f <file>.
• Zephyr OS updated to 2.7.3.
• Alternating port fallback config example for MBED_CLOUD_CLIENT_CUSTOM_URI_PORT added to mbed_cloud_client_user_config.h.
  • If a socket error is encountered, the next try will be done with the original CoaP port 5684.
  • After 2nd fail we alternate back to the custom port.
  • NOTE! Only port 443 can be used as an alternative customer port with Izuma Networks.

Release notes can be found here:
https://developer.izumanetworks.com/docs/device-management/current/release-notes/device-management-client.html

Device Management Client 4.12.0 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
  • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
  • For Zephyr devices, set the DNS API selection to POSIX.

Changes

• Updated to Mbed OS 6.15.1.
• [Linux] Add a new define_lwm2m_compliant.txt that enables communication with a LwM2M compliant service / interoperability (IoP) testing.
• [Mbed OS] Add a new mbed_app_lwm2m_compliant.json that enables communication with an LwM2M compliant service/interoperability (IOP) testing with FRDM K64F device.

Device Management Client 4.11.2 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
  • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
  • For Zephyr devices, set the DNS API selection to POSIX.

Changes

• Updated to Mbed OS 6.15.0.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 4.11.1 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
  • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
  • For Zephyr devices, set the DNS API selection to POSIX.

Changes

• Updated Parsec to 0.6.0 version. This version is compatible with Mbed TLS 2.27.0.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 4.11.0 General Availability

Device Management Client example

Known issues

• [Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
  • For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
  • For Zephyr devices, set the DNS API selection to POSIX.

Changes

• Application restructuring:
  • M2MInterfaceFactory::create_resource() function used for creating object and resources.
  • Replaced the deprecated status APIs with the on_status_changed() API.
  • Removed the MCC_MEMORY flag.
  • Replaced the MCC_MINIMAL flag with the PDMC_EXAMPLE_MINIMAL flag.
• Updated to Mbed OS 6.14.0.
• Updated Mbed TLS to 2.27.0 in pal-platform.
• Added a demonstration of FOTA component update. Placed component registration and callback examples in source/fota_platform_hooks_imp.cpp.
• [Linux] Added demonstration of FOTA combined update. Placed subcomponent registration and callback examples in source/fota_platform_hooks_imp.cpp under the MBED_CLOUD_CLIENT_FOTA_SUB_COMPONENT_SUPPORT flag.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 4.10.0 General Availability

Device Management Client example

Changes

• Configured the NXP_LPC54628 target to use the new upgraded Update client.

• Updated mesh configuration in mesh_wisun.json based on the new Update client implementation.

• Introduced new bootloaders for devices that use candidate image encryption.
  Replaced FOTA_USE_DEVICE_KEY with FOTA_USE_ENCRYPTED_ONE_TIME_FW_KEY as the default value for MBED_CLOUD_CLIENT_FOTA_KEY_ENCRYPTION due to a security vulnerability found in FOTA_USE_DEVICE_KEY.

  This is a breaking change for Mbed OS devices that use bootloaders from PDMC 4.8.0 or 4.9.0.
  If you are upgrading to Device Management Client 4.10.0 but using the bootloader from a previous release, you must explicitly define FOTA_USE_DEVICE_KEY.
  We highly recommend using the bootloader from Device Management Client 4.10.0, which fixes a security vulnerability found in the bootloader from the 4.8.0/4.9.0 releases.

• Updated to Mbed OS 6.12.0.

Known issues

• [Zephyr] Asynchronous DNS does not work well. The device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level by setting the DNS API selection to POSIX in the application's configuration settings.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 4.9.1 General Availability

Device Management Client example

Changes

• No changes

Known issues

• [Zephyr] Asynchronous DNS does not work well. The device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level by setting the DNS API selection to POSIX in the application's configuration settings.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html

Device Management Client 4.9.0 General Availability

Device Management Client example

Changes

• [Mbed OS] Increased SN_COAP_BLOCKWISE_MAX_TIME_DATA_STORED stored time to 15min for mesh to account for long retransmission chains during blockwise transfers.
• [Mbed OS] Updated ISM43362 Wi-Fi driver to #09a71bf with fix for mutex handling.
• Removed unregister resource 5000/0/1 from the application. Device Management Client library now implements OMA resource 1/0/4, which supports deregistration.
• Removed delta-tool from the application.
  • The current supported version (2.2.0 or later) of manifest-tool provides the functionality internally.
• Updated cURL to 7.76.0 in pal-platform.
• Fixed Atmel SE configuration.
• Updated to Mbed OS 6.9.0.
• [Linux] Updated Mbed TLS to 2.25.0.

Known issues

• [Zephyr] Asynchronous DNS does not work well. The device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted. To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level by setting the DNS API selection to POSIX in the application's configuration settings.

Release notes can be found from:
https://cloud.mbed.com/docs/current/release-notes/device-management-client.html