Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full reset doesn't work, if there is no config.json #1872

Open
g-regor opened this issue Jan 18, 2024 · 2 comments
Open

Full reset doesn't work, if there is no config.json #1872

g-regor opened this issue Jan 18, 2024 · 2 comments

Comments

@g-regor
Copy link

g-regor commented Jan 18, 2024

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:

  1. Upload firmware (V1.7.0) with TRIGGER_GPIO feature enabled and invalid MQTT_SERVER set.
  2. Setup the gateway through WiFi manager
  3. Wipe gateway's filesystem
  4. Now it fails to connect to MQTT broker, but connects to WiFi
  5. Hold down the TRIGGER_GPIO
  6. 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.

Copy link

This issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Apr 18, 2024
Copy link

github-actions bot commented May 2, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as completed May 2, 2024
@1technophile 1technophile removed the stale label May 2, 2024
@1technophile 1technophile reopened this May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants