ChirpStack Application Server is an open-source LoRaWAN application-server.
MIT License
Bot releases are hidden (Show)
Published by brocaar almost 5 years ago
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).
This is the first release providing .rpm packages for CentOS and RedHat. (#383
All definitions are now imported from github.com/brocaar/chirpstack-api/go
. When using the gRPC API, you must update your imports.
Implement re-connect in case of an Azure Service-Bus error. This to work partly around azure-service-bus-go/issues/149.
Implement support for configuring multiple endpoints in the HTTP integration.
Handlink of the received uplinks has been improved to reduce the number of required database transactions.
Published by brocaar almost 5 years ago
Published by brocaar almost 5 years ago
This release renames LoRa App Server to ChirpStack Application Server. See the Rename Announcement for more information.
Published by brocaar almost 5 years ago
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.
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".
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.
In the gateway list page, it is now possible to show a map showing all the gateways and their states.
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.
Published by brocaar about 5 years ago
Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.
Published by brocaar about 5 years ago
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 metics have been implemented for the Join Server API interface.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.
Published by brocaar about 5 years ago
The LoRa App Server web-interface has now the option to:
gRPC API metrics can now be exposed using a Prometheus metrics endpoint.
In future releases, more metrics will be exposed using this endpoint.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.
Published by brocaar over 5 years ago
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).
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.
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.
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/.
Published by brocaar over 5 years ago
Published by brocaar over 5 years ago
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.
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.
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.
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/.
Published by brocaar over 5 years ago
DevAddr
to enqueue API call to LoRa Server so that LoRa Server can validate the session-keys are in sync.Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/.