ChirpStack Deduplication Issue with Multiple Gateways

Hello everyone,


I am a beginner using ChirpStack v4 as a network server to manage LoRaWAN devices, and I have two very close gateways (Milesight UG56-868M) that receive messages from the same Milesight EM300-DI device.

The problem is that ChirpStack does not seem to apply deduplication correctly, as I receive two identical uplinks with the same fCnt and data, but with a different gatewayId. Here is an example of what I receive:


(In other words, one uplink arrives via Gateway A and the other via Gateway B)


How can I configure ChirpStack to process only one of the two uplinks?


Thank you very much,

Juan

How close is the device to the gateways and the gateways to each other? Being too close can cause issues like this (<5ish meters)

Hello Liam,

The gateways are 1km away (Milesight UG56-868M), and therefore, the Milesight EM300-DI is more than 5 meters away. I noticed that both gateways receive the same packet from the EM300, and in Tenants/ChirpStack/Applications/Test/Devices, it appears duplicated and is published via MQTT twice.

Is there a way to filter it so that if one gateway has already received the packet, the other ignores it? Otherwise, the EM300 ends up showing two data packets as if it had sent them twice.

Hi Juan, if you have disabled frame-counter validation in the device configuration tab you’ll see duplicate frames if the timing between them exceeds the deduplication_delay in chirpstack.toml.

1 Like