Feature - Firmware OTA Update exposed to user #98
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
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 everyone,
Previously, the FOTA (Firmware Over-The-Air) feature was implemented only as an internal example and was not accessible to users.
With this PR, the Firmware OTA update functionality is now properly exposed to users through the
on_firmware_receivedcallback. Users can assign their own function to this callback, which will be triggered when a new firmware is received. This allows for custom handling of the firmware update process.Users can also report the update status using the update_firmware_info method for better control over the update process.
Additionally, I’ve removed the dummy checksum failure from the library code and moved it to the example. This keeps the core library clean and avoids misleading behavior during actual use.
Feedback is very welcome—please let me know if you have suggestions for improvement or see any potential issues.
Best regards,
Leo Granier
Wiifor