Add UPGRADE <version_number> as an option to UPGRADE. #213
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
* Allow cmnd of UPGRADE 3.1.13 which will only try to upgrade it the version specified is higher than our current one. This allows a "cmnd/<group_topic>/upgrade 3.1.13" to be issued repeatedly to cause tardy devices to upgrade via the OTAURL, but cause no interruption to devices already running the specified version (or newer). * Fix an issue where "UPGRADE 1" cmnds were being accepted due to poor parsing. e.g. "UPGRADE 1xx" & "UPGRADE 1.2.3" would always trigger an update.
|
@crankyoldgit maybe worth reimplementing on the new repo: https://github.com/arendst/Sonoff-Tasmota ? |
|
Implemented in Sonoff-Tasmota version 5.2.3 soon to be released. |
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.
specified is higher than our current one.
This allows a "cmnd/<group_topic>/upgrade 3.1.13" to be issued repeatedly
to cause tardy devices to upgrade via the OTAURL, but cause no interruption
to devices already running the specified version (or newer).
e.g. "UPGRADE 1xx" & "UPGRADE 1.2.3" would always trigger an update.