Azure IoT Device SDK / Edge Modules preview

pre-release for the modules-preview branch

• introducing the new ModuleClient
• Modules can:
  • connect to Edge Hub or IoT Hub
  • send telemetry
  • use Azure IoT Edge routing feature with inputs and outputs (only available when connecting to an Edge Hub)
  • use their twin
  • receive method requests
• Known limitations of this preview version:
  • receive C2D messages
  • upload files
  • use X509 authentication

Azure IoT SDKs for Devices v1.4.2

Bugfixes

• azure-iot-device-amqp: method receiver link has invalid rcvSettleMode 293
• Improved detail added to userAgent string for SDK usage tracking
• Many improvements to E2E tests

Packages released

• azure-iot-amqp-base: v1.5.2
• azure-iot-common: v1.5.1
• azure-iot-device: v1.4.2
• azure-iot-device-amqp: v1.4.2
• azure-iot-device-http: v1.4.2
• azure-iot-device-mqtt: v1.4.2
• azure-iot-http-base: v1.4.1
• azure-iot-mqtt-base: v1.4.1
• azure-iot-provisioning-device: v1.1.3
• azure-iot-provisioning-device-amqp: v1.1.4
• azure-iot-provisioning-device-http: v1.1.4
• azure-iot-provisioning-device-mqtt: v1.0.5
• azure-iot-provisioning-service: v1.0.5
• azure-iot-security-x509: v1.0.4
• azure-iothub: v1.3.1

Azure IoT SDKs for Devices v1.4.1

Features

• Added the ability to pass an HTTP Agent object to the HTTP (4dda10b) and MQTT-WS (093bd9b) transports (enables setting keep-alive and proxy settings). Closes #98

Bugfixes

• Fixes for a couple of race conditions in the MQTT (3745125) and AMQP (75f23f8) transports
• Adjust MQTT QoS level for C2D messages (b4cb2e2)

Packages released

• azure-iot-amqp-base: v1.5.1
• azure-iot-http-base: v1.4.0
• azure-iot-mqtt-base: v1.4.0
• azure-iot-device: v1.4.1
• azure-iot-device-amqp: v1.4.1
• azure-iot-device-http: v1.4.1
• azure-iot-device-mqtt: v1.4.1
• node-red-contrib-azureiothubnode: v0.1.27
• azure-iot-provisioning-device-http: v1.1.3
• azure-iot-provisioning-device-amqp: v1.1.3
• azure-iot-provisioning-device-mqtt: v1.0.4

Azure IoT SDKs for Node.js

New features

• Support for contentType and contentEncoding properties on the Message class: this enables routing on message body in Azure IoT Hub (see this blog post for details)

Bugfixes and Improvements

• The Twin feature has been refactored to enable retries - no public API has been modified.
• Thanks to @treedust for fixing typos in our docs!

Package versions

• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]

Azure IoT SDKs for Node.js

Fixes:

• #64
• #157
• #221 (part deux)

Improvements:

• Update service api-version to 2018-01-16
• Update dependency versions of lodash, azure-storage, machina, debug, uuid and tss.js

Azure IoT SDKs for Node.js

TL;DR

• Fix for #221
• Fix for #193
• Fix for #187
• Add support for TPM-based device registration and authentication
• update MQTT library dependency minimum version
• update AMQP library dependency minimum version

Details

azure-iot-common v1.4.0

• Add new factory method for the SharedAccessSignature class enabling the caller to pass a function to use when signing the SAS token.

azure-iot-amqp-base v1.4.0 (not a usable public API!)

• update AMQP library dependency minimum version
• Enable support for custom SASL mechanism (used by TPM-based authentication)
• Remove call to undefined callback (#221/#222)

azure-iot-http-base v1.3.1 (not a usable public API!)

• Export HttpTransportError class.

azure-iot-mqtt-base v1.3.1 (not a usable public API!)

• update MQTT library dependency minimum version

azure-iot-device v1.3.1

• Fix for #193

azure-iothub v1.2.4

• Fix for #187 (properly URI-encode device ids)

azure-iot-provisioning-device v1.1.0

• Add support for TPM-based device registration

azure-iot-provisioning-device-http v1.1.0

• Add support for TPM-based device registration

azure-iot-provisioning-device-amqp v1.1.0

• Add support for TPM-based device registration

azure-iot-security-tpm: v1.0.0-preview

• Support for TPM-based registration

All packages have been updated to the latest version of the azure-iot-common package as well.

Azure IoT SDKs for Node js v1.3.0 (Device), v1.2.3 (Service) and v1.0.0 (provisioning)

This release includes new features!

Azure IoT Hub

Device SDK (v1.3.0)

• Introducing the concept of authentication providers

Service SDK (v1.2.3)

• Snap to latest common packages

Azure IoT Hub Device Provisioning Service

Device SDK

• Support for X509-based registration over AMQP, MQTT and HTTP (TPM will come in future releases)

Service SDK

• snap to latest common packages

Azure IoT Hub Device Provisioning Service SDK v1.0.0 and Service SDK v1.2.2

Azure IoT Hub Device Provisioning Service SDK v1.0.0

This SDK enables you to create, update, delete and query individual enrollments and enrollment groups, as well as query, get and delete device registration states. This is the first official (non-preview) release of the Azure IoT Hub Device Provisioning Service SDK for Node.js.

• Service Documentation
• Code
• Samples

Azure IoT Hub Service SDK v1.2.2

Bugfixes

• #162 missing ? for last optional parameter in nextAsTwin() (solved with #165). Thanks @Qba91 and @anthonyvercolano !

Azure IoT SDKs for Node.js v1.2.2 (Device) and v1.2.1 (Service)

Issues closed

• #132 (Thanks @dsjh, @bmrpatel, @wmmihaa)
• #138 (Thanks @jonbgallant)
• #141 (Thanks @dsjh)

Package versions

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Azure IoT SDKs for Node.js v1.2.1 (Device) and v1.2.0 (Service)

Bugfixes:

• #73 with #131 (MQTT Premature close error)
• #119 with #120 (typescript types in service SDK - thanks @nebrius !)
• Removed dependency to old sinon.js version that was producing deprecation warnings
• Removed deprecated --type-check option in the tslint npm script.

New features:

• #127 Retry logic for the AMQP Client of the service SDK (to retry connecting and sending C2D messages)

Retries in azure-iothub.Client

Before this release, the SDK user had to manually manage if the Client was connected or not before sending C2D messages and eventually called connect. if not connected. it was also mandatory to listen to the disconnect event.

With the new AMQP state machine and Client introduced in this release, sending C2D messages automatically handles connecting the client if necessary, and retries connecting and sending messages (if the error can be retried, such as a timeout). this is done using the azure-iot-common.ExponentialBackoffWithJitter policy. it is possible to modify the retry policy using the Client.setRetryPolicy API.

Please note: the current retry logic does not include the FeedbackReceiver and FileNotificationReceiver objects: this is in our backlog but if you are using those for now, you should still listen to the disconnect event and call getFeedbackReceiver and getFileNotificationReceiver manually to re-establish the link. Calling any of these APIs will also automatically connect the client.