Update changelog + docs. Bump version.

brocaar · Aug 20, 2019 · af46281 · af46281
1 parent 1bfd7f4
commit af46281
Show file tree

Hide file tree

Showing 4 changed files with 44 additions and 2 deletions.
diff --git a/docs/config.toml b/docs/config.toml
@@ -40,4 +40,4 @@ pygmentsUseClasses = true
     weight = 5
 
 [params]
-version = "3.1.0"
+version = "3.2.0"
diff --git a/docs/content/features/device-profile.md b/docs/content/features/device-profile.md
@@ -13,7 +13,7 @@ description: Defines the device capabilities and boot parameters needed by LoRa
 The device-profile defines the device capabilities and boot parameters that
 are needed by LoRa Server to "connect" with a device.
 
-## Fields / options
+## LoRaWAN Backend Interface
 
 The following fields are described by the
 [LoRaWAN Backend Interfaces specification](https://www.lora-alliance.org/lorawan-for-developers).
@@ -38,3 +38,10 @@ Fields marked with an **X** are implemented by LoRa Server.
 - [ ] **MaxDutyCycle** Maximum duty cycle supported by the End-Device
 - [X] **RFRegion** RF region name (automatically set by LoRa Server)
 - [ ] **Supports32bitFCnt** End-Device uses 32bit FCnt (mandatory for LoRaWAN 1.0 End-Device) (always set to `true`)
+
+## Geolocation buffer
+
+The following extra fields can be used to configure the geolocation buffer:
+
+- **GeolocBufferTTL** Maximum TTL for items in the geolocation buffer.
+- **GeolocMinBufferSize** Minimum required buffer size before using geolocation.
diff --git a/docs/content/features/geolocation.md b/docs/content/features/geolocation.md
@@ -25,6 +25,21 @@ will decrypt the fine-timestamp, before forwarding it to the geolocation-server.
 For getting this fine-timestamp decryption key, please contact your gateway vendor
 or Semtech.
 
+## Multi-frame geolocation
+
+LoRa Server support multi-frame geolocation to increase the geolocation accuracy.
+In the [Device Profile]({{<relref "device-profile.md">}}) it is possible to
+configure the:
+
+* TTL of each item in the geolocation buffer
+* Minimum buffer size before using geolocation
+
+Example:
+
+When the TTL is set to 5 minutes (300 seconds) and the minimum buffer size is
+set to 3, then geolocation will only be used when there are at least 3 frames
+in the geolocation buffer that are received within the last 5 minutes.
+
 ## Device location
 
 When LoRa Server (using the geolocation-server) is able to resolve the location

diff --git a/docs/content/overview/changelog.md b/docs/content/overview/changelog.md
@@ -9,6 +9,26 @@ description: Lists the changes per LoRa Server release, including steps how to u
 ---
 # Changelog
 
+## v3.2.0
+
+### Features
+
+#### Multi-frame geolocation
+
+Support for geolocation on multiple uplink frames has been added. Using the
+[Device Profile](https://www.loraserver.io/loraserver/features/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](https://lora-alliance.org/resource-hub/nwkid-length-fix-type-3-and-type-4-netids-errata-lorawan-backend-10-specification) published by the LoRa Alliance.
+* Fix RX2 timing when RXDelay is > 0. ([#419](https://github.com/brocaar/loraserver/issues/419))
+
 ## v3.1.0
 
 ### Features