Skip to content

Commit 894d2ff

Browse files
committed
Update changelog. Bump version.
1 parent 3eec483 commit 894d2ff

File tree

2 files changed

+46
-1
lines changed

2 files changed

+46
-1
lines changed

docs/config.toml

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,5 +55,5 @@ theme = "chirpstack-hugo-theme"
5555
weight = 7
5656

5757
[params]
58-
version = "3.9.0"
58+
version = "3.10.0"
5959
component = "chirpstack-network-server"

docs/content/overview/changelog.md

+45
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,51 @@ description: Lists the changes per ChirpStack Network Server release, including
99
---
1010
# Changelog
1111

12+
## v3.10.0
13+
14+
### Features
15+
16+
#### Multi-downlink commands and ACKs
17+
18+
With this feature, ChirpStack Network Server will send all downlink opportunities
19+
(e.g. RX1 and RX2) at once to the gateway, reducing the number of roundtrip in
20+
case of failures. Previously ChirpStack Network Server would send the
21+
next downlink opportunity on a received nACK. In case of a retry, this saves one
22+
roundtrip reducing the risk of a failed downlink due to network latency. The
23+
gateway will always send at most one downlink.
24+
25+
**Note:** This feature requires ChirpStack Gateway Bridge v3.9 or later, but is
26+
backwards compatible with previous versions, in which case ChirpStack Network
27+
Server will fallback into the old behavior. This backwards compatibility has some
28+
overhead, which can be controlled by the `multi_downlink_feature` configuration
29+
variable.
30+
31+
#### Disable device
32+
33+
This feature makes it possible to (temporarily) disable a device, in which case
34+
uplinks are ignored.
35+
36+
#### Join Server integration
37+
38+
The Join Server integration has been updated, so that it is no longer required
39+
to rely on DNS resolving of the Join Server. It is now possible to configure
40+
a per JoinEUI endpoint of the Join Server.
41+
42+
#### Geolocation cleanup
43+
44+
This removes the Geolocation Server integration (relying on [LoRa Cloud](https://www.loracloud.com/))
45+
from ChirpStack Network Server. The reason for this is that there are various
46+
options for geolocation, some of them relying on the decrypted FRMPayload,
47+
e.g. in case of Wifi and GNSS sniffing. To provide one unified integration,
48+
this integration has been moved to [ChirpStack Application Server](https://www.chirpstack.io/application-server/).
49+
50+
**Note:** This will deprecate [ChirpStack Geolocation Server](https://www.chirpstack.io/geolocation-server/)
51+
as v3.11 will provide a per-application configurable LoRa Cloud integration.
52+
53+
### Improvements
54+
55+
* Expose to Application Server if received uplink was confirmed or unconfirmed.
56+
1257
## v3.9.0
1358

1459
### Features

0 commit comments

Comments
 (0)