Releases: Azure/azure-iot-sdk-node
Releases · Azure/azure-iot-sdk-node
Azure IoT SDKs for Node.js v1.1.11 (Device) and v1.1.10 (Service)
Bugfixes
azure-iot-device-http
- messageId and other system properties were not set correctly in D2C messages over HTTP
azure-iothub
- Device Method parameters were still using the
timeoutInSeconds
parameter instead ofconnectTimeoutInSeconds
andresponseTimeoutInSeconds
.
Important note
We've switched to typescript during this release. while we expect no breaking changes and have decent end-to-end test coverage, it is not impossible that we missed something, especially as we turn from manual to automatic generation of d.ts file. please report any problem you find!
Azure IoT Device SDK for Node.js version 1.1.10
Bugfixes:
- Fix for #34: Twin timeout has been increased to support slower connections
- Set MQTT keepalive ping to 3 minutes, and no rescheduling, to make sure we detect MQTT connections dropping
Azure IoT SDKs for Node.js version 1.1.9
New features
- CBS Support for Service SDK Client (uses AMQP)
Bugfixes
- Fix for #28 (could not getTwin after disconnect/reconnect)
- Fix for #25 (Node-red: Allow multiple nodes with different connection strings in the same flow)
External contributions:
- #24: Fix typos in docs (Thanks @efreiberg)
Azure IoT SDKs for Node.js version 1.1.8
New features:
- CBS support for AMQP protocol
CBS is a type of authentication that relies on Shared Access Keys, like SASL-PLAIN. Instead of sending the shared access signature token in the URL used to connect to IoT Hub (which means the client has to disconnect and reconnect to update this token), the connection is opened anonymously and the SAS token is sent to a specific endpoint separately and can be renewed without disconnecting the client. This is a big improvement for reliability of the AMQP protocol stack.
Bugfixes:
Azure IoT SDK for Node.js v1.1.7
Service SDK: [email protected]
- Added Bulk device management APIs:
- Registry.addDevices(deviceArray, callback)
- Registry.updateDevices(deviceArray, callback)
- Registry.removeDevices(deviceArray, callback)
See the code sample for details
Issues/PRs:
Pulled #16 and #17 to improve docs.
Other items:
Added a few internal APIs to azure-iot-common
and azure-iot-amqp-base
to enable future work.
Azure IoT Hub SDK for Node Release 2017-2-10
Service Client
- Fix a typo on the methodName property in device_method_params.d.ts
- Add optional continuationToken argument to query.next*()
- Add getRegistryStatistics API to the Service SDK
Device Client
- Properly set correlationId property in AMQP
- Properly handle some errors when attaching with AMQP
Update the readme on how to run samples.
Various changes/fixes to the end to end tests.
Azure IoT SDKs for Node.js version 1.1.5
Service SDK
- Fix AMQP over Websockets transport for the Client (Connection URL was being overwritten)
Device SDK
- Enforce UTF-8 decoding of PEM files in tests and samples (node 0.10 compatibility)
- Add
ConnectionString.createWithSharedAccessKey()
andConnectionString.createWithX509Certificate()
APIs - Add E2E tests for authentication failure
Thanks to @jsturtevant for helping with the iothub-explorer debugging instructions!
Azure IoT SDKs for Node.js version 1.1.4
Fixes for the following issues:
Azure IoT Hub SDK for Node.js
Azure IoT Device and Service SDKs for Node.js
Device SDK
- Delay loading of azure-storage until actually needed
- Update samples to use MQTT by default
- Fix Twin class export in typescript definition files
- Throws correct NotImplementedError when a feature is not implemented by a transport
Service SDK
- Fixed wrong timeout property name in device method parameters
- Update scheduled jobs samples
iothub-diagnostics
- removed deprecated amqp-ws dependency