Developers

blukii Hub JSON API 2.0

In this documentation the JSON API structure 2.0 is described.

Last modified for version: 3.0.5.3.

HTTP Response format

The hub expects the following response data, if the server accepts the JSON data structure.

Push interface overview

Output example of the push interface

{
  "id": "hub86C274E0",
  "localIp": "192.168.178.41",
  "data": [
    "F05ECD2555ACBB9155263E8F0100006401626C756B69692E636F6D626561636F6E00010001C7",
    "665544332211ADC455263E8F0100006420020100000000000000010080",
    "F05ECD2555ACB8CA56263E8F0100006402CE626C756B626561636F6E000000010001",
    "665544332211ABF856263E8F0100006420020100000000000000010080",
    "F05ECD2555ACB9F257263E8F0100006402CE626C756B626561636F6E000000010001",
    "665544332211AB2558263E8F0100006420020100000000000000010080",
    "F05ECD2555ACB95959263E8F01000064040CEC000000003F510000C06C"
  ]
}

This format contains the raw byte data of each received data frame.

Data frame coding

Common Frame Part

MAC RSSI Timestamp Battery Type Content
6 bytes 1 byte 8 bytes 1 byte 1 byte N bytes

The records are sorted in ascending order according to timestamp.

iBeacon Content

Frame Data Type: 0x01

Content Length: 21 Bytes

UUID Major Minor Measured Power
16 bytes 2 bytes 2 bytes 1 byte

Eddystone UID Content

Frame Data Type: 0x02

Content Length: 17 Bytes

TxPower Namespace Instance
1 byte 10 bytes 6 bytes

Eddystone TLM Content

Frame Data Type: 0x04

Content Length: 12 Bytes

Battery Temperature Packets Active Time
2 bytes 2 bytes 4 bytes 4 bytes

Device Tracing Content

Frame Data Type: 0x10

Content Length: 22 Bytes

Device Id Tracing Set Frame Index Found Devices
2 bytes 1 byte 1 byte 16 bytes

Device Tracing Found Devices Content

Id 0 RSSI 0 Id 1 RSSI 1 Id 5 RSSI 5
2 bytes 1 byte 2 bytes 1 byte 2 bytes 1 byte

The Found Devices are sorted according to RSSI value with highest value first.

Special Frame Content

Frame Data Type: 0x20

Content Length: special content defined

Special Type Special Content
1 byte N bytes