Out of the box, the SensorData LoRaWAN is not configured to take any readings, and must be first configured by setting up schedules. Currently, there can be up to 5 different schedules, each with 4 items, which represent a single data source (analog input reading, GPS position, battery voltage, etc). Each schedule is completely independent, but if 2 (or more) happen to occur at the same time, they will be run one after the after (without grouping data into transmissions).

Schedule Period: In minutes, this is how often the schedule gets run. Care must be taken in choosing this value, as different LoRaWAN regions (and networks) have different restrictions on how often, and how much data can be sent.

Schedule Expiry: Due to the nature of LoRaWAN, a single payload transmission may be paused until a time period has passed (determined by the network). There is no time-stamp information sent with payloads, so the time a payload is received is assumed to be (close to) the time of sampling. The schedule expiry (in seconds), can be used to invalidate data that has been waiting too long to be transmitted; it will basically be ignored. This may cause only part of a schedule to be transmitted (if it was split between payloads). This feature can be disabled by setting the value to 0.

Item IDs: For the full list, see the integration documentation, or configuration app.