Skip to content

Azure IoT SDK - C - 2.0.0-preview.2 (Public Preview)

Pre-release
Pre-release

Choose a tag to compare

@ewertons ewertons released this 07 Nov 01:37
· 89 commits to releases/public-preview since this release
62f7f95

We are pleased to announce the public preview of Azure IoT SDK - C (c/ in the Azure/azure-iot-sdk repository), released alongside the first general availability release, 1.0.0. This preview includes all features of 1.0.0 (IoT Hub over mqttv3, and DPS) and adds capabilities that are not yet generally available.

This SDK is separate from the earlier Azure IoT C SDK in the Azure/azure-iot-sdk-c repository.

Preview notice. APIs may change before a stable release. This version is intended for evaluation and feedback; 1.0.0 is recommended for production use.

GA and preview at a glance

Capability 1.0.0 (GA) 2.0.0-preview.2 (Public Preview)
IoT Hub over mqttv3 (MQTT 3.1.1): telemetry, cloud-to-device messages, direct methods, device twin, file upload Yes Yes
Device Provisioning Service: registration, certificates issued from a CSR, TPM attestation Yes Yes
X.509 and SAS authentication, keys in PKCS#11 tokens, TPM 2.0 or PSA Crypto Yes Yes
Certificate renewal over IoT Hub Yes Yes (mqttv3 only)
IoT Hub over mqttv5 (MQTT 5.0): telemetry, device twin, direct methods, custom topics - New
Software updates with Azure Device Update - New
mqttv5 support in the Paho and az_mqtt adapters - New

New in this preview

  • mqttv5 IoT Hubs. DPS returns the hub's connection profile and the SDK selects the protocol; for a direct connection, the profile is set explicitly.
    • Telemetry, device twin, and direct methods, with mqttv5 user properties, content type, correlation data, message expiry, and Reason Strings.
    • Custom topics: publish at QoS 0 or 1 to the topics permitted by the hub's topic templates.
    • mqttv5 hubs require X.509 authentication (including keys held in hardware); SAS is not yet accepted.
    • Not yet available on mqttv5: cloud-to-device messages, file upload, and certificate renewal over IoT Hub.
  • Software updates with Azure Device Update. A client for mqttv3 and mqttv5 hubs. The device requests update information from the service over its DPS connection, downloads the update files separately through a download handler provided by the application, verifies the signed manifest and the file hashes, installs through application code, and reports the result.
    • Managed, library, and primitives-only integration modes.
    • Inline and detached (mini) update manifests. A detached manifest file is downloaded, verified against the signed mini manifest, and persisted across reboots.
    • Multi-step workflows, rollback, reboot and resume, and delta updates.
    • ESP-IDF OTA platform hooks and a sample.
    • Not yet supported: reference steps. A manifest that contains one is refused before any step runs.
    • See the software update guide.
  • mqttv5 support in both adapters (Paho and az_mqtt) and in the application-provided adapter interface, covered by the adapter conformance suite.
  • New package components mqttv5 and su_delta. During the preview, the installed CMake package accepts the same minor version only (SameMinorVersion).

All other capabilities (connectivity, resilience, authentication and certificates, platforms, and integration options) are as described in the 1.0.0 release.

Getting started

The SDK is distributed as source. Preview development continues on the releases/public-preview branch.

Feedback

Feedback is welcome and helps shape the stable release. To report an issue or share feedback, please open an issue.