Skip to content
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

BK7231T and OTA update - I lose every time autoexec #1385

Open
DamianLisu opened this issue Oct 10, 2024 · 3 comments
Open

BK7231T and OTA update - I lose every time autoexec #1385

DamianLisu opened this issue Oct 10, 2024 · 3 comments

Comments

@DamianLisu
Copy link

I have the same two thermometers based on BK7231T.
Both have the same problem. After OTA update (Web Application -> OTA -> Select file -> Start OTA) I am losing my autoexec file. After each update I have to recreate them. List Filesystem it doesn't show anything.
Autoexec is not complicated:

startDriver TuyaMCU
tuyaMcu_setBaudRate 9600
tuyaMcu_defWiFiState 4
startDriver NTP
ntp_timeZoneOfs +2

linkTuyaMCUOutputToChannel 1 val 0
linkTuyaMCUOutputToChannel 2 val 1
linkTuyaMCUOutputToChannel 9 val 2

delay_s 1
//F -> C
SetChannel 2 1

I will add that I have several devices with BK7231N and the described problem with the update does not occur here. I tried to restore the RF partition but without success.
I have no idea what's going on.

@DamianLisu DamianLisu changed the title BK7231T and OTA update - every time loss autoexec BK7231T and OTA update - I lose every time autoexec Oct 10, 2024
@DeDaMrAzR
Copy link
Contributor

Can you share what was the previous version that you've updated from and to what version you updated that to?

There was a breaking change on T modules at some point that will erase LFS if OTA is done form an older version.

@DamianLisu
Copy link
Author

Of course, basically, the version doesn't matter now, because performing an upgrade from a version to the same version causes this problem. I currently have a version of 1.17.743.

@Wolfieeewolf
Copy link

This is a long-standing issue

#1305 and #1010

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants