Add reset loop detection, skip loading setting from EEPROM, set brightness low, etc.

[jasoncoon]

No description provided.

[qawsed55]

Jason, I recomend you to add so SETUP
WiFi.persistent(false);
This tell ESP to skip writing WiFi settings to last three EEPROM sectors if they was not changed. EEPROM has limited writing cycles, and this would bring some more life )

[henrygab]

First, is this still considered an issue? The original issue was opened ~5 years ago. Thus, I'd recommend closing this issue as stale. I may do this if not confirmed as a current issue before 2022-03-14.

Questions if keeping this issue open

If keeping it, some clarity would be helpful. If I understand this issue correctly, it sounds like this is a request for the following:

1. Add a user-settable option (and maybe sub-options) to enable a "Safe Mode" boot.
2. At boot, detect if the ESP was reset by watchdog and/or detected brownout
3. If watchdog and/or detected brownout causing this boot, enter "Safe Mode" rather than normal booting.

The goal of "Safe Mode" is to allow re-configuration via WiFi, while avoiding likely causes of failure. Therefore, Safe Mode would be defined as (or have options for):

• WiFi:
  • Enabled (default ... but this does use settings stored in EEPROM)
  • WiFi AP mode (does wifimanager library have any option to avoid reading settings?)
• GPIO:
  • All GPIO set to floating / tri-state (default ... prevents shorts)
  • GPIO set normally (??? should this even be an option for safe mode ???)
• LED Limits, if GPIO allowed to be set normally:
  • Limit to only 3 LEDs being allowed to be any color other than black (off)
  • (If the three LEDs are enabled, allows simple feedback that it's in safe mode)
  • Limit brightness of those 3 LEDs
• EEPROM settings:
  • Do not use any current EEPROM settings
  • Erase any current EEPROM settings
  • Note that WiFi is handled separately...