When booting into AP mode and no config.json is found, and a user typo's the WiFi credentials, how would a user recover? Thinking of a case where the 8266 was configured and sent to the end-user with the expectation of bootstrapping upon first power-up.
Currently, from testing, the unit writes config.json with incorrect data and proceeds into an endless STA_DISCONNECTED state (at least for 743seconds so far). Does this ever time out and revert back to AP mode? How long does it take?
Second, same scenario when no config.json is found, if a user changes the unit name in general.html a reset is performed. The issue is config.json is written out and contains garbage WiFi connection data, so the unit has a name but never comes online to WiFi. What is the design to recover from this case?
When booting into AP mode and no config.json is found, and a user typo's the WiFi credentials, how would a user recover? Thinking of a case where the 8266 was configured and sent to the end-user with the expectation of bootstrapping upon first power-up.
Currently, from testing, the unit writes config.json with incorrect data and proceeds into an endless STA_DISCONNECTED state (at least for 743seconds so far). Does this ever time out and revert back to AP mode? How long does it take?
Second, same scenario when no config.json is found, if a user changes the unit name in general.html a reset is performed. The issue is config.json is written out and contains garbage WiFi connection data, so the unit has a name but never comes online to WiFi. What is the design to recover from this case?