# ADR problems - node of the same type have different ADR behaviour

**URL:** <https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825>\
**Category:** v2 Backend\
**Created:** [February 17, 2019, 8:58am UTC](https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825 "2019-02-17T08:58:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 17, 2019, 9:18am UTC](https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825/2 "2019-02-17T09:18:23Z")

</div>

To see if TTN is sending an ADR request for that second node:

- What’s the payload size of that downlink of the second node? (Where for the first node it’s 34 bytes.) Posting the actual payload might help too, so we can [tell if the ADR is as expected](https://www.thethingsnetwork.org/forum/t/what-are-these-port-0-downlink-messages/22330/4).

- Does clicking the downlinks give you any additional trace information that relates to ADR?

(Also, I find the frame counters confusing. Like the first screenshot shows low values for the uplink frame counter; I wonder when TTN resets the ADR statistics it gathered when a node is restarted. And the second screenshot shows it’s the 3rd downlink, so the first downlinks were transmitted before TTN got 20 uplinks too. I guess that’s hard to debug.)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825)._