[Feature Request]: Config backup and restore as part of OTA flow

[DaneEvans]

Checklist

• [x] I have used the search function for OPEN ISSUES to see if someone else has already submitted the same feature request.

• [x] I have also used the search function for CLOSED ISSUES to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.

• [x] I will describe the request with as much detail as possible.

• [x] This request contains only one single feature, not a list of multiple (related) features.

• [x] I have read and understood the Contribution Guidelines.

• [x] I agree to follow this project's Code of Conduct

Contact Details

No response

Feature or improvement you want

• [ ] Allow backup and restore of channels
• [ ] add it to the flow

Why should this be added?

to encourage people to do the updates, by reassuring them that their config will be restored.

Screenshots / Drawings / Technical details

No response

[github-actions[bot]]

Thank you for your detailed feature request! However, it seems we're missing some important information that could help in assessing the feasibility of your suggestion.

Could you please provide:

• Version information (e.g., the version of the software or environment this feature applies to)?
• Any specific reproduction steps or scenarios where this feature would be beneficial?
• Expected behavior if this feature were implemented and actual behavior without it?

This information would be invaluable in understanding your request better. Thank you!

[DaneEvans]

Bad bot. #3910 didn't work.

[jamesarich]

IME upgrading the firmware shouldn't nuke the channel config.. unless doing a wipe first (which hasn't been implemented as part of the fw upgrade module yet)

[DaneEvans]

But if it works fully we can recommend erase and update for larger jumps, which solves a lot of odd behaviour in firmware.

[RCGV1]

@jamesarich upgrading from an old version to a new one will nuke config