It’s each address in EEPROM that has a limit, not the entire EEPROM, so each address will last 2,845 days, then you can just switch to different addresses. You have 1032 to play with.
Unfortunately that’s unlikely. 10k writes indicates that the “EEPROM” is only standard flash. It’s common for microcontrollers to emulate “EEPROM” via flash because it’s much, much cheaper. Usually the only difference is that anything called “EEPROM” is easier to access during operation. Some microcontrollers have multiple flash sectors tied together to distribute the wear and thus increase lifetime).
Anyways, the important point is, you can only erase groups of 64 bytes (or 128 or something else; depends on the specific chip) - these groups are called pages. So every write to a page requires the entire page to be erased and rewritten. Btw. this is why you have “EEPROM” emulation. The emulation hides the erase/rewrite stuff since it’s not only complicated but often timing sensitive, too.
Long story short, without further details on how Nextion exactly implemented the “EEPROM” you can’t make the assumption you made.
Then, I try to set the dims to 0, and set it to 25 when I wanted the display. It works fine.
In fact, Dim is setting in the EEPROM memory (I think) because, the setting operates even after powering off/on thge module.
dims is the variable that updates the EEPROM,
dim only changes the runtime behavior. I’d think of
dims as a function that updates
dim and then writes the new value to the EEPROM.
While Nextion gives some sort of lifetime for its EEPROM, it doesn’t give any info about the
bauds variables, how they work exactly and what wear is to be expected. F.ex. it’s unclear whether they write to EEPROM/flash when the new value matches the current one.