# Join Request problem

**URL:** <https://www.thethingsnetwork.org/forum/t/join-request-problem/10596>\
**Category:** End Devices (Nodes)\
**Created:** [November 14, 2017, 10:58pm UTC](https://www.thethingsnetwork.org/forum/t/join-request-problem/10596 "2017-11-14T22:58:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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 15, 2017, 5:12pm UTC](https://www.thethingsnetwork.org/forum/t/join-request-problem/10596/4 "2017-11-15T17:12:46Z")

</div>

You’re right about the wiring; if you see packets then that’s probably okay.

> [@jimrm](#):
>
> The problem is the device address on the gateway traffic does not match the device address entered in the sketch.

Please make sure you got the terminology right. As you’re referring to a Join Request, I assumed this is an OTAA node. A Join Request uses the DevEUI, not a Device Address (DevAddr, which is calculated from a Join Accept).

If you’re looking in the local gateway log (rather than TTN Console) then I guess you compared with a node that does work, so I guess you know how to decipher the log then. But just to be sure: beware that many details are in reverse order in a LoRaWAN packet. (You could use [an online decoder](https://runkit.io/avbentem/lorawan-packet-decoder/branches/master) when unsure.)

If you’re seeing a Join Request with the wrong DevEUI in the Gateway Traffic in TTN Console (see [No Join Response from TTN](https://www.thethingsnetwork.org/forum/t/no-join-response-from-ttn/10469) for expected screenshots of gateway and application), then the node must be configured wrongly.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/join-request-problem/10596)._