chirpstack-application-server

Improvements:

• --mqtt-ca-cert / MQTT_CA_CERT configuration flag was added to
  specify an optional CA certificate
  (thanks @siscia).

Bugfixes:

• MQTT client library update which fixes an issue where during a failed
  re-connect the protocol version would be downgraded
  (paho.mqtt.golang#116).

Features & changes:

• Added frame logs tab to node to display all uplink and downlink
  frames of a given node. Note: This requires
  LoRa Server 0.18.0.
• Updated organization, application and node navigation in UI.

Bugfixes:

• Fix ABP settings not editable by organization admin
  (#85)

Features & Changes:

• Channel-lists have been removed. Extra channels (if supported by the ISM
  band) are now managed by LoRa Server configuration.

Bugfixes:

• On editing a gateway, disable the MAC input field (as this is the unique
  identifier of the gateway).
• A pagination regression has been fixed (#82).

Note: when upgrading to this version with --db-automigrate /
DB_AUTOMIGRATE set, channel-list data will be removed.

Features & changes:

• Organization management so that applications and gateways can be managed per organization.
• Node-session migrate function (to migrate from LoRa Server 0.11.*) has been cleaned up.

Bugfixes:

• Openstreetmap tiles can now be fetched using https:// (in some cases Safari was not loading any tiles because of mixed content).
• When the browser does not allow using the location service, freegeoip.net is used as a fallback.
• Map zoom in/out on scrolling has been disabled (to avoid accidental zoom on scrolling the page).

Many thanks again to @jcampanell-cablelabs for collaborating on this feature.

Bugfixes:

• Fix race-condition between fetching the gateway details and getting the
  current location if the gateway location is not yet set (UI).

Features & changes:

• Add 'set to current location' (create / update gateway in UI)

Features & changes:

• Gateway management and stats
  • Gateway management UI and API (accessible by global admin users) was added.
  • Gateway locations are now exposed in the uplink MQTT topic
  • Requires LoRa Server 0.16.0+.
• On MQTT and PostgreSQL connect error, LoRa App Server will retry instead
  of fail.

Many thanks again to @jcampanell-cablelabs
for collaborating on this feature.

This release contains changes that are not backwards compatible!

Features & changes:

• User management with support to assign users to applications.
• API authentication / authorization (JWT token) format has been updated
  (it contains the username instead of all the permissions of the user).
  See API documentation for more information.
• --jwt-secret / JWT_SECRET is now mandatory.
• An initial user with admin / admin credentials will be created (change
  this password immediately!).
• Node-session API has been removed, use the /api/nodes/{devEUI}/activation
  endpoint for getting (and setting) node activations.
• Updated web-interface to support user management.
• New API endpoints for creating users and assigning users to applications.

Many thanks to @jcampanell-cablelabs for collaborating on this feature.

Features:

• Per application (network) settings. Settings like Class-C, ADR, receive-window,
  data-rate etc. can now be managed on an application level. Optionally, they can
  be overridden per node.
• Applications and nodes are now paginated per 20 rows.

This release contains changes that are not backwards compatible!

Features & changes:

• Nodes can now be grouped per application (e.g. called temperature-sensor).
  For backwards compatibility, the AppEUI is used as application name when
  upgrading.
• Nodes can now be given a name (e.g. garden-sensor), which must be unique
  within an application. For backwards compatibility the DevEUI is used as
  name for the nodes when upgrading.
• Application ID, and the name of the application and node are included in the
  MQTT payloads.
• JWT token validation is now based on the ID of the application instead of the
  AppEUI (which should not be used for grouping nodes by purpose).
• The gRPC and REST apis have been updated to reflect the above application and
  node name changes.
• The MQTT topics (and payloads) are now based on the application ID and node
  DevEUI (see mqtt topics for more info).
• An endpoint for activating nodes and for fetching the activation status has
  been added (before this was done by using the node-session endpoint).
• The node activation mode can now be set (OTAA or ABP). Incoming join-requests
  for ABP nodes will be rejected.
• The node-session API is now accessible at /api/node/{devEUI}/session.

Many thanks to @jcampanell-cablelabs
and @VirTERM for their input on the API changes.

Bugfixes:

• limit and offset url parameters are now correctly documented in the
  API console.
• More descriptive error on missing --http-tls-cert and --http-tls-key
  configuration.

Features:

• Adaptive data-rate support. See loraserver/features
  for more information about ADR. Note:
  • LoRa Server 0.13.0 or higher
    is required
  • ADR is currently only implemented for the EU 863-870 ISM band
  • This is an experimental feature
• Besides RX information, TX information is exposed for received uplink
  payloads. See MQTT topics for more information.

Initial release.

See also the LoRa Server changelog for 0.12.0 when migrating from an older LoRa Server version: https://github.com/brocaar/loraserver/blob/master/docs/changelog.md#0120