First uplink fine, second fails with "Drop uplink message - Device not found"

[arjanvanb (Arjan)]

@ms_theloop

When a packet is sent and the downlink ack is not received, more packets are sent over and over again

If I understand correctly, then that’s a fault in the LoRaWAN protocol:

@cslorabox

LoRaWAN confirmed uplink isn’t very well thought out, as if its the ack that is lost, the node will never get another for that sequence number and instead will simply retry until its give up limit. Generally you’re better off doing your own application-level confirmation, not only because of that, but because for many applications it make as much sense to retry with fresher data as it does to keep trying to get increasingly stale data through.

@ms_theloop

According to the guidelines, should I make my posts a bit shorter?

I like details!