# Different gateway, suddenly no Join Accept received by RN2483 node, but all fine for another gateway or node

**URL:** <https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835>\
**Category:** Gateways\
**Created:** [February 23, 2018, 9:01am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835 "2018-02-23T09:01:16Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Afstkla](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/afstkla/32/11096_2.png) [@Afstkla](https://www.thethingsnetwork.org/forum/u/Afstkla)\
**Post date:** [February 23, 2018, 9:01am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/1 "2018-02-23T09:01:16Z")

</div>

Hi guys,

I’m trying out the Lorix One gateway, and while everything seems to be configured correctly, I do not seem to be able to receive any JoinAccept with my RN2483. A tester that I have laying around (not sure what the underlying module is) does successfully receive the JoinAccept, but the RN2483 never does.  
The weird thing is that with the Kerlink iFemtocell I usually use, everything works flawlessly.

This makes me assume that there’s some timing-related issue, but does anyone know how this can be verified/resolved? The two gateways are connected to exactly the same network, and both are shown as being connected in the TTN Console.

Thanks,  
Job

---

<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 23, 2018, 10:07am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/2 "2018-02-23T10:07:09Z")

</div>

As the other node does work it’s probably okay, so just to be sure: does TTN Console show the RN2483’s Join Accept? And does it show it for the expected gateway? What if you power down the first gateway?

If shown: does it use the same SF as with the other gateway? If it’s using SF12, then:

> [@Joining Adeunis RF Tester on TTN via OTAA](https://www.thethingsnetwork.org/forum/t/joining-adeunis-rf-tester-on-ttn-via-otaa/9686/3):
>
> The RN2483 failing to join on SF12 has been observed by several TTN users.

---

<div class="post-metadata">

**Author:** ![Afstkla](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/afstkla/32/11096_2.png) [@Afstkla](https://www.thethingsnetwork.org/forum/u/Afstkla)\
**Post date:** [February 23, 2018, 10:15am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/3 "2018-02-23T10:15:27Z")

</div>

TTN Console shows both JoinRequests, but the RN2483 never replies with ‘Accepted’.  
If we power up both gateways, we see both gateways receiving the JoinRequests. If we power down the iFemtocell, the RN2483 no longer replies with ‘accepted’ (although we still see the JoinRequest in the Console).

I’ll check the SF in a bit, but we use the 1.0.3 firmware on the RN2483 (and they’re actually RN2483A, rather than RN2483), so that should’ve fixed the SF12 problems.

EDIT: ~~The RN2483 only replies with ‘accepted’ when the iFemtocell is powered off. Don’t think the first sentence was clear enough.~~  
EDIT2: Apparently I’m not awake yet. Obviously, the RN2483 only replies with accepted when the iFemtocell is powered _on_…

---

<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 23, 2018, 10:17am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/4 "2018-02-23T10:17:57Z")

</div>

My guess is that the Lorix One is a single channel gateway, and that TTN does not think it supports downlinks? Then I’d guess that TTN would select the other gateway for the Join Accept, but maybe there’s a bug there.

---

<div class="post-metadata">

**Author:** ![Afstkla](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/afstkla/32/11096_2.png) [@Afstkla](https://www.thethingsnetwork.org/forum/u/Afstkla)\
**Post date:** [February 23, 2018, 10:18am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/5 "2018-02-23T10:18:51Z")

</div>

I’ve seen that happen before, but then the TTN Console also mentioned something like ‘no downlink gateway available’ or similar, which I haven’t seen this time.

---

<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 23, 2018, 10:19am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/6 "2018-02-23T10:19:16Z")

</div>

Note that TTN Console should show the Join Accept in the device’s Data page, _and_ in one of the gateways’ Traffic page. ([Screenshots](https://www.thethingsnetwork.org/forum/t/things-uno-not-joining-anymore/12772/5).)

---

<div class="post-metadata">

**Author:** ![Afstkla](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/afstkla/32/11096_2.png) [@Afstkla](https://www.thethingsnetwork.org/forum/u/Afstkla)\
**Post date:** [February 23, 2018, 10:21am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/7 "2018-02-23T10:21:10Z")

</div>

Now that I think of it more, if it would actually be a single-channel gateway, the field tester also shouldn’t work. But, the field tester does work. Which is what led me to the assumption that it’s a timing problem in the first place (assuming the RN2483 is more strict than the field tester)

---

<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 23, 2018, 10:23am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/8 "2018-02-23T10:23:02Z")

</div>

> [@Afstkla](#):
>
> But, the field tester does work.

…for which TTN may be using the other gateway for the Join Accept, if that gateway has a better reception of its Join Request…

If the Lorix One gateway is NOT single channel, then maybe somehow TTN still thinks it cannot do downlinks? Like maybe it’s not pulling for commands at all? (Again, I’d guess TTN would select the other gateway then as that also received the RN2483’s Join Request, but maybe there’s a bug there?)

As an aside: having multiple gateways in the same network should be fine: [2 gateways behind 1 router / port 1700?](https://www.thethingsnetwork.org/forum/t/2-gateways-behind-1-router-port-1700/10547)

---

<div class="post-metadata">

**Author:** ![Afstkla](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/afstkla/32/11096_2.png) [@Afstkla](https://www.thethingsnetwork.org/forum/u/Afstkla)\
**Post date:** [February 23, 2018, 10:36am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/9 "2018-02-23T10:36:40Z")

</div>

Sorry if I wasn’t clear, but I actually mean that the field tester works with _just_ the Lorix One plugged in.

So:  
iFemtocell + Lorix one: RN2483 **works** , field tester **works**  
Just iFemtocell: RN2483 **works** , field tester **works**  
Just Lorix One: RN2483 **_doesn’t_** work, field tester **works**

---

<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 23, 2018, 10:39am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/10 "2018-02-23T10:39:03Z")

</div>

Weird. But for the multiple gateways I’d still check _which_ of the gateways (if any) is sending the Join Accept then; it might still reveal some pattern.

Here’s some Markdown for you to copy and enhance 🙂

```markdown
Join Accepts according to the gateways' Traffic pages in TTN Console:

| Active gateway(s) | Join Accept RN2483 | Join Accept Field tester
| ---------------------- | :----------------: | :----------------------:
| iFemtocell + Lorix one | ??? | ???
| Just iFemtocell | iFemtocell | iFemtocell
| Just Lorix One | none | Lorix One

```

---

<div class="post-metadata">

**Author:** ![alexbn71](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/alexbn71/32/16965_2.png) [@alexbn71](https://www.thethingsnetwork.org/forum/u/alexbn71)\
**Post date:** [February 24, 2018, 10:40am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/11 "2018-02-24T10:40:51Z")

</div>

Hi, I’m trying in this days the same configuration. LORIXOne + RN2483 without problems. Double check that app eui and app key on RN2483 are the same configured under lororix one gateway instance in TTN. This is a common join reject, if not.

Alex

---

<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 24, 2018, 8:30pm UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/12 "2018-02-24T20:30:14Z")

</div>

> [@alexbn71](#):
>
> Double check that app eui and app key on RN2483 are the same configured under lororix one gateway instance in TTN.

Where would one configure devices _with specific gateways_ in TTN Console?

Gateways and applications/devices are unrelated. And as the Join Request is accepted when using another gateway, I’m quite sure the RN2483’s configuration must be okay.

---

<div class="post-metadata">

**Author:** ![alexbn71](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/alexbn71/32/16965_2.png) [@alexbn71](https://www.thethingsnetwork.org/forum/u/alexbn71)\
**Post date:** [February 26, 2018, 7:40am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/13 "2018-02-26T07:40:29Z")

</div>

You’re right I made a bit of confusion 🙂

---

<div class="post-metadata">

**Author:** ![tuftec](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/tuftec/32/30225_2.png) [@tuftec](https://www.thethingsnetwork.org/forum/u/tuftec)\
**Post date:** [September 8, 2018, 1:26am UTC](https://www.thethingsnetwork.org/forum/t/different-gateway-suddenly-no-join-accept-received-by-rn2483-node-but-all-fine-for-another-gateway-or-node/12835/14 "2018-09-08T01:26:04Z")

</div>

Did this issue ever get resolved.  
I am seeing a similar issue with a RAK831 gateway and a Things gateway.  
I have a a RAK811 that will join on both gateways but my LoPy4 will only join on the RAK gateway.  
Both gateways are multi-channel.  
I believe the issue might be related to the frequencies used during the OTAA process.  
My RAK811 node prefers to register using the primary channels at BW=125. The LoPy attempts to OTAA using the secondary channel at BW=500. My guess is that the RAK831 does not seem to care which channel is used where as the Things gateway may not like the secondary channel registration request.  
Has anyone else seen this issue?

Peter.
