Skip to content

Commit

Permalink
Update changelog. Bump version.
Browse files Browse the repository at this point in the history
  • Loading branch information
brocaar committed May 25, 2020
1 parent 3eec483 commit 894d2ff
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -55,5 +55,5 @@ theme = "chirpstack-hugo-theme"
weight = 7

[params]
version = "3.9.0"
version = "3.10.0"
component = "chirpstack-network-server"
45 changes: 45 additions & 0 deletions docs/content/overview/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,51 @@ description: Lists the changes per ChirpStack Network Server release, including
---
# Changelog

## v3.10.0

### Features

#### Multi-downlink commands and ACKs

With this feature, ChirpStack Network Server will send all downlink opportunities
(e.g. RX1 and RX2) at once to the gateway, reducing the number of roundtrip in
case of failures. Previously ChirpStack Network Server would send the
next downlink opportunity on a received nACK. In case of a retry, this saves one
roundtrip reducing the risk of a failed downlink due to network latency. The
gateway will always send at most one downlink.

**Note:** This feature requires ChirpStack Gateway Bridge v3.9 or later, but is
backwards compatible with previous versions, in which case ChirpStack Network
Server will fallback into the old behavior. This backwards compatibility has some
overhead, which can be controlled by the `multi_downlink_feature` configuration
variable.

#### Disable device

This feature makes it possible to (temporarily) disable a device, in which case
uplinks are ignored.

#### Join Server integration

The Join Server integration has been updated, so that it is no longer required
to rely on DNS resolving of the Join Server. It is now possible to configure
a per JoinEUI endpoint of the Join Server.

#### Geolocation cleanup

This removes the Geolocation Server integration (relying on [LoRa Cloud](https://www.loracloud.com/))
from ChirpStack Network Server. The reason for this is that there are various
options for geolocation, some of them relying on the decrypted FRMPayload,
e.g. in case of Wifi and GNSS sniffing. To provide one unified integration,
this integration has been moved to [ChirpStack Application Server](https://www.chirpstack.io/application-server/).

**Note:** This will deprecate [ChirpStack Geolocation Server](https://www.chirpstack.io/geolocation-server/)
as v3.11 will provide a per-application configurable LoRa Cloud integration.

### Improvements

* Expose to Application Server if received uplink was confirmed or unconfirmed.

## v3.9.0

### Features
Expand Down

0 comments on commit 894d2ff

Please sign in to comment.