ESP8266, sporadically no write access to the file system

Question

I have an ESP8266 project which reads my gas consumption. The hardware and the project run satisfactorily. Sporadically, the ESP8266 can no longer write to its file system and therefore cannot save any data. As soon as I upload the complete data and the sketch to the device again, it works for a few months. After that, the mistake occurred again and again. What could that be?

The ESP8266 then has an "Exception" error. Unfortunately, I have not yet been able to find the reason for the error, why it always happens.

Does anyone have a tip on how I can isolate the problem?

https://github.com/HomeAutoUser/ESP-Gaszaehler-GZ16/tree/pre-release_v1.91

• Juraj: what is what you write? configuration or log files? if you upload the data does it contain the files with logged data? isn't the file system simply full?
• dandavis: does github.com/me-no-dev/EspExceptionDecoder give you any more info about what's exploding? Does rebooting once a day fix it?
• user47164: The link is broken, I believe. It may also be that the module's flash is wearing out, although I'm not sure how reuploading would fix that, if that is the case.
• user11528497: The link is now revised.

Answer 1

I have faced the same issue with my water leak detector, based on esp8266. It was caused by memory leak in the ESP binaries, so, I've updated it to ver 2.6.3

So, you can try to log (print to serial) free memory amount:

extern "C" 
{
 #include "user_interface.h"
}
uint32_t free = system_get_free_heap_size();

• user11528497: Thanks for the answer. I now have the problem that it can be compiled with the Core 2.5.2 but not with the Core 2.6.3. I added the code above. Suddenly a variable should not be declared. exit status 1 StaticRequestHandler has not been declared
• user11528497: The line 'extern "C" { #include "user_interface.h" }' is in code already in.
• Juraj: the memory leak was with WiFiClient in 2.4.1 2 years ago
• gbg: @Juraj, okay, so, any other ideas?