Skip to main content

WeMos D1 ESP8266 Web Controlled Switch

Last year I made Room automation with Raspberry Pi and few Arduinos for switching lights and air conditioner on and off using my phone. It required lots of components for accomplishing a simple task. The reason was that Arduino itself cannot connect to wifi and NRF24L01+ module doesn’t support TCP/IP protocol, so I needed Raspberry Pi for wifi connection. Also using new Raspberry Pi for each light switch is just too expensive. This time I used WeMos ESP8266.

ESP866 is an inexpensive Wifi Module for Arduino that supports 802.11 b/g/n protocols and it can also run Arduino code. There are multiple versions of this SOC. Some require serial to USB adapter for programming and some have micro USB port. They also vary by amount of GPIO ports and memory they have.

List of parts that I also used for this project:

  • WeMos D1 ESP8266
  • Relay module
  • MB102 Breadboard Power Supply Module
  • Old notebooks power adapter

For assembly I connected notebook’s PSU to MB102 PSU module, MB102 to ESP8266 with USB cable and GPIO ports 0, 2 and ground on ESP8266 to Relay module.

ESP8266  WeMos
ESP8266 WeMos

I modified ESP8266 library example code and uploaded it on the WeMos ESP8266:

Module automatically connects to wifi when powered and receives an IP address from router ( for example). It’s IP may change every time module disconnects from wifi, so I assigned it static IP address on my router.

You can switch GPIO on by sending HTML request to “http://[ESP8266s ip address]/gpio/0” and to turn it off “~/gpio/1”. This is done simply by visiting url in a web browser.
Disadvantage of the code from libraries example is that you can’t tell whether GPIO is on or off. I modified it so that html response includes info about its status when you visit ~/status.

Turning the air conditioner on by typing into a browser and making sure that it’s on or off by visiting it’s not very practical, so I made a simple web interface and added it to my homes dashboard webpage.

It displays a button with text “Turn on” or “Turn off” depending on the GPIOs current status. When you click it, it sends a html request to the module to change its GPIO state.
You can use as many ESP8266 modules as you want and manage them from a centralized web application.

Everything connected
Everything connected

Edit: Someone on Reddit requested code for managing multiple ESP8266s. So here is the code. To add new module, just add its IP address and name in the array.

Here is a video demonstration of last years system. Front-end webapp is the same and it functions the same.

6 thoughts to “WeMos D1 ESP8266 Web Controlled Switch”

  1. The examples you provided here are great. I was looking for a way to control a boiler and your example works flawlessly. Is there a way to get the temperature to show on the page also. I am using ds18b20. Any help would be greatly appreciated. In any case thanks for the examples and keep up the good work

    1. There probably is a way. You would need to connect the temperature sensor to ESP8266 and make a program using the same code as for a normal switch, but also include ds18b20s library and code for reading and formatting temperature and add the variable that reads temperature in the html response. Then, using php parse the response in a way to get the temperature in a var. I will try this in the following days and post the source here. :)

  2. I found this post to be really enlightening. I am thinking of starting a business catering the IoT sector. Is there a better or cheaper way to connect existing switchboards to the wi fi? I am trying to find a compact module that can be encased and fitted behind the switch boards. I am not familiar with Arduino and stuff, so any kind of help will be really appreciated. Thanks in advance :)

  3. Great project. The author is honored and respected. How can you add to code one-button (momentary). When you first make a start, turn on the next time you turn off. With the feedback state in the web.

Leave a Reply

Your email address will not be published. Required fields are marked *