Closed wateras closed 5 years ago
The ack is sent by the Semtech packet-forwarder, LoRa Gateway Bridge only forwards this ACK. So when the packet-forwarder does not send ACKs, LoRa Gateway Bridge won't either.
Can you confirm if the Semtech packet-forwarder sends ACKs? You will find some helpful commands here: https://www.loraserver.io/guides/troubleshooting/gateway/.
The ack is sent by the Semtech packet-forwarder, LoRa Gateway Bridge only forwards this ACK. So when the packet-forwarder does not send ACKs, LoRa Gateway Bridge won't either.
Can you confirm if the Semtech packet-forwarder sends ACKs? You will find some helpful commands here: https://www.loraserver.io/guides/troubleshooting/gateway/.
I did not see the received downlink data log from the log of the gateway program. Did the gateway bridge not receive the downlink data pushed by the server at all? At present, our server architecture is a gateway bridge deployed on the server. I also deployed a bridge on the arm a7 platform. I found that the communication also has problems. The phenomenon is that the server sometimes does not see the uplink data, but the mqtt client software does. You can subscribe to the gateway/mac/rx message.
LoRa Server not "seeing' (rejecting) data can have different causes, like session-keys and / or frame-counters that are out of sync. That is a different topic.
Your is question is why you don't see .../ack
messages and this is likely because your packet-forwarder doesn't send them. This feature was initially not available. The best would be to use tcpdump
to debug the (UDP) frames sent between the packet-forwarder and LoRa Gateway Bridge.
Is this a bug or a feature request?
What did you expect?
What happened?
What version are your using?
How can your issue be reproduced?
Could you share your log output?