# V3 ADR always resets to SF7

**URL:** <https://www.thethingsnetwork.org/forum/t/v3-adr-always-resets-to-sf7/46302>\
**Category:** TTN V2 to V3 Upgrade\
**Created:** [April 2, 2021, 3:53pm UTC](https://www.thethingsnetwork.org/forum/t/v3-adr-always-resets-to-sf7/46302 "2021-04-02T15:53:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![nichtvongestern](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/nichtvongestern/32/35697_2.png) [@nichtvongestern](https://www.thethingsnetwork.org/forum/u/nichtvongestern)\
**Post date:** [April 3, 2021, 2:28pm UTC](https://www.thethingsnetwork.org/forum/t/v3-adr-always-resets-to-sf7/46302/6 "2021-04-03T14:28:00Z")

</div>

I use unconfirmed uplinks. 5-10 per hour.  
I can’t say for sure if this case was really reduced to SF7, because I didn’t record the console. But I have seen it before, although the receiving values were not so good.  
The ADR from the v3-stack is unfortunately bad in my experience and should be adjusted.I measure meteorological data and these should be more or less complete.

Found another case where it is the same.

> [@ADR standard activated in V3 applications?](https://www.thethingsnetwork.org/forum/t/adr-standard-activated-in-v3-applications/44698/3):
>
> Whenever I change DR to 2 (SF10) an “Link ADR request” is enqueued afterwards and SF changes to SF 7 after 1-2 datasets with SF10. This “Link ADR request” has “name”: “ns.mac.link\_adr.request”, “data”: { “[type.googleapis.com/ttn.lorawan.v3.MACCommand.LinkADRReq](http://type.googleapis.com/ttn.lorawan.v3.MACCommand.LinkADRReq)”, “data\_rate\_index”: 5, “tx\_power\_index”: 5,…

This is how it looks then, on 03/28 I turned off my TTIG.  
Then I waited, but ADR comes to no satisfactory settings. Almost everything is lost

```auto
datetime , id ,f_cnt, gateway, RSSI, SNR, SF,
(2021, 4, 1, 3, 9, 54), 13831, 671, 'packetbroker', -117.0, -15.2, 10, 
(2021, 3, 30, 23, 21, 44), 13831, 501, 'packetbroker', -118.0, -13.2, 11, 
(2021, 3, 30, 23, 14, 44), 13831, 500, 'ifm-imst', -120.0, -12.75, 11,
(2021, 3, 30, 23, 7, 44), 13831, 499, 'ifm-imst', -121.0, -13.5, 11, 
(2021, 3, 30, 22, 53, 43), 13831, 497, 'ifm-imst', -119.0, -13.75, 10,
(2021, 3, 30, 22, 39, 43), 13831, 495, 'ifm-imst', -120.0, -14.25, 10,
(2021, 3, 30, 22, 32, 44), 13831, 494, 'ifm-imst', -121.0, -14.0, 10, 
(2021, 3, 30, 22, 25, 43), 13831, 493, 'packetbroker', -117.0, -14.5, 10, 
(2021, 3, 30, 21, 30, 43), 13831, 485, 'packetbroker', -118.0, -12.0, 10,
(2021, 3, 30, 21, 3, 23), 13831, 481, 'ifm-imst', -120.0, -16.0, 10, 
(2021, 3, 30, 20, 49, 43), 13831, 479, 'packetbroker', -117.0, -14.8, 10, 
(2021, 3, 30, 20, 29, 23), 13831, 476, 'ifm-imst', -118.0, -14.0, 10, 
(2021, 3, 30, 19, 42, 43), 13831, 469, 'packetbroker', -117.0, -11.5, 10, 
(2021, 3, 30, 19, 28, 43), 13831, 467, 'packetbroker', -118.0, -12.0, 10,
(2021, 3, 29, 18, 2, 43), 13831, 306, 'packetbroker', -111.0, -12.2, 9, 
(2021, 3, 29, 17, 47, 23), 13831, 304, 'packetbroker', -111.0, -13.5, 9, 
(2021, 3, 29, 17, 41, 23), 13831, 303, 'packetbroker' -116.0, -11.0, 9, 
(2021, 3, 28, 20, 15, 13), 13831, 174, 'packetbroker', -72.0, 7.75, 7, 
(2021, 3, 28, 20, 4, 33), 13831, 173, 'packetbroker', -75.0, 9.5, 7, 

```

This was not the case with TTN-v2. ADR adapted more slowly, but actually about 50% of the packets arrived after successful adaptation.  
Can I use ttn-lw-cli to add my own values?

```auto
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-data-rate-index
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-tx-power-index
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-nb-trans

```

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/v3-adr-always-resets-to-sf7/46302)._