One of the silver linings of coronavirus quarantine has been time to tinker with development boards long ago acquired yet rarely tinkered with. Such is NodeMCU.
I am interested in self-contained devices that rely on little support infrastructure yet offer lots of functionality. So one project I have tackled was the ability to remotely and control the NodeMCU from a web browser.
You can grab the code here: https://github.com/GreenShoeGarage/NodeMCU-Remote-Control

Fire up PuTTY to find the NodeMCU’s IP address:

After getting the IP address from the serial terminal, enter into a browser and viola:

To satiate the curiosity of what is actually getting passed around the network, fire up Wireshark and follow the http traffic:

