# ADR - not what I expected

**URL:** <https://www.thethingsnetwork.org/forum/t/adr-not-what-i-expected/10470>\
**Category:** LMIC\
**Created:** [November 6, 2017, 4:30pm UTC](https://www.thethingsnetwork.org/forum/t/adr-not-what-i-expected/10470 "2017-11-06T16:30:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [November 6, 2017, 5:50pm UTC](https://www.thethingsnetwork.org/forum/t/adr-not-what-i-expected/10470/5 "2017-11-06T17:50:22Z")

</div>

> [@cultsdotelecomatgmai](#):
>
> It appears that TTN is relying on receiving ADRACKReq on uplink

Yes, and reading the specification, I think that’s okay… See also [Does ADR require the use of confirmed uplinks? - #6 by arjanvanb](https://www.thethingsnetwork.org/forum/t/does-adr-require-the-use-of-confirmed-uplinks/9640/6)

~~To mitigate this, you could make the node send a confirmed uplink every now and then…~~

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/adr-not-what-i-expected/10470)._
