Strange - so I can get it to stop responding, but it does seem to pull itself back together after a while and respond.
Looks like it starts off with it responding busy to CIPSEND. Ideally I think Espruino should wait until there's a '>' but it doesn't bother right now. That doesn't seem to be the issue though as it's even responding 'busy' to even CIPCLOSE...
I quickly googled ESP8266 "busy inet" and there some posts that imply that maybe Espruino should wait >1 sec between sending AT+CIPSEND commands. I'll have to look into it a bit further but it could be that this version of the ESP8266 firmware is a bit flaky as a server.
Client seems rock solid though - the weather thing is still running fine.
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.
Strange - so I can get it to stop responding, but it does seem to pull itself back together after a while and respond.
Looks like it starts off with it responding
busy
toCIPSEND
. Ideally I think Espruino should wait until there's a '>' but it doesn't bother right now. That doesn't seem to be the issue though as it's even responding 'busy' to even CIPCLOSE...I quickly googled
ESP8266 "busy inet"
and there some posts that imply that maybe Espruino should wait >1 sec between sendingAT+CIPSEND
commands. I'll have to look into it a bit further but it could be that this version of the ESP8266 firmware is a bit flaky as a server.Client seems rock solid though - the weather thing is still running fine.