ESP8266 as an IOT style device

Hi Theresa,

As I understand (I may have misunderstood) after the initial configuration (using the ESP8266 as a WiFi access point with web server, and a local handset connecting as a WiFi client to it), any subsequent commands are to be sent from anywhere in the world, from a mobile app, through a server in the cloud, i.e.   handset->cloud service->ESP8266.

In that case, there's no way to have almost zero-sec latency, because the path is outside of your control. There are network delays in each leg, as well as server delays in the cloud (for the packet to get inside the OS and into the app, as well as the time for the app to get CPU cycles or be started up (depending on the cloud service you're using) plus any circuit connection set-up delays if you're using mobile for any leg (applies to other mediums too, not just mobile). Keeping the TCP connection open as you're suggesting I think, could be an option, but it still won't be anywhere near real-time if you're controlling moving machinery. The modern way to resolve this is to have local intelligence so that the ESP8266 (or any other device) can autonomously decide to take over and make a decision to stop the actuator.

That may require a device with higher compute performance and different or more sensors. Along with all of that comes other issues to be considered, e.g. reliability, redundancy, etc.

Suggest trying PubNub, if latency is important. There's an Arduino library out there.

Alternatively, look at Google's Firebase. Good for mobile app linkage. Quite a few Arduino libraries for Firebase out there too.

Sort of, the idea is that to start the "IOT" device is in host mode, and is used to connect and then the device switches to Client mode connecting to the house wifi and talking to the master server on the interwebs

Hi Theresa,

I see; yes, that's as I expected. The information above applies to this scenario. As BigG suggests, there's some frameworks you can run on the local hardware (e.g. ESP8266) to provide you with local control capability. Similarly, there's AWS GreenGrass, but it needs a more powerful device running Linux.

When I need a low latency, "virtual wire" as in the case of replacing an RC transmitter, I go with the Xbee platform.

But, for IoT where I just need a couple of pins per device such as for Home Automation, I go ESP8266 as you are thinking.  It definitely has latency, but under a second typically.  It feels darn near immediate when just sending a web socket command on the LAN.

Here you will find code for the ESP8266 to catch Web Socket commands with the IoT platforms IFTTT, Push Bullet, and Alexa:

Home Automation Mojo You Must Know Part 2: Notification

Here you will find code for handling direct Web Socket communication back and forth across different devices:

Episode 376: 4D Gaming with the MATRIX Creator (overview video)

4D IoT Game Engine Blog (circuits and code blog)

These blogs may seem a little daunting, but they cut through about 40+ hours of research to get working socket code for the ESP8266.  The code and circuits are good to have in Maker's IoT tool kit.

See ya',

Sean

theresajayne Cannot give specifics, but I like this https://www.instructables.com/id/GETTING-STARTED-WITH-IoT-With-ESP8266-MicroControl/  which can give you the overview perceptive. Hope that helps.