Releases: brocaar/chirpstack-network-server
v3.0.2
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/.
v3.0.2-test.1
v3.0.2-test.1
v3.0.1
v2.8.2
v3.0.0
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/.
v3.0.0-test.3
v3.0.0-test.3
v3.0.0-test.2
v3.0.0-test.2
v2.8.1
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/.
v3.0.0-test.1
v3.0.0-test.1
v2.8.0
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/.