I am encountering an issue on downlink messages.
My first installation was on Google Cloud, and thought that this issue may be due to a misconfig, and decided to put everything in one box, but the issue still persists.
I realized there was an issue when no downlink messages was displayed when looking at data and frames in the web app console, and also that my gateway was constantly sending the downlink message after my device sent an uplink, even if it was unconfirmed.
In other words, Chirpstack stack is believeing that sending the downlink message failed, constantly retries as it keeps it in the queue, and on each try the gateway is actually sending the message through the air.
After analyzing Semtech UDP datagrams, My LoRaWAN gateway is apparently dealing with v1 (byte 0). In v1, the gateway doesn’t acknoweldge (TX_ACK) it accepted the (PULL_RESP) downlink message for transmission.
Also I see that Chirpstack sends v1 Semtech datagrams to my gateway, which is correct.
So I suspect that a Chirpstack component, probably the network server, is waiting for this ack to define the downlink message has been accepted by the gateway, stops retrying, and displays it in the console.
Uplink messages are handled properly.
Logs will follow this message as I don’t have access to my test env yet, but if anybody has an idea on why this is behaving like this, it is very welcome.