Retry upon first failure (including timeout) in any tasmota update command #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mmand To account for possible device rebooting which can happen at any time after many tasmota update commands, which combines with a deficiency in the HTTPAdapter session handler and results in an update command never timing out, set a timeout and retry manually just the once (per command) after any errors. Multiple reboots are allowed per playbook, but any given command will only be allowed to timeout the once, to prevent endless loops.
|
@spacelama thank you for your contribution! I have tested it and can confirm that this is working! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To account for possible device rebooting which can happen at any time after many tasmota update commands, which combines with a deficiency in the HTTPAdapter session handler and results in an update command never timing out, set a timeout and retry manually just the once (per command) after any errors. Multiple reboots are allowed per playbook, but any given command will only be allowed to timeout the once, to prevent endless loops. Fixes #31