-
-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid accidental downgrade (=bricking the device) #1927
Comments
I don't like the idea as it would prevent all users to downgrade if a version contains a mistake. |
just for curiosity: i ask, because i can not reproduce a brick if i downgrade to a lower version within the scope of the last few months. after that you can close this issue. thanks & greetings, |
I'm not advocating against the possibility to downgrade. Don't get me wrong. @MetaChuh The unit was running v24.3.31 and instead of installing v24.4.12 I uploaded v23.12.18 |
What about a new version field which indicates the "generation" (including memory layout, configuration file format and so on):
|
The downgrad to this version failed because of a bug in the upstream esp32 framework. |
This is not meant to be a "Arbeitsbeschaffungsmaßnahme" (work creation plan). If there was an efficient way for the software to detect an older version, a message like "warning: attempting downgrade, are you sure" is sufficient. Any other ideas? |
many ideas:
possible code solutions:
|
Is your feature request related to a problem? Please describe.
Well, it happed to me: I wanted to upgrade to the latest release but somehow I selected accidently an older version from the downloads folder.
The device rebooted and was obviously not available anymore.
I had to perform a complete reflash with the factory image and restore the configuration from backup.
Describe the solution you'd like
This problem might be easy to fix but some OpenDTU units might be installed in a not-so-easy-to-reach location.
I would like to suggest to
Lets discuss the impact or maybe other ideas which would help.
Thanks!
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: