mirror of
https://github.com/esphome/esphome.git
synced 2026-09-15 09:08:41 +00:00
J. Nick Koston
d30f82784c
Mat931 verified empirically that ``nvs_flash_init()`` after ``nvs_flash_deinit()`` does not revive NVS handles already held by other components: writes still fail with ESP_ERR_NVS_INVALID_HANDLE. The guard therefore only created the appearance of a recovery path. Remove it and document the actual contract: from nvs_flash_deinit() onward, components that hold open NVS handles will fail until the device is rebooted. The success path reboots immediately, so it is unaffected; the failure path now tells the user clearly to reboot and retry, rather than implying retry-without-reboot will work. Also soften the "permanently brick" wording in the pre-write log warning -- a bad partition-table OTA leaves a device that needs a serial flash to recover, not a permanently-dead one.
