Continuous join process

End Devices (Nodes)
1

Hello,

the problem is that the JOIN process is not completed.

The end node has already had a successful join once.

Now in the free field, the join takes place without completion.

20:51:16

mk-cc10-hdc1080-h

Forward join-accept message

  • link

20:51:14

mk-cc10-hdc1080-h

Accept join-request

  • arrow_upward

20:51:00

mk-cc10-hdc1080-h

Forward join-accept message

  • link

20:50:58

mk-cc10-hdc1080-h

Accept join-request

  • arrow_upward

20:50:57

mk-cc16-hdc1080-h

Forward uplink data message

{
  "name": "js.join.accept",
  "time": "2022-05-26T18:50:58.590922184Z",
  "identifiers": [
    {
      "device_ids": {
        "device_id": "mk-cc10-hdc1080-h",
        "application_ids": {
          "application_id": "mk-cc-hdc1080-h"
        }
      }
    },
    {
      "device_ids": {
        "device_id": "mk-cc10-hdc1080-h",
        "application_ids": {
          "application_id": "mk-cc-hdc1080-h"
        },
        "dev_eui": "70B3D57ED004xxxx",
        "join_eui": "032434DD2E48213A",
        "dev_addr": "260B0EDF"
      }
    }
  ],
  "correlation_ids": [
    "rpc:/ttn.lorawan.v3.NsJs/HandleJoin:01G40VAA4FN7QP1DZ8DBHE922T"
  ],
  "origin": "ip-10-100-13-7.eu-west-1.compute.internal",
  "context": {
    "tenant-id": "CgN0dG4="
  },
  "visibility": {
    "rights": [
      "RIGHT_APPLICATION_TRAFFIC_READ",
      "RIGHT_APPLICATION_TRAFFIC_READ"
    ]
  },
  "unique_id": "01G40VAA4YVJVCAPMPV5CDQV71"
}


/----------------------------------------------------------------------------------------------------------------------

{
  "name": "as.up.join.forward",
  "time": "2022-05-26T18:51:00.386188224Z",
  "identifiers": [
    {
      "device_ids": {
        "device_id": "mk-cc10-hdc1080-h",
        "application_ids": {
          "application_id": "mk-cc-hdc1080-h"
        }
      }
    },
    {
      "device_ids": {
        "device_id": "mk-cc10-hdc1080-h",
        "application_ids": {
          "application_id": "mk-cc-hdc1080-h"
        },
        "dev_eui": "70B3D57ED004xxxx",
        "join_eui": "032434DD2E48213A",
        "dev_addr": "260B0EDF"
      }
    }
  ],
  "data": {
    "@type": "type.googleapis.com/ttn.lorawan.v3.ApplicationUp",
    "end_device_ids": {
      "device_id": "mk-cc10-hdc1080-h",
      "application_ids": {
        "application_id": "mk-cc-hdc1080-h"
      },
      "dev_eui": "70B3D57ED004xxxx",
      "join_eui": "032434DD2E48213A",
      "dev_addr": "260B0EDF"
    },
    "correlation_ids": [
      "as:up:01G40VABWW3VBWCVFAN2AXT9ZE",
      "gs:conn:01G3R44FEQPXH79X8SPJSTPCCJ",
      "gs:up:host:01G3R44FEZTFMBP709MPADDYY4",
      "gs:uplink:01G40VAA4AYWWYH5VD6EYYHZ0Z",
      "ns:uplink:01G40VAA4C5Z0B4EQ5DZ79XKGF",
      "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G40VAA4CZF0P2X0G402NNXCK",
      "rpc:/ttn.lorawan.v3.NsAs/HandleUplink:01G40VABWWHXTMD64GCXRNHBHM"
    ],
    "received_at": "2022-05-26T18:51:00.380991301Z",
    "join_accept": {
      "session_key_id": "AYEBtSiUjzG9kqE+YVYd1Q==",
      "received_at": "2022-05-26T18:50:58.572258791Z"
    }
  },
  "correlation_ids": [
    "as:up:01G40VABWW3VBWCVFAN2AXT9ZE",
    "gs:conn:01G3R44FEQPXH79X8SPJSTPCCJ",
    "gs:up:host:01G3R44FEZTFMBP709MPADDYY4",
    "gs:uplink:01G40VAA4AYWWYH5VD6EYYHZ0Z",
    "ns:uplink:01G40VAA4C5Z0B4EQ5DZ79XKGF",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G40VAA4CZF0P2X0G402NNXCK",
    "rpc:/ttn.lorawan.v3.NsAs/HandleUplink:01G40VABWWHXTMD64GCXRNHBHM"
  ],
  "origin": "ip-10-100-12-198.eu-west-1.compute.internal",
  "context": {
    "tenant-id": "CgN0dG4="
  },
  "visibility": {
    "rights": [
      "RIGHT_APPLICATION_TRAFFIC_READ",
      "RIGHT_APPLICATION_TRAFFIC_READ"
    ]
  },
  "unique_id": "01G40VABX2PG5VBPKJ049GC8VR"
}

What is the problem?

Greetings

E_T

2

My crystal ball has been clouded lately but my guess would be that the node does not receive the join accept downlink. What are the numbers (rssi and snr) of the join request?

Oh, BTW, could you use the formatting tools </> to format the json content next time? Makes for easier reading.

3

Thank you kersing,

that could be the problem!

The node has poor receiving conditions.

Greetings

E_T