Get DevAddr in OTA mode

Home › Forums › General › Get DevAddr in OTA mode

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • November 29, 2016 at 10:15 am #15697
    David Chaudet
    Participant

    When I try to obtain a address for my device, I have this log :

    14:23:45:751|DEBUG| Rx on 868500000, rssi: -90 snr: 80
14:23:45:752|DEBUG| Received frame: type: Join Request
14:23:45:752|INFO| Received join request
14:23:45:752|DEBUG| BUFFER: 000001006032d5b3709013006032d5b370a513
14:23:45:753|DEBUG| App EUI: 70-b3-d5-32-60-00-01-00
14:23:45:753|DEBUG| Dev EUI: 70-b3-d5-32-60-00-13-90
14:23:45:753|DEBUG| Nonce: 000013a5
14:23:45:754|TRACE| SQL query = SELECT appkey FROM appkeys WHERE appeui = "70b3d53260000100" AND deveui = "70b3d53260001390";
14:23:45:756|WARNING| Tossing join request, invalid NET EUI and no record of Dev EUI

    I would like to know what means “invalid NET EUI and no record of Dev EUI”.
    I checked the deveui and the appeui and both are corrects.
    I’ve already read some documents at this link without any clue to solve my problem.

    At this topic, it is mentionned that firmware have to be upgrade but mine are :

    lora-network-server - 1.0.8-r0.0
lora-packet-forwarder - 1.4.1-r9.0
lora-query - 1.0.2-r1.0

    Which seem to be good.

    Is there anyone who could give me some tips to solve the issue?
    Thanks.

    • This topic was modified 8 years, 4 months ago by David Chaudet.
    November 29, 2016 at 11:02 am #15702
    Jason Reiss
    Keymaster

    Have you read the getting started and ensured the network settings match on mdot and Conduit?

    Getting Started with LoRa Conduit AEP (LoRa Configuration)

    Getting Started with LoRa Conduit mLinux (LoRa Configuration)

    I would like to know what means “invalid NET EUI and no record of Dev EUI”.

    This means the AppEUI in the join request did not match the lora network server setting and a record of the device was not found in the database.

    lora-query utility can be used to register a device with unique appkey appeui pair, this will be used if the conduit NetEUI NetKey does not match.

    LoRa Network Server

    November 29, 2016 at 11:07 am #15703
    David Chaudet
    Participant

    Thanks for your answer.
    Yes, I read the getting started documents.
    And I already registered the device via the command :
    lora-query -a 0 A 0000000000000000 70b3d53260001390 a4fe7622cebb98406cd99a8565c6a82f
    Deveui : 70b3d53260001390
    Appkey : a4fe7622cebb98406cd99a8565c6a82f

    November 29, 2016 at 11:13 am #15704
    Jason Reiss
    Keymaster

    Did you register with the AppEUI value? Or do you have this matching the Conduit global setting?

    Try.
    lora-query -a 1 A 70b3d53260000100 70b3d53260001390 a4fe7622cebb98406cd99a8565c6a82f

    November 29, 2016 at 11:13 am #15705
    David Chaudet
    Participant

    And if I do the command :
    lora-query -c 00:00:00:00 (No address already configured in OTA mode), I have this :

    Net Addr     Dev EUI                  Class  App EUI                  AppKey                            Net Session Key                   Data Session Key
00:00:00:00  70-b3-d5-32-60-00-13-90  A      00-00-00-00-00-00-00-00  a4fe7622cebb98406cd99a8565c6a82f  2b7e151628aed2a6abf7158809cf4f3c  2b7e151628aed2a6abf7158809cf4f3c
    November 29, 2016 at 11:23 am #15706
    David Chaudet
    Participant

    Thanks for your quick answer.
    When I try your command (after deleted the device registered), the device has the address 00:00:00:01.
    The error doesn’t appeared anymore. Thanks a lot!

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.