ZF Openmatics

Table of contents

This example shows the required configuration to enable ZF Openmatics asset tracking.

  • username - has to be replaced with the login username for the ZF deTAGtive platform
  • password - has to be replaced with the login password for the ZF deTAGtive platform
  • 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:
The DigiCert root certificate has to be installed on the Aruba infrastructure when connecting the ZF Openmatics deTAGtiv platform. Please see the Aruba CLI Reference - Importing Certificates for details.

ArubaOS

iot radio-profile "ble-int"
    radio-mode none ble
!
ap-group <ap-group>
    iot radio-profile "ble-int"
!
iot transportProfile "ZF-Openmatics-deTAGtive"
    serverType ZF-Openmatics
    serverURL "https://app.detagtive.com/backend/"
    username <username>
    password <password>
    reportingInterval 5
    deviceClassFilter zf-tags
    include-ap-group <ap-group>
!
iot useTransportProfile "ZF-Openmatics-deTAGtive"

Aruba Instant

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

iot use-radio-profile "ble-int"

iot transportProfile "ZF-Openmatics-deTAGtive"
 endpointURL https://app.detagtive.com/backend/
 endpointType ZF
 payloadContent zf-tags
 username <username>
 password <password>
 transportInterval 5
 exit

iot useTransportProfile "ZF-Openmatics-deTAGtive"