I need clarification on whether Chirpstack will try and retransmit a confirmed Class C downlink if no ack received from node. My testing determines that is does not attempt any retries.
I see my confirmed downlink message in the device queue and i also see my initial downlink frame in the Chirpstack Lorawan Frames panel in the web browser.
No subsequent downlink messages are sent and the downlink message is deleted from the queue after the expiry of the Class-C downlink retries time set in the device profile.
In an 2017 message on the forum Brocaar mentioned maybe implement a retries parameter on the downlink MQTT/restAPI message but it doesn’t appear as an option as far as i can see from the API definition.
Is it up to the application to implement retry functionality - if so what is the purpose of keeping the item on the queue?
Thanks for any clarity around this.