Skip to content

Releases

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

Choose a tag to compare

@ewertons ewertons released this 07 Nov 01:37
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.

Microsoft.Azure.Iot.Device 1.2.0 Release

Choose a tag to compare

@timtay-microsoft timtay-microsoft released this 03 Nov 03:14
cf6c9df

Azure IoT SDK - C - 1.0.0

Choose a tag to compare

@ewertons ewertons released this 07 Nov 00:47
fa63f8e

We are pleased to announce the first general availability (GA) release of Azure IoT SDK - C (c/ in the Azure/azure-iot-sdk repository), a C99 device SDK for Azure IoT Hub and the Device Provisioning Service (DPS). It is designed for constrained and embedded devices and is easy to use on higher-end platforms.

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

What is in 1.0.0

Capability 1.0.0 (GA) 2.0.0-preview.1 (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 - Preview
Software updates with Azure Device Update - Preview
mqttv5 support in the Paho and az_mqtt adapters - Preview

Highlights

  • Connectivity. Registration with DPS and connection to the assigned IoT Hub over mqttv3, or direct connection to a known hub. TCP (8883) or WebSockets (443), with HTTP proxy support.
  • Resilience. Reconnection with exponential backoff and jitter, identity recovery, re-provisioning, and a saved hub with DPS fallback.
  • Security. X.509 and SAS authentication. Certificates issued by DPS from a certificate signing request (CSR) and renewed over IoT Hub. Private keys held in a PKCS#11 token, a TPM 2.0, PSA Crypto (such as the ESP32 Digital Signature peripheral), or behind an application-provided sign() callback. DPS TPM attestation.
  • IoT Hub features. Telemetry (with a documented delivery contract), cloud-to-device messages, direct methods, device twin, and file upload.
  • Resource-constrained design. Single-threaded contract. The connection and feature clients perform no dynamic allocation and run in workspaces provided by the application.
  • Extensibility. Eclipse Paho C (default), the az_mqtt client, or an application-provided MQTT client through an adapter interface. OpenSSL 3, mbedTLS, or an application-provided crypto backend.
  • Platforms. Linux (GCC, Clang), Windows (MSVC), ESP32 through ESP-IDF components (esp32, esp32c3, esp32s3, esp32c6), and Yocto. Built in strict C99, and also as C11, C17 and C23.
  • Integration. add_subdirectory(), FetchContent, or an installed CMake package with pkg-config files. A vcpkg manifest is included.

Quality

Every change is built and tested in continuous integration on Linux (GCC, Clang) and Windows (MSVC):

  • Unit tests, and an MQTT adapter conformance suite run against an MQTT broker.
  • End-to-end tests against IoT Hub and DPS, on both MQTT adapters (Paho and az_mqtt): SAS, X.509, DPS-issued certificates, TPM attestation and file upload. PKCS#11 key custody is tested on Linux.
  • The ESP32 sample, booted in QEMU (esp32, esp32s3 and esp32c3).
  • Memory and concurrency checks: Valgrind memcheck on Linux, AddressSanitizer on Windows (MSVC), and race detection (helgrind, DRD and ThreadSanitizer) on Linux.
  • Code coverage reporting.

See test coverage and end-to-end tests.

Getting started

The SDK is distributed as source; this release provides no binary packages.

Related release

Support for mqttv5 hubs and Azure Device Update software updates is available as a public preview in 2.0.0-preview.1, released alongside this version. Preview APIs may change; 1.0.0 is the stable release line.

Feedback

To report an issue or share feedback, please open an issue.

Microsoft.Azure.Iot.Device 2.0.0-preview4 Release

Choose a tag to compare

@timtay-microsoft timtay-microsoft released this 03 Nov 03:14
cf6c9df