ChirpStack Application Server is an open-source LoRaWAN application-server.
MIT License
Bot releases are visible (Hide)
Published by brocaar over 6 years ago
Improvements:
application/[applicationID]/node/[devEUI]/error
MQTT topic.Pre-compiled binaries are available at: https://www.loraserver.io/lora-app-server/overview/downloads/
Published by brocaar over 6 years ago
Features:
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/
Published by brocaar over 6 years ago
Features:
Improvements:
Bugfixes:
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
Published by brocaar over 6 years ago
Improvements:
Bugfixes:
Published by brocaar over 6 years ago
Features:
Bugfixes:
Published by brocaar over 6 years ago
Features:
/api/devices/{devEUI}/frames
(formerly Device.GetFrameLogs
)Device.StreamFrameLogs
).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.
Published by brocaar over 6 years ago
Bugfixes:
/
prefix in two UI links causing a redirect to the login page.Published by brocaar over 6 years ago
Features:
Device last seen timestamp is now stored and displayed in device list
In the service-profile, it is now possible to set the
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:
info
debug
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 the vendor
folder
(which is not part of the repository anymore) and run make 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)Published by brocaar almost 7 years ago
Features:
This removes the following CLI options:
--ns-ca-cert
--ns-tls-cert
--ns-tls-key
See for more information:
Improvements:
Bugfixes:
applicationID
showing all device-profile namesPublished by brocaar almost 7 years ago
Features:
LoRa App Server is now able to decode (uplink) and encode (downlink)
payloads using the following per application configurable codecs:
base64
encoded data will be exposed)See Applications
documentation for instructions how to configure this option.
Published by brocaar almost 7 years ago
Changes:
Downlink device-queue
fCnt
to which the notification is related.Downlink device-queue API (/api/devices/{devEUI}/queue
)
DELETE /api/devices/{devEUI}/queue/{id}
endpoint (as removingfCnt
gaps).DELETE /api/devices/{devEUI}/queue
to flush the whole device-queue.Class-C
Bugfixes:
Improvements:
This release depends on LoRa Server 0.23.0. Upgrade LoRa Server first.
After upgrading LoRa App Server, it will migrate the remaining
device-queue items to the LoRa Server database.
Published by brocaar almost 7 years ago
Bugfixes:
Published by brocaar almost 7 years ago
Bugfixes:
Published by brocaar almost 7 years ago
Bugfixes:
RxInfo
length validation as this slice is empty when/api/node/...
prefix of downlink queue into /api/device/...
DownlinkQueue...
gRPC methods and structs into DeviceQueue...
.Published by brocaar almost 7 years ago
Note: this release brings many changes! Make sure (as always) to make a
backup of your PostgreSQL and Redis database before upgrading.
Changes:
Data-model refactor to implement service-profile, device-profile and
routing-profile storage as defined in the
LoRaWAN backend interfaces.
Application users have been removed to avoid complexity in the API
authorization. Users can still be assigned to organizations.
LoRa App Server can now connect to multiple LoRa Server
instances.
LoRa App Server exposes a Join-Server API (as defined in the LoRaWAN backend
interfaces document), which LoRa Server uses as a default join-server.
E-mail and note field added for users.
Adaptive-datarate configuration has been moved to LoRa Server.
OTAA RX configuration has been moved to LoRa Server.
API changes:
New API endpoints:
/api/device-profiles
(management of device-profiles)/api/service-profiles
(management of service-profiles)/api/network-servers
(management of network-servers)/api/devices
(management of devices, used to be /api/nodes
, settingsUpdated API endpoints:
/api/applications
(management of applications, most of the settings are now part of the device-profile)/api/gateways
(management of gateways, network-server field has been added)Removed API endpoints:
/api/applications/{id}/users
(management of application users)/api/nodes
(management of nodes, has been refactored into /api/devices
)Note: these changes also apply to the related gRPC API endpoints.
Note: this release brings many changes! Make sure (as always) to make a
backup of your PostgreSQL and Redis database before upgrading.
Note: When LoRa App Server is running on a different server than LoRa Server,
make sure to set the --as-public-server
/ AS_PUBLIC_SERVER
(default localhost:8001
).
This release depends on the latest LoRa Server release (0.22).
Start with updating LoRa Server first. See also the
LoRa Server changelog.
LoRa App Server will perform the data-migration when the --db-automigrate
/
DB_AUTOMIGRATE
config flag is set. It will:
Published by brocaar about 7 years ago
Improvements:
Published by brocaar about 7 years ago
Features:
Note: this release requires LoRa Server 0.21+ as the gateway ping feature
depends on the 'Proprietary' LoRaWAN message-type.
Bugfixes:
Published by brocaar about 7 years ago
Features:
Improvements:
Bugfixes:
Published by brocaar about 7 years ago
Features:
Note: This feature is dependent on LoRa Server
version 0.20.0+.