Feature
|
Description
|
---|---|
Improved ease of Azure IoT Hub configuration
|
|
Improved ease of granting visibility and permissions to the Azure IoT Hub Connector.
|
|
Support for Azure IoT Edge Devices and Edge Modules
|
|
Improved outgoing message ("egress") processing
|
|
Support for Device Methods for Azure IoT Edge Devices as well as Azure IoT Devices
|
|
Improved support for Azure Blob Storage
|
|
Encryption of Azure IoT Hub credentials
|
|
Encryption of the configuration file for the Azure IoT Hub Connector
|
|
Updated smoke test for Azure IoT Edge Devices and Modules
|
|
Improved metrics for monitoring your Connector
|
|
Improved troubleshooting information
|
|
Improved logging by adding rolling policy
|
ID (SFID)
|
Description
|
---|---|
AZX-485 (14753782)
|
Azure IoT Hub Connector 2.0.0 works well with Java 1.8_u131 but fails with Java 1.8_201 on Azure Windows 2016.
This issue is fixed in v.3.0.0 of the Connector. The version of Java for this release is 1.8_u141 at minimum due to requirements of the ThingWorx Security Client application.
|
AZX-372 (14078093)
|
The Edge Device demo fails to start with error: No signature of method.
This issue is fixed in this release.
|
AZX-374 (14074993)
|
Azure IoT Hub Connector Firmware Update Demo NodeJS code fails.
This issue is fixed in this release.
|
ID
|
Description
|
---|---|
AZX-8 (formerly VOL-41)
|
The Azure IoT Hub Connector disappears from the list of connected Connection Servers on the platform.
When it starts up, the Azure IoT Hub Connector is visible under the list of Connection Servers on the Monitoring tab in ThingWorx. When run continuously under a high load, the Connector disappears from that list after several hours have passed. The Connector also stops processing messages, but no exceptions are written to the logs.
This issue is fixed in this release.
|
AZX-320
|
Azure IoT Hubs with uppercase letters in their names will not connect.
With release 2.0.0, the Connector connects to Azure IoT Hubs with uppercase letters in their names.
|
AZX-327
|
Azure-cxserver-name does not exist or is not yet associated with a Thing error when starting up the Azure IoT Hub Connector.
The ApplicationLog error that was generated when the Connector thing did not exist no longer occurs. However, if the bind fails (the Thing exists but does not have the tthcorrect template), the error message about the bind failure is logged.
|
AZX-341
|
Allow multiple properties in Cloud to device messaging.
Cloud-to-device messaging sends only one property at a time. Essentially, after a property value changes, a message containing the update is sent.
The ThingWorx Azure IoT Hub Connector now allows multiple property updates to be sent in a single message. Refer to the ThingWorx Azure IoT Hub Connector Installation and Operations Guide, v.2.0.0 for details.
|
AZX-353
|
Remove azureHub property from AzureIotHubThing Thing Template.
The azureHub property on the AzureIotThing Thing Template is no longer used and has been removed from this Thing Template.
|
ID
|
Description
|
---|---|
AZX-3
|
Message ordering is not preserved for a single device.
Although messages are retrieved synchronously from the Azure Event Hub endpoint, messages are dispatched to ThingWorx Platform asynchronously, leading to potential out-of-order application.
|