Describe the Enhancement
If there is something wrong with the backend or noise causes a bit to be flipped and the data get "send" but is not inserted into the database. Currently the data will be removed from the TX buffer and the data will be lost. Adding a response from Dirtviz back to the soil power sensor can create a check that must return success before the data is removed. If an error is returned the upload is tried again
Benefits
Increased reliability -> less data loss due to unforeseen errors
Possible Drawbacks
Having a lot of downlink messages could violate limits on TTN and LoRaWAN in general. According to these docs we can only downlink 10 times per day per device.
More power usage from downlink messages
Additional Context
There is the concept of confirmed uplink and downlink messages as part of LoRaWAN. I haven't looked into it but it could be related to what this issue is trying to enhance.
Describe the Enhancement If there is something wrong with the backend or noise causes a bit to be flipped and the data get "send" but is not inserted into the database. Currently the data will be removed from the TX buffer and the data will be lost. Adding a response from Dirtviz back to the soil power sensor can create a check that must return success before the data is removed. If an error is returned the upload is tried again
Benefits Increased reliability -> less data loss due to unforeseen errors
Possible Drawbacks
Additional Context There is the concept of confirmed uplink and downlink messages as part of LoRaWAN. I haven't looked into it but it could be related to what this issue is trying to enhance.