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
![](https://i1.wp.com/gearsofresistance.com/wp-content/uploads/2020/05/editor-1.png?fit=640%2C432&ssl=1)
Fire up PuTTY to find the NodeMCU’s IP address:
![](https://i0.wp.com/gearsofresistance.com/wp-content/uploads/2020/05/putty.png?resize=640%2C389&ssl=1)
After getting the IP address from the serial terminal, enter into a browser and viola:
![](https://i0.wp.com/gearsofresistance.com/wp-content/uploads/2020/05/webbrowser.png?resize=602%2C556&ssl=1)
To satiate the curiosity of what is actually getting passed around the network, fire up Wireshark and follow the http traffic:
![](https://i1.wp.com/gearsofresistance.com/wp-content/uploads/2020/05/wireshark.png?fit=640%2C343&ssl=1)
![](https://i2.wp.com/gearsofresistance.com/wp-content/uploads/2020/05/Wiresharkpcap.png?fit=640%2C518&ssl=1)