v2.0.0-alpha.1

v2.0.0 (in development)

Upgrade notes

Before upgrading to v2, first make sure you have the latest v1 installed and running
(including LoRa App Server). As always, it is recommended to make a backup
first :-)

Features

LoRaWAN 1.1 support!

This release adds support for LoRaWAN 1.1 devices (meaning that both LoRaWAN 1.0
and LoRaWAN 1.1 devices are supported). Please note that the LoRaWAN 1.0 AppKey
is now called NwkKey and LoRaWAN 1.1 adds a new key called AppKey.

Changes

Device-status

The device-status has been removed from the uplink payload and is sent over
a separate MQTT topic (or HTTP integration). This to make sure that the
the device-status is only published when an update is available.
See also Sending and receiving data.

API changes

The API has been cleaned up to improve consistency and usability. This update
affects most of the endpoints! Most of these changes can be summarized by
the following example (where device is a separate object which now can be
re-used for create / get and update methods).

Old API

POST /api/devices

{
  "name": "test-device",
  "devEUI": "0102030405060708",
  "applicationID": "123"
  ...
}

New API

POST /api/devices

{
  "device": {
    "name": "test-device",
    "devEUI": "0102030405060708",
    "applicationID": "123"
    ...
  }
}

InfluxDB changes

The device_uplink measurement spreading_factor, bandwidth, modulation
and bitrate tags are now replaced by a single dr tag.

Uplink message payload

The uplink message payload (used for MQTT and HTTP integrations) has been
modified slightly:

• It now contains a dr field indicating the used uplink data-rate.
• Location related fields of each rxInfo element has been moved inside a location object.
• MAC has been renamed to gatewayID for each rxInfo element.
• The adr field has been moved out of txInfo and moved into the root object.