Link Search Menu Expand Document

Azure IoT Hub (ble data)

Table of contents

This example shows the required configuration to enable BLE data forwarding for all supported BLE vendors to Azure IoT Hub.

  • scope-id - has to be replaced with Azure DPS enrollment group scope-id
  • key - has to be replaces with Azure symmetric group key
  • ap-group - has to be replaced with the AP group name the configuration should be enabled on (multiple statements are required for multiple groups) (ArubaOS only)

Note:
bleDataForwarding is enabled by default for server type Azure-IoTHub and cannot be disabled.

Caution:
Enabling the device class filter all will enable BLE data forwarding of all knon/supported BLE vendor device classes. This could haveally increase the amount of data beeing forwarded to the remote server because all BLE advertisements and scan respsonse packets are forwarded in near real time.
It is recommended to use the BLE device class filter and BLE data filters to filter the data being forwarded.

ArubaOS

iot radio-profile "ble-int"
    radio-mode none ble
!
ap-group <ap-group>
    iot radio-profile "ble-int"
!
iot transportProfile "Azure-IoT-Hub-ble-data"
    serverType Azure-IoTHub
    deviceClassFilter all
    bleDataForwarding
    azure-dps-id-scope <scope-id>
    azure-dps-auth-type group-enrollment symmetric-key <key>
    include-ap-group <ap-group>
!
iot useTransportProfile "Azure-IoT-Hub-ble-data"

Aruba Instant

iot radio-profile "ble-int"
 radio-mode ble
 exit

iot use-radio-profile "ble-int"

iot transportProfile "Azure-IoT-Hub-ble-data"
 endpointType Azure-IoTHub
 payloadContent all
 bleDataForwarding
 azure-dps-id-scope <scope-id>
 azure-dps-auth-type group-enrollment symmetric-key <key>
 exit

iot useTransportProfile "Azure-IoT-Hub-ble-data"