Third party LoRA end-device OTA fail

[eason lai]

Hello there,

I am encounter the OTA fail between my end-device and the Conduit.

After checked few articles on the forum, the end-device SQL search on my Conduit is different with others.

Here is my log of OTA flow (won’t update the new device into SQL DB):

13:38:31:807|TRACE| SQL query = SELECT appkey FROM appkeys WHERE appeui = “0880088008800880” AND deveui = “3ff000b41ff80054”;

13:38:31:809|WARNING| Tossing join request, invalid NET EUI and no record of Dev EUI

 

The OTA log from this article(Automatically update the new device into SQL DB):
https://forum.pycom.io/topic/59/multitech-conduit/15

12:4:42:760|TRACE| SQL query = SELECT address FROM nodes WHERE deveui = “70b3d54996276e62”;
12:4:42:761|INFO| Device not found in DB
12:4:42:762|INFO| assigning address: 1
12:4:42:763|TRACE| SQL query = SELECT address FROM nodes where deveui = “70b3d54996276e62”;
12:4:42:765|TRACE| SQL query = INSERT INTO nodes (address, appeui, deveui, authenticationkey, encryptionkey, lastdownmsgseqno, class) VALUES (“00000001”, “ada4dae3ac12676b”, “70b3d54996276e62”, “2b7e151628aed2a6abf7158809cf4f3c”, “2b7e151628aed2a6abf7158809cf4f3c”, 0, “A”)

Please help me to figure out the difference. thank you.

The following is the lora setting of Conduit. I have referenced few versions on the forum.
{
“__v” : 1,
“db” : “/var/config/lora/lora-network-server.db”,
“lora”: {
“netID”: “010203”, /* netID for beacon packets */
“frequencyBand”: “915”, /* US=”915″, EU=”868″ */
“channelPlan”: “US915”,
“frequencySubBand”: 1, /* Sub-band for US operation, 1-8 */
“rx1DatarateOffset”: 0, /* Datarate offset for mote rx window 1 sent in join response (0-3) */
“rx2Datarate”: 12, /* Datarate for mote rx window 2 sent in join response (7-12) */
“maxTxPower”: 14, /* Max Tx power (dBm), -6 to 26 */
“joinByteOrder”: “MSB”,
“enabled”: true
},
“udp”: {
“appPortUp”: 1784, /* port for user-developed application use */
“appPortDown”: 1786 /* port for user-developed application use */
},
“addressRange”: {
“start”: “00:00:00:01”, /* address range used for mDots */
“end”: “FF:FF:FF:FE”
},
“network”: {
“leasetime”: 0, /* time until mDot join expires (minutes) or 0 for no expiration */
“eui”: “8008800880088009”,
“key”: “0B-7E-15-16-28-AE-D2-A6-AB-F7-15-88-09-CF-4F-3C”,
“public”: true /* set to false for private LoRa network with mDots + Conduit */
},
“log” : {
“console” : true,
“syslog” : false,
“level” : 100, /* error=10, warn=20, info=30, debug=50, trace=60, max=100 */
“path”: “/var/log/lora-network-server.log”
},
“mqtt”: {
“enabled”: true
},
“test” : {
“disableDutyCycle” : false,
“disableRxJoin1” : false,
“disableRxJoin2” : false,
“disableRxWindow1” : false,
“disableRxWindow2” : false
},
“whitelist” : {
“devices” : [],
“enabled” : false
}
}

[eason lai]

Thanks a lots for the help from Mulitech support.

The problem was caused by the mismatch AppEUI and wrong joinByteOrder between end-device and the Conduit.

[Author]

Posts