Multitech Conduit AP 'Not OTAA joine yet...' issue (EU 868)

  • Hi everybody,

    I have updated my LoPy and my Multitech Conduit AP to the last firmwares, however I still get stuck in the 'Not yet joined...' loop, I've checked other topics but none gave me solution.

    Here is my code:

    from network import LoRa
    import time
    import ubinascii
    import pycom
    import socket
    # Colors
    off = 0x000000
    red = 0x7f0000
    green = 0x007f00
    blue = 0x00007f
    # Turn off hearbeat LED
    # LoRa region will be set when you update the firmware
    # it does not need to be explicitly stated  
    lora = LoRa(mode=LoRa.LORAWAN, region=LoRa.EU868, device_class=LoRa.CLASS_A, public = False)
    # OTAA authentication parameters
    dev_eui = ubinascii.unhexlify('70b3d5499f68dbb1')
    app_eui = ubinascii.unhexlify('af86e54a8730668c')
    app_key = ubinascii.unhexlify('48df5716b92753954f4a0331c68c303a')
    # join a network using OTAA (Over the Air Activation)
    lora.join(activation=LoRa.OTAA, auth=(dev_eui, app_eui, app_key), timeout=0)
    for i in range(3, 15):
        print("removed channel: " + str(i))
    lora.add_channel(index=0, frequency=868100000, dr_min=0, dr_max=5)
    print("added channel 868.1Mhz")
    lora.add_channel(index=1, frequency=868300000, dr_min=0, dr_max=5)
    print("added channel 868.3Mhz")
    lora.add_channel(index=2, frequency=868500000, dr_min=0, dr_max=5)
    print("added channel 868.5Mhz")
    lora.add_channel(index=3, frequency=867500000, dr_min=0, dr_max=5)
    print("added channel 867.5Mhz")
    # Loop until joined
    while not lora.has_joined():
        print('Not OTAA joined yet...')
    print('OTAA Joined')
    s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
    s.setsockopt(socket.SOL_LORA, socket.SO_DR, 4)
    i = 0
    while True:
        count = s.send(bytes([i % 256]))
        print('Sent %s bytes' % count)
        i += 1

    And here is my Gateway configuration:
    (multitech EU868

    It seems that the gateway is receiving join requests and that the requests are successful as per this screenshot :

    But I am still stuck in the loop:

    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...
    Not OTAA joined yet...

    Am I missing something ? Any idea ? Other than that ABP seems to work.

    Thank you in advance,


  • @bnjroos Yes, the RX1 and RX2 delay are specified in the LORaWAN regional settings. I did not look that up for every region, but the ones I recall use 5 and 6 seconds for OTAA join, and 1 and 2 seconds for other downlink messages as default.

  • @robert-hh Yeah that is what came to my mind afterwards when I read "Must match Dot settings", that it was tied to the node hardware, however it is specified in the LoRaWAN regional parameters if I am not mistaken ?

  • @bnjroos The PyCom software if configured for a 5 second RX1 delay for join. I could not test join at the RX2 window. can be configured to use RX1 or RX2, but it seems to use RX1 in any case. The configuration only affects the other dowlink messages.

  • @robert-hh True, I've modified that too, but what is weird is that in the Multitech documentation I found the following for Private Network:


    But indeed I've modified it to 5 at the same time i checked Disable Join Rx2 and it seems to work.

    Now I need to find out how to disable join Rx2 on !

  • @bnjroos The Join delay is 5 seconds, nor one second as shown in the screen dump.

  • I'll just answer myself as it seems that what was pointed out on another post was right, I disabled Join on RX2:

    And now it is working.

Pycom on Twitter