When setting this to 0s, the ChirpStack Network Server will start processing the uplink as soon as it receives the first message, this essentially disables de-duplication. In order to collect data from other receiving gateways, this must be > 0, e.g. 200ms (in which case the NS will wait 200ms to receive data from other gateways).
Our goal is building own geolocation server.
If you enable the json marshaler in the ChirpStack Application Server configuration (instead of the default json_v3) you will receive all the fine-timestamp information that the ChirpStack Gateway Bridge sends to the NS. This makes it possible to implement your geolocation solution using the information published by the AS. That might save you some work
Chripstack Network Server receives two uplink frames, then collect it.
Is it sign of de-duplication mechanism is still working?
I’m double checking the configuration, nothing is wrong.
Here’s my network server configuration.
# Network-server settings.
# Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203)
# LoRaWAN regional band configuration.
# Note that you might want to consult the LoRaWAN Regional Parameters
# specification for valid values that apply to your region.
# See: https://www.lora-alliance.org/lorawan-for-developers
Network server version is 3.6.0, pre compiled binary.
Running on CentOS 7.