Manually adding node via ABP

[piyush s]

Hi

I have manually added the mDot node in the conduit mlinux using the lora-query tool as below
lora-query -a 01234567 C 0000111122223333 [DEVEUI] 0123456701234567012345670123456701234567012345670123456701234567

Now if I send some data from the mDot using the AT commands, it is not getting received in the conduit. I use below mosquito command for listening to that:
mosquitto_sub -t lora/+/up -v
Interestingly, when I use the below command
mosquitto_sub -t lora/+/packet_recv I get the receiving message, yet the data isn’t correct. I mean when I send ‘1234’ from the mDot, I received “QGdFIwEABwABdZh0nYyT71I=” as data. Though with the earlier command with ‘/up’ I do not get even that.
Does anybody know what am I missing ?

thanks

[Jason Reiss]

see output of:
> lora-query -n

and

> lora-query -c 01234567

A manually joined node should have DevAddr, NetSKey and DataSKey set.
AppEUI and AppKey values are used for OTA join.
DevEUI is used to report to the application on Conduit.

LoRa Network Server

[piyush s]

Thanks Jason for the response.

I queried with the ‘-c’ option and observed the different value ‘2b7e151628aed2a6abf7158809cf4f3c’ under the network session key. I guess this is because of the encryption. I even updated my lora-query -a command with these values, I get same error.
There is no output under ‘/up’ but there is some output under ‘/packer_recv’ but not the correct one.
Can you tell me what is the difference between
lora/+/up & lora/+/packet_recv?

[piyush s]

Jason,

I was mistakenly removing the space between NSK and DSK in lora-query command. Looked thoroughly to find that out. It worked. But it ‘d be good to know the difference between ‘/up’ and ‘/packet_recv’.

thanks,

[Jason Reiss]

https://www.google.com/search?q=multitech+lora+packet_recv

[Author]

Posts