With latest lwip 2 from esp github repo, we we call jw.disconnect() it is not automatically connecting back to the network (Or should I say, pretending that it is not connecting but actually still connected).
This example from Serial dump of Espurna after i send the command "wifi.reset" .
[WIFI] Disconnected
[WIFI] Connecting to BSSID: FE:3F:60:14:FF:3F CH: 00, RSSI: 0, SEC: OPEN, SSID: WhoMe...
[WIFI] Could not connect to WhoMe...
It will keep printing message - 'Connecting to BSSID...' and then 'Could not connect to MY_WIFI_NAME'
But i am also running a webserver on the esp8266 and surprisingly i am able to connect to the IP of the device when it was connected to my wifi network even when its showing trying to connect message in terminal..
This is happening with latest lwip version 2.
With latest lwip 2 from esp github repo, we we call jw.disconnect() it is not automatically connecting back to the network (Or should I say, pretending that it is not connecting but actually still connected).
This example from Serial dump of Espurna after i send the command "wifi.reset" .
It will keep printing message - 'Connecting to BSSID...' and then 'Could not connect to MY_WIFI_NAME'
But i am also running a webserver on the esp8266 and surprisingly i am able to connect to the IP of the device when it was connected to my wifi network even when its showing trying to connect message in terminal..
This is happening with latest lwip version 2.