Device Management Client Lite 1.1.1 release notes (preview)

Device Management Client Lite

Client Lite 1.1.0 sends an additional component update object (/14) as part of its registration message even though the client does not support it yet. The update service has changed recently to handle the client differently, so there is no backward compatibility. Client Lite 1.1.0 cannot successfully update firmware. As part of this patch release, component update is behind a feature flag that is disabled in Client Lite release.

Example application

Increased the default lifetime of UDP_QUEUE mode devices to 600 seconds. The earlier, shorter lifetime was causing intermittent issues where the device was unable to re-register before the lifetime expired.

Known issues

The software is alpha quality, which means:

• It is tested to compile only with the GCC_ARM compiler.
• All client features are not in place yet.
• APIs may change.
• Documentation is work in progress.

Client Lite development is in progress so there are some known issues to keep in mind while using the APIs:

• NRF52840_DK board uses J-Link. It has some stability issues when flashing the board. Sometimes, it ends up in "read only" mode. To fix this, unplug the USB cable and plug it back in.

• API definitions and behavior may not be stable and may change in future releases.

• The logs show:

  Resource created
  Error code : 7
  

  You can ignore this error.

• NRF52840_DK does not compile with ARMC6 compiler.

• The device preserves certificates between device flashes (using .hex flashing). If you want the device to pick new developer credentials, you need to clear the storage for example with pyocd erase --mass-erase or use the configuration option storage-reset-dev-credentials in mbed_app.json. The device creates a new Device ID if it is not found in KVStore. Please note that developer certificate limits number of devices to 100.

• NRF52840_DK board does not work with Block-wise sizes smaller than 512.