Repository navigation
Add companion Wi-Fi OTA maintenance controls and delivery tooling - #4
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem and behavior
Add the previously completed companion controls for the firmware Wi-Fi OTA maintenance work on top of current
master, without resubmitting the BLE client already merged in #3.The full maintenance flow depends on the companion firmware draft PR; 3rdEyez/ESP-3RDEYE#3. Local package metadata preflight does not replace firmware cryptographic signature verification.
Validation and limits
Seven App tool tests and 156 Flutter tests passed; Flutter analysis and BLE document/vector contract checks passed. Firmware-side synthetic regressions also pass. No new Android release signing, installation, device OTA or deployment is performed for this PR.
Draft pending real-device wireless OTA and migration acceptance. Firmware migration interruption during bootloader/table writes requires manual recovery; it is not covered by app rollback.