Lora Conduit ACK's not sent black list – third party end node

[RADU HORGA]

Our partner discovered a new problem with the Conduit and Lora and third party end nodes. I will describe it:

After testing them for about a month, some nodes stopped working properly. They use ACKs, and the Conduit is not sending back the ACK anymore for the messages from the nodes to the Conduit.
This happens on the oldest nodes, and they stopped working one after another, 4 of them already.
If to the same node they assign a new DEVICE EUI, the node works again, and the ACKs from the Conduit are received again, so it seems to be a problem of the Conduit lorawan side. Is like this number, the DEVICE EUI of the node, were on a black list on the Conduit.

The configuration of the node:
mac set deveui 0004A30B001B2837
mac set devaddr 00000001
mac set appeui 54454……………….
mac set appkey 544C4B5F53495354……………..
mac set adr on
mac set ar on
mac set rxdelay1 3000
mac set ch freq 3 864100000
mac set ch freq 4 864300000
mac set ch freq 5 864500000
mac set ch freq 6 864700000
mac set ch freq 7 864900000
mac set ch dcycle 3 0
mac set ch dcycle 4 0
mac set ch dcycle 5 0
mac set ch dcycle 6 0
mac set ch dcycle 7 0
mac set ch drrange 3 0 7
mac set ch drrange 4 0 7
mac set ch drrange 5 0 7
mac set ch drrange 6 0 7
mac set ch drrange 7 0 7
mac set ch status 3 on
mac set ch status 4 on
mac set ch status 5 on
mac set ch status 6 on
mac set ch status 7 on
mac join otaa
ok
accepted

Enlace OK

mac tx cnf 10 01,01,0D,10,07,12,A4,BA,18,7B,F0,DE,00,C8,01,00,00,2B,34,30,2E,35,35,00,30,30,30,00,00,2D,30,30,33,2E,34,39,00,30,30,30,00,
ok
mac_err –> this should be normally mac_tx_ok

The message reaches the Conduit and it’s processed by the node-red, but the node does not receive the ACK confirmation, so it shows this “mac_err”
The only way to recover the node is to change decive eui mac set deveui 0004A30B001B2837. Then the node receives the ACK.

Did anyone else report this problem?

[Author]

Posts