External Components

Now let’s try the same, but not with the build-in LED – let’s connect an external LED and try to use that. The connection should look like this:


Note how one leg of the LED is a little bit longer, and the other had a flattening on the plastic of the LED next to it. The long leg should go to the plus, and the short one to the minus. We are connecting the LED in opposite way than the internal one is connected – between the pin and gnd. That means that it will shine when the pin is high, and be dark when it’s low.

Also note how we added a resistor in there. That is necessary to limit the amount of current that is going to flow through the LED, and with it, its brightness. Without the resistor, the LED would shine very bright for a short moment, until either it, or the board, would overheat and break. We don’t want that.

Now, let’s try the code:

from machine import Pin
import time

led = Pin(14, Pin.OUT)
for i in range(10):

Again, you should see the LED blink 10 times, half a second for each blink.

This time we used time.sleep_ms() instead of time.sleep() – it does the same thing, but takes the number of milliseconds instead od seconds as the parameter, so we don’t have to use fractions.

Pulse Width Modulation

Wouldn’t it be neat if instead of blinking, the LED slowly became brighter and then fade out again? Can we do this somehow?

The brightness of the LED depends on the voltage being supplied to it. Unfortunately, our GPIO pins only have a simple switch functionality – we can turn them on or off, but we can’t fluently change the voltage (there are pins that could do that, called DAC, for “digital to analog converter”, but our board doesn’t have those). But there is another way. Remember when we first tried to blink the LED without any delay, and it happened too fast to see?

Turns out we can blink the LED very fast, and by varying the time it is on and off change how bright it seems to be to the human eye. The longer it is on and the shorter it is off, the brighter it will seem.

Now, we could do that with a simple loop and some very small delays, but it would keep our board busy and prevent it from doing anything else, and also wouldn’t be very accurate or terribly fast. But the ESP8266 has special hardware dedicated just for blinking, and we can use that! This hardware is called PWM (for Pulse Width Modulation), and you can use it like this:

from machine import Pin, PWM
import time

pwm = PWM(Pin(2))

If you run this, you should see the blue led on gpio2 change brightness. The possible range is from 1023 (100% duty cycle, the LED is off) to 0 (0% duty cycle, the LED is on full brightness). Why is 0 full brightness? Remember, that the LED on the gpio2 is reversed – it shines when the pin is off, and the duty cycle tells how much the pin is on.

You can also change the frequency of the blinking. Try this:


That should blink the LED with frequency of 1Hz, so once per second – we are basically back to our initial program, except the LED blinks “in the background” controlled by dedicated hardware, while your program can do other things!


We don’t have a button in our kit, but we can simulate one by just using two wires, one with a male plug, and one with female. Connect them like so:


Now we will write some code that will switch the LED on and off each time the wires are put together:

from machine import Pin
led = Pin(2, Pin.OUT)
button = Pin(14, Pin.IN, Pin.PULL_UP)
while True:
    if not button.value():
        led.value(not led.value())
        while not button.value():

We have used Pin.IN because we want to use gpio14 as an input pin, on which we will read the voltage. We also added Pin.PULL_UP – that means that there is a special internal resistor enabled between that pin and the 3V3 pins. The effect of this is that when the pin is not connected to anything (we say it’s “floating”), it will return 1. If we didn’t do that, it would return random values depending on its environment. Of course when you connect the pin to GND, it will return 0.

However, when you try this example, you will see that it doesn’t work reliably. The LED will blink, and sometimes stay off, sometimes switch on again, randomly. Why is that?

That’s because your hands are shaking. A mechanical switch has a spring inside that would shake and vibrate too. That means that each time you touch the wires (or close the switch), there are in reality multiple signals sent, not just one. This is called “bouncing”, because the signal bounces several times.

To fix this issue, we will do something that is called “de-bouncing”. There are several ways to do it, but the easiest is to just wait some time for the signal to stabilize:

import time
from machine import Pin
led = Pin(2, Pin.OUT)
button = Pin(14, Pin.IN, Pin.PULL_UP)
while True:
    if not button.value():
        led.value(not led.value())
        while not button.value():

Here we wait 3/10 of a second – too fast for a human to notice, but enough for the signal to stabilize. The exact time for this is usually determined experimentally, or by measuring the signal from the switch and analyzing it.


Time to actually physically move something. If you plan on building a robot, there are three main ways of moving things from the microcontroller:

  • a servomechanism (servo for short),
  • an H-bridge and a DC motor,
  • a stepper or brushless motor with a driver.

We are going to focus on the servo first, because I think this is the easiest and cheapest way. We are going to use a cheap “hobby” servo, the kind that is used in toys – it’s not particularly strong, but it’s enough for most use cases.


Don’t try to force the movement of the servo arms with your hand, you are risking breaking the delicate plastic gears inside.

A hobby servo has three wires: brown or black gnd, red or orange vcc, and white or yellow signal. The gnd should of course be connected to the gnd of our board. The vcc is the power source for the servo, and we are going to connect it to the vin pin of our board – this way it is connected directly to the USB port, and not powered through the board.



Servos and motors usually require a lot of current, more then your board can supply, and often even more than than you can get from USB. Don’t connect them to the 3v3 pins of your board, and if you need two or more, power them from a battery (preferably rechargeable).

The third wire, signal tells the servo what position it should move to, using a 50Hz PWM signal. The center is at around 77, and the exact range varies with the servo model, but should be somewhere between 30 and 122, which corresponds to about 180° of movement. Note that if you send the servo a signal that is outside of the range, it will still obediently try to move there – hitting a mechanical stop and buzzing loudly. If you leave it like this for longer, you can damage your servo, your board or your battery, so please be careful.

So now we are ready to try and move it to the center position:

from machine import Pin, PWM
servo = PWM(Pin(14), freq=50, duty=77)

Then we can see where the limits of its movement are:


There also exist “continuous rotation” servos, which don’t move to the specified position, but instead rotate with specified speed. Those are suitable for building simple wheeled robots. It’s possible to modify a normal servo into a continuous rotation servo.


When I wrote that PWM has a frequency, did you immediately think about sound? Yes, electric signals can be similar to sound, and we can turn them into sound by using speakers. Or small piezoelectric beepers, like in our case.


The piezoelectric speaker doesn’t use any external source of power – it will be powered directly from the GPIO pin – that’s why it can be pretty quiet. Still, let’s try it:

from machine import Pin, PWM
import time

beeper = PWM(Pin(14), freq=440, duty=512)

We can even play melodies! For instance, here’s the musical scale:

from machine import Pin, PWM
import time
tempo = 5
tones = {
    'c': 262,
    'd': 294,
    'e': 330,
    'f': 349,
    'g': 392,
    'a': 440,
    'b': 494,
    'C': 523,
    ' ': 0,
beeper = PWM(Pin(14, Pin.OUT), freq=440, duty=512)
melody = 'cdefgabC'
rhythm = [8, 8, 8, 8, 8, 8, 8, 8]

for tone, length in zip(melody, rhythm):

Unfortunately, the maximum frequency of PWM is currently 1000Hz, so you can’t play any notes higher than that.

It’s possible to make the sounds louder by using a better speaker and possibly an audio amplifier.


The ESP8266 has wireless networking support. It can act as a WiFi access point to which you can connect, and it can also connect to the Internet.

To configure it as an access point, run code like this (use your own name and password):

import network
ap = network.WLAN(network.AP_IF)
ap.config(essid="network-name", authmode=network.AUTH_WPA_WPA2_PSK, password="abcdabcdabcd")

To scan for available networks (and also get additional information about their signal strength and details), use:

import network
sta = network.WLAN(network.STA_IF)

To connect to an existing network, use:

import network
sta = network.WLAN(network.STA_IF)
sta.connect("network-name", "password")

Once the board connects to a network, it will remember it and reconnect every time. To get details about connection, use:



The command console in which you are typing all the code is called “REPL” – an acronym of “read-evaluate-print-loop”. It works over a serial connection over USB. However, once you have your board connected to network, you can use the command console in your browser, over network. That is called WebREPL.

First, you will need to download the web page for the WebREPL to your computer. Get the file from and unpack it somewhere on your computer, then click on the webrepl.html file to open it in the browser.

In order to connect to your board, you have to know its address. If the board works in accesspoint mode, it uses the default address. If it’s connected to WiFi, you can check it with this code:

import network
sta = network.WLAN(network.STA_IF)

You will see something like XXX.XXX.XXX.XXX – that’s the IP address. Enter it in the WebREPL’s address box at the top like this ws://XXX.XXX.XXX.XXX:8266/.

To connect to your board, you first have to start the server on it. You do it with this code:

import webrepl

Now you can go back to the browser and click “connect”. On the first connection, you will be asked to setup a password – later you will use that password to connect to your board.


Writing in the console is all fine for experimenting, but when you actually build something, you want the code to stay on the board, so that you don’t have to connect to it and type the code every time. For that purpose, there is a file storage on your board, where you can put your code and store data.

You can see the list of files in that storage with this code:

import os

You should see something like [''] – that’s a list with just one file name in it. and later are two special files that are executed when the board starts. is for configuration, and you can put your own code in

You can create, write to and read from files like you would with normal Python:

with open("myfile.txt", "w") as f:
    f.write("Hello world!")
with open("myfile.txt", "r") as f:

Please note that since the board doesn’t have much memory, you can put large files on it.

Uploading Files

You can use the WebREPL to upload files to the board from your computer. To do that, you need to open a terminal in the directory where you unpacked the WebREPL files, and run the command:


Where is the file you want to send, and XXX.XXX.XXX.XXX is the address of your board.


You have to have Python installed on your computer for this to work.

HTTP Requests

Once you are connected to network, you can talk to servers and interact with web services. The easiest way is to just do a HTTP request – what your web browser does to get the content of web pages:

import urequests
r = urequests.get("").json()

You can use that to get information from websites, such as weather forecasts:

import json
import urequests
r = urequests.get("").json()
print(r["main"]["temp"] - 273.15)

It’s also possible to make more advanced requests, adding special headers to them, changing the HTTP method and so on. However, keep in mind that our board has very little memory for storing the answer, and you can easily get a MemoryError.