Releases: brocaar/chirpstack-application-server
0.20.1
Improvements:
- Skip frame-counter check can now be set per device (so it can be used for OTAA devices).
- Publish codec decode errors to the
application/[applicationID]/node/[devEUI]/error
MQTT topic.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/
0.20.0
Features:
- (Gateway) channel-configuration has been refactored into gateway-profiles.
- This requires LoRa Server 0.26.0 or up.
- This removes the channel-configuration related gateway API methods.
- This adds gateway-profile API methods.
Bugfixes:
Upgrade notes:
In order to automatically migrate the existing channel-configuration into the
new gateway-profiles, first upgrade LoRa Server and restart it. After upgrading
LoRa App Server and restarting it, all channel-configurations will be migrated
and associated to the gateways. As always, it is advised to first make a backup
of your (PostgreSQL) database.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/
0.19.0
Features:
- Global search on organizations, applications, devices and gateways.
- Display live device events (the same data as publised over MQTT).
See also Event logging.
Improvements:
- When creating an application, show a warning when no service-profile exists.
- When creating a gateway, show a warning when no network-server has been associated.
- When creating a device, show a warning when no device-profile exists.
Bugfixes:
- Fix organization selector (which would sometimes show an empty value on select).
- Fix user selector when assigning an user to an organization (which would sometimes show an empty value on select).
Upgrade notes:
Before upgrading, the PostgreSQL pg_trgm
extension needs to be enabled.
Assuming the LoRa App Server database is configured as loraserver_as
this
extension could be enabled using the commands below.
Start the PostgreSQL prompt as the postgres
user:
sudo -u postgres psql
Within the PostgreSQL prompt, enter the following queries:
-- change to the LoRa App Server database
\c loraserver_as
-- enable the extension
create extension pg_trgm;
-- exit the prompt
\q
0.18.2
Improvements:
- Gateway discovery configuration has been moved to network-server configuration.
- Important: when you have the gateway discover feature configured,
you need to re-add this configuration under network-servers (web-interface).
- Important: when you have the gateway discover feature configured,
- Expose the following MQTT options for the MQTT gateway backend:
- Configurable MQTT topics (uplink, downlink, join, ack, error)
- QoS (quality of service)
- Client ID
- Clean session on connect
- Expose LoRa Server version and configured region through the network-server
API endpoint. - Websocket client automatically re-connects on connection error (#221)
Bugfixes:
- The Class-C enabled checkbox was displayed twice in the web-interface.
- Organization dropdown was not autocompleting correctly.
0.18.1
Features:
- Expose Class-B fields in device-profile web-interface form.
- Note: Class-B support is implemented since LoRa Server 0.25.0.
Bugfixes:
- Fix factory preset frequency field in device-profile form.
0.18.0
Features:
- LoRa App Server uses a new configuration file format.
See configuration for more information. - Frame-logs for device are now streaming and can be downloaded as JSON file.
- Note: the
/api/devices/{devEUI}/frames
(formerlyDevice.GetFrameLogs
)
endpoint has changed (and the gRPC method has been renamed toDevice.StreamFrameLogs
). - You need LoRa Server 0.24+ in order to use this feature.
- Note: the
- Added streaming frame-logs for gateways (which also can be downloaded as JSON file).
- You need LoRa Server 0.24+ in order to use this feature.
- Support MQTT client certificate authentication (#201).
Upgrade notes:
When upgrading using the .deb
package / using apt
or apt-get
, your
configuration will be automatically migrated for you. In any other case,
please see configuration.
0.17.1
Bugfixes:
- Fix missing
/
prefix in two UI links causing a redirect to the login page. - Fix typo in TLS certificate loading causing error failed to find certificate PEM data in certificate input (thanks @Francisco_Rivas)
0.17.0
Features:
-
Device last seen timestamp is now stored and displayed in device list
-
In the service-profile, it is now possible to set the
- Device-status request frequency
- Report battery level
- Report margin
When the interval is set to > 0 and reporting of this status is enabled,
then this information is displayed in the device list and exposed over MQTT
and the configured integrations. -
Extra logging has been added:
- gRPC API calls (to the gRPC server and by the gRPC clients) are logged
asinfo
- Executed SQL queries are logged as
debug
- gRPC API calls (to the gRPC server and by the gRPC clients) are logged
-
A warning is displayed in the web-interface when creating a service-profile
when no network-server is connected. -
A warning is displayed in the web-interface when creating a device-profile
when the organization is not associated with a network-server.
Internal changes:
-
The project moved to using dep as vendoring
tool. In case you run into compiling issues, remove thevendor
folder
(which is not part of the repository anymore) and runmake requirements
. -
The front-end code has been updated to use React 16.2.0 and all dependencies
have been updated.
Bugfixes:
--gw-ping-dr 0
is now handled correctly (#204)
0.16.1
Features:
- Implement client certificate validation for incoming application-server API connections.
- Implement client certificate validation for incoming join-server API connections.
- Implement client certificate for API connections to LoRa Server.
This removes the following CLI options:
--ns-ca-cert
--ns-tls-cert
--ns-tls-key
See for more information:
- LoRa Server configuration
- LoRa App Server configuration
- LoRa App Server network-server management
- https://github.com/brocaar/loraserver-certificates
Improvements:
- Optional note field (users) has been changed to textarea.
- Description field of the gateway has been changed to textarea.
Bugfixes:
- Fix device-profile permissions in UI for organization admins.
- Fix device-profile list per
applicationID
showing all device-profile names
and IDs on the same network-server as the service-profile associated with the
given application.
0.16.0
Features:
-
LoRa App Server is now able to decode (uplink) and encode (downlink)
payloads using the following per application configurable codecs:- None (only the raw
base64
encoded data will be exposed) - Cayenne LPP (data will be encoded / decoded using the
Cayenne LPP encoding) - Custom JavaScript codec functions (you can provide your own encoding /
decoding functions in JavaScript)
- None (only the raw
See Applications
documentation for instructions how to configure this option.