# 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:** 18

<div class="post-metadata">

**Author:** ![gigi130358](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/gigi130358/32/36137_2.png) [@gigi130358](https://www.thethingsnetwork.org/forum/u/gigi130358)\
**Post date:** [February 22, 2019, 1:54pm UTC](https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825/18 "2019-02-22T13:54:28Z")

</div>

Sorry, may be I wasn’t clear enough.  
The last test wasn’t carried out with one of the four nodes that give me the original problem, because I could’t conect with them to see theirs log.  
For check if the adr commnad sent by TTN reach the node, I used another lora node (“The Things Node”).  
In the Arduino IDE debug console of this node, I’m able to see the downlink msg that I manually sent from the TTN console, but when the TTN console shows an adr command sent from TTN to “The Things Node” after 64 uplinks, there is not trace of this msg in the Arduino IDE debug console of the node.

---

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