Closed eugentib closed 5 years ago
I can see a wifi ap called "ESP_A15C16
Tasmota don't provide that name. So, that means that your firmware is corrupt. May be it has rests of other firmware in flash.
Please do a full erase with esptool.py as explained in the wiki and then flash with esptool.py the precompiled bins.
If you need further assistant please find us in the Tasmota Support Chat. Github issues are meant for bug reporting. Help and support is better and faster in the chat. Thanks
I'm having the same issue, I erased many times and flashed again with esptools or platformio, I also tried to change cfg holder without success. The WiFi ap starts with ESP with smart config and it doesn't work, while it is ok with wifi manager where AP Name starts with sonoff. Wifi manager has another issue: if I set the admin password in config after enter the password it redirect me to a blank page so I cannot setup WiFi connection, no problem without setting the admin password.
@ascillato @eugentib I was able to resolve the issue by modifying line 159 #ifdef of support_wifi.ino as follows:
#ifdef USE_SMARTCONFIG
else if (WIFI_SMARTCONFIG == wifi_config_type) {
AddLog_P(LOG_LEVEL_INFO, S_LOG_WIFI, PSTR(D_WCFG_1_SMARTCONFIG " " D_ACTIVE_FOR_3_MINUTES));
WiFi.mode(WIFI_STA);
WiFi.beginSmartConfig();
}
#endif // USE_SMARTCONFIG
As you can see, I just added
WiFi.mode(WIFI_STA);
Good job, thanks!
I thing something is wrong with my_user_config.h because with the latest release version I can't use WiFi Smart Config (I use it without problems on versions 5.x.x)
status 0
:To Reproduce Steps to reproduce the behavior: my_user_config.h
Expected behavior I am unable to set the wifi credentials with 3 android apps that I tried and even that in the serial monitor appears "WIF: SmartConfig active for 3 minutes" I can see a wifi ap called "ESP_A15C16" but with no port open (looks more like WIFI_MANAGER that I can't use because of the TLS)
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)