config-nvs

OTA-safe NVS storage retains WiFi, MQTT, and NTP settings across ESP32 firmware updates by using version tracking to detect OTA transitions, preventing data loss and avoiding manual reconfiguration after reboot.

Migrating pool-controller configuration from LittleFS JSON to NVS involves using the ConfigManager API to load existing JSON settings and persist them into ESP32 non-volatile storage, ensuring a single source of truth for WiFi, MQTT, and NTP parameters.

Implementing a factory reset for ESP32 NVS configuration involves invoking the ConfigManager reset workflow, which clears all WiFi, MQTT, NTP, and operational parameters from non-volatile storage and restores default settings safely.

The ConfigManager lifecycle works by calling begin to initialize NVS, load to read WiFi and MQTT settings into memory, save to persist modified values, and reset to clear storage, ensuring resilient configuration management across reboots.

ESP32 pool-controller settings disappear after a reboot or OTA update when not stored in OTA-safe NVS storage; using ConfigManager with explicit key mappings and version tracking ensures configuration persistence and prevents data loss.

You do not need separate storage for WiFi and operational parameters; the central ConfigManager API handles WiFi, MQTT, NTP, and controller settings with a single source of truth in NVS, simplifying configuration management.