Overview – Azure IoT Hub

Azure IoT Hub is a fully managed service specifically designed for IoT devices, providing a secure and scalable way to connect, monitor, and control billions of IoT devices.

OAS provides connectivity to Azure IoT Hub using the OAS Azure IoT driver by setting the Type to IoT Hub.

👉 For more details see Getting Started Azure IoT Hub

Configuration Parameters

The following section outlines the configuration parameters available for the Azure IoT driver.

Driver Type

The Azure IoT driver supports two connection types: IoT Hub and Event Hubs. Set the Type to IoT Hub to use the Azure IoT Hub service.

👉 To use the Azure Event Hubs service see Overview – Azure Event Hubs

Connection Parameters

The following connection parameters can be configured:

  • Azure IoT Device ID: The ID that uniquely identifies this connection.
  • Azure IoT Connection: The connection string to Azure IoT.
  • Azure IoT Hub: The name of the Event Hub.
  • Azure IoT Transport: The protocol to use for communication. [AMQP, AMQP Web Sockets Only]
  • Return to Online: The frequency in seconds to check for good communications when the interface is taken offline.

Store and Forward

Enable data buffering when communication failure occurs. Values will be stored to directory specified under Configure > Options > Store and Forward.

To buffer data from remote OAS Engine enable Buffer for Remote IoT Publish under Configure > Options > Store and Forward on each remote data source system.

Failover

You can enable the Enable Failover property and configure a secondary bootstrap server and security protocol. When a secondary interface is configured, OAS will attempt to use it if the primary interface fails to communicate.

Publish Selected Tags

The Publish Selected Tags feature allows you to specify a list of Tags that should be published to a given topic. The chosen Tags will be published based on a configurable interval, a Boolean Tag event trigger or a time based schedule. You can control a number of different parameters to customize the JSON payload structure. See IoT Publish for details.