Is it possible that the library or some part of it could have been initialised twice somehow? That could explain things being messed up.
An HTTP bug is unlikely given it works fine in for all the other connection modes and devices. It's possible, but I'd try and rule out some other things first :)
Also, did you try just calling wifi.connectandwifi.startAP? The way the EspruinoWiFi library works, the wifiMode variable should be ORed such that if you call both functions then Espruino is put into CWMODE 3 - the softap/station mode you're after?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Is it possible that the library or some part of it could have been initialised twice somehow? That could explain things being messed up.
An HTTP bug is unlikely given it works fine in for all the other connection modes and devices. It's possible, but I'd try and rule out some other things first :)
Also, did you try just calling
wifi.connect
andwifi.startAP
? The way the EspruinoWiFi library works, thewifiMode
variable should be ORed such that if you call both functions then Espruino is put into CWMODE 3 - the softap/station mode you're after?