Add ability to forceupdate via wifi with a single call on 2.x #1531
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
CapnBry
changed the title
pkendall64
approved these changes
Apr 16, 2022
AlessandroAU
approved these changes
Apr 16, 2022
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.
This backports part of #1371 (forceupdate). No firmware can be forceupdate'd over wifi by the configurator until the firmware already on the device actually allows it.
Getting this in the 2.x releases (that come at a moment's notice) will allow a migration path across target names (environments) with the 3.0 forceupdate PIO targets.
I really don't want to backport all of 1371 to maintenance, but at least this will allow a user running 2.4.1 or 2.5.0 or above to forceupdate when their target name changes in 3.0.