You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Upload firmware (V1.7.0) with TRIGGER_GPIO feature enabled and invalid MQTT_SERVER set.
Setup the gateway through WiFi manager
Wipe gateway's filesystem
Now it fails to connect to MQTT broker, but connects to WiFi
Hold down the TRIGGER_GPIO
WiFi manager's AP is never started
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: