The Azure IoT Hub output in ArcGIS Velocity allows you to send messages to a Microsoft Azure IoT Hub, where you can push information to devices and sensors in the field, enabling actuation or changes in device behavior. Azure IoT Hub is a managed service hosted in the Azure cloud that acts as a central message hub for bidirectional communication between ArcGIS Velocity and your IoT devices.
For more information on Azure IoT Hub, see the Azure IoT Hub documentation.
Examples
- A data analyst wants to update the properties of sensors, connected through an Azure IoT Hub, based on information coming in from a related system.
- A logistics company configures an Azure IoT Hub output to trigger vehicle tracking device behavior based on the vehicle's current location.
Usage notes
- Azure IoT Hub connection properties can be obtained in the Azure IoT Hub.
- The shared access policy should have Service Connect permissions.
- The device to which you intend to send messages must already exist in Azure IoT Hub. Velocity will not create it.
- The Track ID of the message or record should match the device ID that is registered in the Azure IoT Hub.
- Azure maintains a maximum of 50 pending messages for delivery per device. For more information, see the Azure IoT Hub documentation.
Parameters
| Parameter | Description | Data type |
|---|---|---|
Azure IoT Hub Host Name | The host name for Azure IoT Hub. | String |
Shared Access Key Name | The shared access key name for the Azure IoT Hub credentials. | String |
Shared Access Key | The shared access key for the Azure IoT Hub credentials. | Password |
Considerations and limitations
Azure IoT Hub supports a message time to live parameter, which is the expiration time for a cloud-to-device message. In the current release, this is set by default to 1 hour for all outgoing messages from Velocity. This will be exposed as a configurable property in a later release.