Hi!
I have a Dragino Door Sensor LDS02, configured with Confirmed Uplinks.
This morning, I have an uplink at 7:06am (door opened).
Then, at 8:23, I closed the door, and the uplink was directly flagged as re-transmission. This is strange because there is no “first uplink” received.
The deduplication ids are different, and the frame counter seems to be ok, as you can see the previous and next frames (35 & 37).
What can be the reason? Why did the NS ignore this message?
Does this happen often? What is the behaviour with f_count verification disabled? Chirpstack should only trigger that error when f_count is repeated… Maybe the device doesn’t increment properly and actually sent fcnt 35 twice (then tried to confirm the failing uplink 3 times) then went to 37?
This is also the only explaination I see. So I will disable f_count verification to try to catch a “bad increment behavior”
Maybe chirpstack send a NbTrans command to the device? Check the tab LoRaWAN frames on chripstack.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
