Bot releases are visible (Hide)
Published by brocaar almost 5 years ago
v3.4.0
This release renames LoRa Server to ChirpStack Network Server. See the Rename Announcement for more information.
Published by brocaar almost 5 years ago
v3.3.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.
Forwards gateway stats to Application Server API
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).
Extend Network Controller API
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.
Improvements
- Add PostgreSQL max open / idle connections settings. (#437)
Bugfixes
- Recover Azure Service-Bus queue client on Receive error.
- Fix unreturned errors. (#428)
- Fix send on closed channel. (#434)
- Fix logging DevEUI in join flow. (#438)
Upgrading
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
v3.2.1
Improvements
- Improve environment variable based configuration for list of structures.
- Update LoRa Server dependencies to their latest versions.
Bugfixes
- Fix Azure Unauthorized access. 'Listen' claim(s) are required to perform this operation. error. (see azure-service-bus-go/#116)
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar about 5 years ago
v3.2.0
Features
Multi-frame geolocation
Support for geolocation on multiple uplink frames has been added. Using the Device Profile the geolocation "buffer" can be configured.
Prometheus metrics
Prometheus metrics have been added to the MQTT, Azure and Google Cloud Platform backends.
Bugfixes
- Fix NetID 3 & 4 NwkID prefix according to the errata published by the LoRa Alliance.
- Fix RX2 timing when RXDelay is > 0. (#419)
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar about 5 years ago
v3.1.0
Features
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
Always forward uplink data (even on fPort = 0)
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)
Bugfixes
- Revert LoRaWAN 1.1 Class-C device always joins as Class-A. (#395)
- Fix TXParamSetupReq mac-command not being sent. (#397)
- Fix ignoring packets received on multiple frequencies. (#401)
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
v3.0.2
Improvements
- Make max idle / max active Redis connections configurable.
Bugfixes
- Fix Azure IoT Hub detached link issue / recover on AMQP error.
- Fix load device-session twice from database. #406.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
v3.0.1
Bugfixes
- Fix ADR setup. #396
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
v3.0.0
Features
Improvements
Legacy code removed
Legacy code related to older gateway structures have been removed. All gateway messages are now based on the Protobuf messages.
MQTT topic refactor
Previously, each topic was configured separatly. To be consistent with LoRa Gateway Bridge v3, this has been re-factored into "events" and "commands".
Azure integration
The Azure integration (Cloud to Device) has been improved.
RXTimingSetupAns acknowledged
When LoRa Server receives a RXTimingSetupAns mac-command, it will always respond to the device, even when this results in sending an empty frame.
Upgrading
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
v2.8.2
Bugfixes
- Fix ADR setup. #396
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/.
Published by brocaar over 5 years ago
Improvement
Validate DevAddr on enqueue
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
v2.8.0
Features
Add mqtt2to3 sub-command
This 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 startsystemctl 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.
Azure integration
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.
Upgrading
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/.