Allow definition of MY_OTA_RETRY and MY_OTA_RETRY_DELAY #1241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
Playing with OTA firmware update, and struggling a bit because of the small number of retries and short retry delay. Essentially, a radio disturbance during 2.5s can lead to a failure of the OTA. This caused most uploads to fail in my situation.
Would you consider allowing the user to change MY_OTA_RETRY and/OR MY_OTA_RETRY_DELAY in order to influence their OTA process?