Closed g-regor closed 3 months ago
This issue is stale because it has been open for 90 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
This issue is stale because it has been open for 90 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Holding down the
TRIGGER_GPIO
button down, doesn't erase the config (WiFi credentials and the filesystem) and then run the WiFi manager, if config.json doesn't exits. Since the WiFi credentials are still present, WiFi manager doesn't run and is impossible to configure the gateway which would create config.json.Steps to reproduce the behavior:
TRIGGER_GPIO
feature enabled and invalidMQTT_SERVER
set.TRIGGER_GPIO
WiFi credentials should be erased, even if config.json doesn't exist.
Additional context I uploaded newer firmware on a NodeMCU-32s module, that was previously running an older version (v0.9.6), so it already had WiFi credentials stored, but config.json wasn't present (new partitioning probably wiped it).
The same problem probably shows up, if you flash it on a board that was previously used for a different project and still has valid WiFi credentials.