Devices provide a collection of BLE Services.
<device name>.json files contain a top-level object with name and services keys.
This value is the canonical display name of the device.
This is an array of filenames of Service definitions. Services will be presented on the device in the order of files in the array.
Definitions using the datastructure JSON key are used to specify how binary data should be parsed.
Data is parsed as little endian beginning with the first DataType in an array.
A DataType is an object with three keys, type, count, and an optional description:
A string specifying a primitive data type or an array of DataTypes. The allowed primitive values are:
UTF8- A UTF-8 encoded stringuint8/uint16/uint32- Unsigned integers of 8, 16, or 32-bit lengthsint8/int16/int32- 2's complement signed integers of 8, 16, or 32-bit lengths
This value will be either a number or null.
- Numbers indicate how many consecutive
types to parse. nullindicates that the Characteristic value is of variable length, and all of the remaining bytes in the value should be interpreted astype.
This is an optional entry provided only as a developer reference.
BLE Services are defined in individual files in the services directory.
Service files contain a top-level object with service and characteristics keys.
Bluetooth uses 128-bit UUIDs for identifiers of Services & Characteristics. The Bluetooth Spec defines a 16-bit shorthand for UUIDs for Services and Characteristics defined by the Specification. These shorthand values can be used as-is for Service and Characteristic identification. All custom Services and Characteristics must use full 128-bit UUIDs.
Service identifiers consist of two keys/value pairs:
name- human-readable UTF-8 stringUUID- 128-bit or 16-bit shorthand UUID values expressed as hex characters
This value is an array of BLE Characteristic definitions. A Service will contain one or more Characteristics.
The Characteristic name describes the logical function of the Characteristic value.
The 128-bit or 16-bit shorthand UUID of the Characteristic expressed as hex characters.
An array of DataTypes, as described above.
This object indicates what interactions the Characteristic supports. Object keys directly correspond to common BLE Characteristic property names.