Skip to content

Commit 8cbf2f9

Browse files
committed
Update changelog. Bump version.
1 parent f9eb89f commit 8cbf2f9

File tree

2 files changed

+40
-1
lines changed

2 files changed

+40
-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.7.0"
58+
version = "3.8.0"
5959
component = "chirpstack-network-server"

docs/content/overview/changelog.md

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

12+
## v3.8.0
13+
14+
### Features
15+
16+
#### Downlink gateway randomization
17+
18+
When sending a downlink response, ChirpStack Network Server will select from
19+
the list of gateways with a given (configurable) margin, a random gateway
20+
for the downlink. This should result in a better downlink distribution across
21+
gateways. In case non of the gateways are within the configured margin, the
22+
best gateway is selected (old behavior).
23+
24+
#### Monitoring
25+
26+
The monitoring configuration has been updated so that it is possible to
27+
configure both a [Prometheus](https://prometheus.io/) endpoint at `/metrics`
28+
and healthcheck endpoint at `/health`. This change is backwards compatible,
29+
but to use the `/health` endpoint you must update your configuration.
30+
31+
#### Forward gateway metadata to AS
32+
33+
By forwarding gateway metadata to the (ChirpStack) Application Server,
34+
information like serial number, temperature, ... could be stored by the
35+
Application Server for various use-cases. The configuration of metadata
36+
is covered by the [ChirpStack Gateway Bridge](https://www.chirpstack.io/gateway-bridge/).
37+
38+
### Improvements
39+
40+
#### Downlink LoRaWAN frame logging
41+
42+
Previously the first downlink scheduling attempt was logged (visible in the
43+
ChirpStack Application Server under the Gateway / Device LoRaWAN frames). This
44+
has been changed so that the scheduling attempt acknowledged by the gateway
45+
is logged. E.g. when RX1 fails, but RX2 succeeds this will log the RX2 attempt.
46+
47+
### Bugfixes
48+
49+
* Update gRPC dependency to fix 'DNS name does not exist' error. ([#426](https://github.com/brocaar/chirpstack-application-server/issues/426))
50+
1251
## v3.7.0
1352

1453
### Features

0 commit comments

Comments
 (0)