Bot releases are hidden (Show)
Published by brocaar almost 5 years ago
This release renames LoRa Server to ChirpStack Network 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.
This decouples the storage / handling of gateway stats from the Network Server. This deprecates the GetGatewayStats
API method (will be removed in the next major version).
Next to the already existing HandleUplinkMetaData
method, this adds a HandleDownlinkMetaData
API method. The HandleUplinkMetaData
API call has been extended with more meta-data (e.g. DevEUI, payload size, ...) which can be used for accounting purposes.
Although not required, to benefit fully from the IDs for correlation feature, it is recommended to update LoRa Gateway Bridge to v3.3.0 (or later).
As the gateway stats are now forwarded to the Application Server API, in order to continue receiving gateway stats you must upgrade to LoRa App Server v3.4.0 (or later).
Published by brocaar about 5 years ago
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar about 5 years ago
Support for geolocation on multiple uplink frames has been added. Using the Device Profile the geolocation "buffer" can be configured.
Prometheus metrics have been added to the MQTT, Azure and Google Cloud Platform backends.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar about 5 years ago
gRPC API metrics can now be exposed using a Prometheus metrics endpoint. In future releases, more metrics will be exposed using this endpoint.
Even when no application-payload is sent, this can still provide valuable information to the end-application (e.g. data-rate, RX attributes, the fact that the device is 'alive'). (#408)
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
Legacy code related to older gateway structures have been removed. All gateway messages are now based on the Protobuf messages.
Previously, each topic was configured separatly. To be consistent with LoRa Gateway Bridge v3, this has been re-factored into "events" and "commands".
The Azure integration (Cloud to Device) has been improved.
When LoRa Server receives a RXTimingSetupAns
mac-command, it will always respond to the device, even when this results in sending an empty frame.
LoRa Server v3 depends on LoRa Gateway Bridge v3! It is recommended to upgrade to the latest LoRa Server v2 release (which is forwards compatible with the LoRa Gateway Bridge v3), upgrade all LoRa Gateway Bridge installations to v3 and then upgrade LoRa Server to v3.
It is also recommended to update your LoRa Server configuration file. See Configuration for more information.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
A DevAddr
field has been added to the MulticastQueueItem
API field. When this field is set, LoRa Server will validate that the current active security-context has the same DevAddr
and if not, the API returns an error.
This prevents enqueue calls after the device (re)joins but before the new AppSKey
has been signalled to LoRa App Server.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
mqtt2to3
sub-commandThis sub-command translates MQTT messages from the old topics to the new topics (gw > ns) and backwards (ns > gw) and should help when migrating from v2 to v3 MQTT topics (see below).
This sub-command can be started as (when using the Debian / Ubuntu package):
/etc/init.d/loraserver-mqtt2to3 start
systemctl start loraserver-mqtt2to3
From the CLI, this can be started as:
loraserver mqtt2to3
As soon as all LoRa Gateway Bridge instances are upgraded to v3, this is no longer needed.
Using the Azure integration, it is possible to connect gateways using the Azure IoT Hub service. This feature is still experimental and might (slightly) change.
As a preparation to upgrade to LoRa Server v3, it is recommended to update the MQTT topic configuration to:
uplink_topic_template="gateway/+/event/up"
stats_topic_template="gateway/+/event/stats"
ack_topic_template="gateway/+/event/ack"
downlink_topic_template="gateway/{{ .MAC }}/command/down"
config_topic_template="gateway/{{ .MAC }}/command/config"
Together with the mqtt2to3
sub-command (see above), this stays compatible with LoRa Gateway Bridge v2, but also provides compatibility with LoRa Gateway Bridge v3. Once LoRa Server v3 is released, it is recommended to first upgrade all LoRa Gateway Bridge instances to v3 and then upgrade LoRa Server to v3.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.