ESP8266 Community Forum

- Tue Sep 16, 2014 12:49 pm #666 Not going to be all that helpful if It can not stay connected!

Need to work this one out.

Subscribe to our mailing list to be kept up to date on all developments
of this low cost Serial controlled FCC approved IoT module
complete Arduino library and Web API available soon.

* mail list sub and unsub handled by 3rd party MailChimp.com

- Tue Sep 16, 2014 12:56 pm #667 Well it is kind of solved. There is AT+CIPSTO command that can extend that timeout.
There is just one more thing, it would be great if this module answered to KEEP ALIVE messages when socket connection is established. It seams that it doesn't answer to KEEP ALIVE though. Maybe it was my module that is having that problem (I have the old version with only TX RX GND and VCC pins broken out). Can someone else give it a try?

- Sat Sep 20, 2014 1:42 am #777 Updated the documentation and server source on github. Currently thinking about the hardware and building a website for User and Base registration.

I am wondering if it is possible for these modules to communicate with each other, without connecting any of them to the internet or to a server in local LAN. Something like nRF24L01 work.

- Sat Sep 27, 2014 1:40 am #953

Well it is kind of solved. There is AT+CIPSTO command that can extend that timeout.
There is just one more thing, it would be great if this module answered to KEEP ALIVE messages when socket connection is established. It seams that it doesn't answer to KEEP ALIVE though. Maybe it was my module that is having that problem (I have the old version with only TX RX GND and VCC pins broken out). Can someone else give it a try?

When you say you have only the old version.... what is the difference. I have a unit that does not seem to work properly and I've no way to know if it's old or new.. any info would be helpful.

Peter Scargill - http://tech.scargill.net