The new Low Power Wide Area networks (LPWAN) are intended to deploy a large number of sensors in the field. Typically the payloads from LPWAN devices are limited. They cannot be used over these LPWAN networks.
To support LoRaWAN devices, we have, in conjunction with Proximus Enco, developed a containerized implementation of a Binary payload. These containers are based on a per sensor type and provide you an easy and lean way to upload you sensor data over the Proximus Public LoRaWAN network.
The convention for the containers is outlined below and fully implemented into our Arduino LoRAWAN SDK
Containers
Definition container name in the library code, for example #define BINARY_TILT_SENSOR ((short)2)
Asset name asset name in AllThingsTalk Maker
Data type the primitive data type in the code
Asset profile the corresponding asset profile in AllThingsTalk Maker
Fixed containers (13)
When manually creating an asset from Maker, make sure you use the asset name (the numbers in the table below), corresponding with the data type you need!
Definition
Asset name
Data type
Asset profile
BINARY_TILT_SENSOR
2
bool
{"type":"boolean"}
PUSH_BUTTON
3
bool
{"type":"boolean"}
DOOR_SENSOR
4
bool
{"type":"boolean"}
TEMPERATURE_SENSOR
5
float
{"type":"number"}
LIGHT_SENSOR
6
float
{"type":"number"}
PIR_SENSOR
7
bool
{"type":"boolean"}
ACCELEROMETER
8
floats
{"type":"object", "properties": {"x":{"type":"number"},"y":{"type":"number"},"z":{"type":"number"}}} All fields are required
GPS
9
floats
{"type":"object", "properties": {"latitude":{"type":"number"},"longitude":{"type":"number"},"altitude":{"type":"number"}, "timestamp":{"type":"number"}}} Latitude and longitude are required, altitude and timestamp are optional