-
Notifications
You must be signed in to change notification settings - Fork 145
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
CFG Holder automatisch Update Alert Message #1214
Comments
That's just a warning that's displayed when you choose the automatic updates if you are coming from a custom build I believe. Are you coming from a custom build? If your Tasmota upgrade flow is valid it should be fine. |
yes before that was a custom build |
That message will always be displayed as a warning whenever you do an automatic upgrade unfortunately. Perhaps we could provide a setting to permanently dismiss it in the settings. |
Yes, it would be better because you think you have to do something |
That sounds like a better suggestion! Thanks Might make the UI a bit slow as this warning is triggered from the BE after querying all devices but could be feasible unless we render it on the UI. |
Read STATUS1 when creating the module |
Hello
just testing tasmoadmin
I currently only have one module installed to test
For me, when I want to update my device, I get this message automatically
Attention: If you previously changed the CFG_HOLDER, it is now reset. This means that the default user_config.h will be loaded from the Tasmota GIT and your previous settings will be overwritten!
The CFG Holder is like the original setting, see device data
10:22:15.266 MQT: STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"Küche_Nachtlicht","OtaUrl":"http://ota.tasmota. com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:00:34","StartupUTC":"2024-07-17T09:21:41 ","Sleep":50,"CfgHolder":4617,"BootCount":3,"BCResetTime":"2024-07-17T10:12:05","SaveCount":8,"SaveAddress":"F4000"} }
what is wrong or is it a BUG
The text was updated successfully, but these errors were encountered: