Considering the RxWindow durations and duty cycle limitations of a given region, the limitation on the retransmission window would result in allowing only a couple of retries, and the rest of the retries get dropped.
Steps to Reproduce
...
What do you see now?
The network server drops the retries from the device received after the retransmission window with the device not found error.
What do you want to see instead?
The retransmission window size needs to account for the RxDelay durations and the duty cycle limitations of the region.
Environment
TTS v3.11.3 CH
How do you propose to implement this?
Increase the retransmission window size for now and long-term make it dependent on duty cycle limitations.
How do you propose to test this?
...
Can you do this yourself and submit a Pull Request?
Summary
Number of retries allowed for confirmed uplinks currently on NS end:
NbTrans
for all confirmed frames in versions since MAC v1.0.45
for confirmed frames in versions before MAC v1.0.4Also, Network Server has a max retransmission delay - the latest retransmission may arrive no later than
RX_DELAY + 11 seconds
after the first uplink. Ref: https://github.com/TheThingsIndustries/lorawan-stack-support/issues/354Considering the
RxWindow
durations andduty cycle
limitations of a given region, the limitation on the retransmission window would result in allowing only a couple of retries, and the rest of the retries get dropped.Steps to Reproduce
...
What do you see now?
The network server drops the retries from the device received after the retransmission window with the
device not found
error.What do you want to see instead?
The retransmission window size needs to account for the
RxDelay
durations and theduty cycle
limitations of the region.Environment
TTS v3.11.3 CH
How do you propose to implement this?
Increase the retransmission window size for now and long-term make it dependent on duty cycle limitations.
How do you propose to test this?
...
Can you do this yourself and submit a Pull Request?
No