chirpstack-application-server

v3.6.1

Bugfixes

• Fix setting time in rxInfo for json_v3 (default) integration marshaler.
• Fix integrations break when codec function returns a NaN value. (#390)

v3.6.0

Features

Protobuf based integrations

This feature adds a marshaler configuration option to the integration configuration. The default is backwards compatible with the current JSON format. New options are protobuf (Protobuf binary) and json (Protobuf based JSON).

RPM packaging

This is the first release providing .rpm packages for CentOS and RedHat. (#383

Improvements

gRPC / Protobuf cleanup

All definitions are now imported from github.com/brocaar/chirpstack-api/go. When using the gRPC API, you must update your imports.

Azure Service-Bus integration

Implement re-connect in case of an Azure Service-Bus error. This to work partly around azure-service-bus-go/issues/149.

Support multiple HTTP endpoints

Implement support for configuring multiple endpoints in the HTTP integration.

Internal improvements

Handlink of the received uplinks has been improved to reduce the number of required database transactions.

Bugfixes

• Payload codec is hidden on application create (it was already on edit).

Improvements

• Deprecate use of dots (.) in environment variable names, use double understore (__) instead. (#369)

Bugfixes

• Fixes init stop script which could cause the ChirpStack Gateway Bridge to not properly stop or restart. (#379)

v3.5.0

This release renames LoRa App Server to ChirpStack Application Server. See the Rename Announcement for more information.

Improvements

• Add copy to clipboard for hex heys. (#364)
• Persist selected number of table rows per page in localStorage. (#351)

Bugfixes

• Fix rendering empty gateway map.

v3.4.0

Features

IDs for correlation

This release implements per context unique IDs that are printed in the logs and are returned as header in API responses. This makes it easier to correlate log events.

Organization admin permissions

Next to the organization admin permission, this release makes it possible to also (instead of full organization admin permissions), make an user "device admin" or "gateway admin".

Migrate gateway stats

This release migrates the gateway stats from LoRa Server into LoRa App Server. This also adds new configuration options to the configuration file, to configure the timezone for aggregation and metrics retention.

Gateway map

In the gateway list page, it is now possible to show a map showing all the gateways and their states.

Improvements

• Add PostgreSQL max open / idle connections settings. (#360
• Cleanup old freegeoip.net code for gateway location.

Bugfixes

• Fix gateway last-seen in web-interface.

Upgrading

This release requires LoRa Server v3.3.0 or later (which will forward the gateway stats to the Application Server API). After upgrading LoRa App Server and restarting it, it will run a migration to import existing stats from the LoRa Server database. Therefore make sure LoRa Server is up and running during the upgrade of LoRa App Server.

v3.3.1

Improvements

• Add RXInfo and TXInfo to join-notifications. (#235)

Bugfixes

• Propagate gRPC errors to that the correct HTTP status is returned. (#349)
• Fix not found UI error when device is inactive. (#359)

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.

v3.3.0

Features

Multi-frame geolocation

The multi-frame geolocation (implemented by LoRa Server v3.2.0) fields have been added to the Device Profile form in the web-interface.

Prometheus metrics

Prometheus metics have been implemented for the Join Server API interface.

Improvements

• Update UI dependencies to their latest versions.
• Show popup on gateway create when no Service Profile exists. (#345)
• Remove unused fields when listing users. (#328)
• Update multicast address and session-key input field widgets.
• Mention in API description that the organization ID of an application can not be updated after create. (#343)

Bugfixes

• Trigger organization dropdown reload on organization change. (#342)

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.

v3.2.0

Features

Device queue

The LoRa App Server web-interface has now the option to:

• Enqueue payloads
• List pending queue items
• Flush the device queue

Prometheus metrics

gRPC API metrics can now be exposed using a Prometheus metrics endpoint.
In future releases, more metrics will be exposed using this endpoint.

Improvements

• Multicast-group frame-counter cleanup (there was a column in both the LoRa App Server and LoRa Server database). (#339)

Bugfixes

• Fix missing multicast enqueue error handler (this caused the enqueue endpoint to return a 200 even in case of error).

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.

v3.1.0

Features

Device variables and tags

Device variables and tags are user-defined key/value values that can be assigned to devices. Tags can be used to add additional meta-data to devices and variables can be used for configured integrations (e.g. ThingsBoard requires a per-device Access Token).

PostgreSQL integration

When configured in the lora-app-server.toml configuration file, this integration will write events into a PostgreSQL database. See the PostgreSQL Integration documentation for more information.

ThingsBoard integration

When configured as Application integration, this integration will write attributes and telemetry to the configured ThingsBoard instance. See the ThingsBoard Integration documentation for more information.

Improvements

• Speedup login with default admin / admin credentials (for low CPU power devices). (#320)
• Gateway ID, FPGA ID and AES-key widgets have been updated.
• Always display Class-C timeout field in Device Profile.

Bugfixes

• Fix Gen Application Key is no longer a mandatory field. (#322)
• Fix create organization user. (#323)

Upgrading

Before upgrading, you must enable the hstore extension for the LoRa App Server PostgreSQL database. Example commands assuming the database is named loraserver_as:

sudo -u postgres psql

Within the PostgreSQL prompt, enter the following queries:

-- change to loraserver_as database and enable extension
\c loraserver_as
create extension hstore;

-- exit the prompt
\q

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.

v3.0.0

Features

Firmware Update Over The Air (FUOTA)

This release provides an implementation of the FUOTA specification. Currently the deployment is limited to one device as we would like to gather feedback on this implementation first. However, in this implementation the deployment to groups of devices is taken into account. Note: this feature is experimental and the API might change.

Updated rxInfo / txInfo (live frame-logs)

The LoRa Server <> LoRa Gateway Bridge messages have been updated to make the downlink scheduling more flexible and generic. This change exposes these fields in the live gateway and device frame-logs.

Payload codec

The payload codec settings have been moved to the Device Profile. Codec settings set in the application configuration still remain functional, but new codec settings must be configured in the Device Profile.

Bugfixes

• Fix organization admin cannot add existing users. (#315)

Upgrading

Please upgrade LoRa Server first to v3 (see Changelog), then upgrade LoRa App Server to v3. This LoRa App Server release is fully backwards compatible.

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.

Improvements

• Make it possible in the API to move devices between applications.
• Add DevAddr to enqueue API call to LoRa Server so that LoRa Server can validate the session-keys are in sync.
• Add device details overview (UI).

Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.