ESP32 and ESP8266 devices state persistent

[roberdlv]

Hello,

I have recently been using Esphome for a while, I have ESP32 and ESP8266 devices (before with Tasmota until now) and I wanted to know if there is a reliable way without damaging the flash to save the state or which is the most recommended (I use homeassistant integration, I don’t know if it can be done somehow store the state there so when the connection goes out or the light goes out, recover it persistently and not damage flash)

Opinions or recommendations? Thanks in advance

[Karosm]

preferences:
flash_write_interval:
default is 1min

works for esp32

[Masterzz]

It depends on application specific.

Me have f.e. Garland Switches, they toggled once or twice a day.
So, immediate state write to flash happens 1-2 times per day - any other period will wear flash more.

Can check those topics too:

Wifi keeps saving preferences

Considering how cheap esp boards are, I dont really consider it an issue. Replacing a 2$ esp board isnt exactly on the same level as replacing 2000$ devices. Its not realistic have high expectations for a 2$ MCU.

Bk7231n save state off switch

Why don’t you want to write to flash? If it’s because fear of wearing it out, I think it’s a vastly overstated problem. Here’s a quite from @OttoWinter himself: So as a fundamental thing: Has anyone ever had the memory wear out? I hear a lot of people (IMO incorrectly) fearing about it, but never heard from a user actually experiencing this. There’s also this answer on Stack Overflow,: Anecdotal: I’ve had an ESP32 running for several years, saving to flash every hour, without any problem…

[Karosm]

Yep, I think in 99% of cases default is ok, you don’t even need to think about it.
If you absolutely want to make sure to have the last state saved, set it 0s. It still only writes to flash when state changes.
I see that parameter more useful when you don’t need to save your state and you have states that change continuously and rapidly. In this case you can set it higher.