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
If AP_MODE is set to AP_MODE_OFF then after dumping the code into an ESP Which had previous code given in examples of ESP8266WiFi. The Hotspot will appear with that older name. So i tried writing in the end of function - JustWifi::setSoftAP()
#!c++
WiFi.softAP(_softap.ssid, _softap.pass);
It gave expected result.
And also sometimes by default ESP's wifi mode is set to WIFI_AP, so in espurna framework if no ssid is present in settings, and AP_MODE is set to AP_MODE_ALONE then ESP will by default go into AP_MODE and justwifi will not send any message like - _doCallback(MESSAGE_ACCESSPOINT_CREATING);
So i think this library should set a default mode of ESP as well in the beginning itself. This will give a more predictive result to users.
The text was updated successfully, but these errors were encountered:
Originally reported by: Arihant Daga (Bitbucket: arihantdaga, GitHub: arihantdaga)
I am refering to this code in espurna framework.
jw.setSoftAP(getSetting("hostname", HOSTNAME).c_str(), NULL);
If AP_MODE is set to AP_MODE_OFF then after dumping the code into an ESP Which had previous code given in examples of ESP8266WiFi. The Hotspot will appear with that older name. So i tried writing in the end of function - JustWifi::setSoftAP()
It gave expected result.
And also sometimes by default ESP's wifi mode is set to WIFI_AP, so in espurna framework if no ssid is present in settings, and AP_MODE is set to AP_MODE_ALONE then ESP will by default go into AP_MODE and justwifi will not send any message like - _doCallback(MESSAGE_ACCESSPOINT_CREATING);
So i think this library should set a default mode of ESP as well in the beginning itself. This will give a more predictive result to users.
The text was updated successfully, but these errors were encountered: