Azure IoT ESP Samples
This version of PnP sample is now deprecated and will be updated son.
To see the latest PnP (Plug and Play) convention visit the PnP documentation
In this repository, you will find:
- Azure samples for Espressif boards located in the
- Azure IoT SDK component for the ESP stable version located in the
componentsfolder. These components can be used in any ESP project which desires to connect to Azure IoT. Two versions of the component are provided within this repository:
- Azure IoT SDK without PnP
- Azure IoT SDK with PnP (preview)
If you are a beginner with Azure IoT or Espressif boards, please look at the Key Concepts section below.
In addition to the current ESP32 and ESP8266 hardware offerings, Espressif now offers the ESP32 Azure IoT Board, a development board that includes key sensors, OLED screen, and support for Wi-Fi & Bluetooth protocols. More information about this Azure certified board is available in the Azure IoT catalog.
For any questions or suggestions, please open an issue and tag @ericmitt, @drajput, @tawalke
Table of Contents
- Prerequisites - Required items to run samples
- Installing Toolchain & Development Framework - Dev environment setup
- Sample Setup - How to setup and run samples
- Key Concepts - Understand Azure IoT & ESP
- Contributing - How to contribute to this repository
Samples available in this repository
|azure-esp-starter||Send telemetry data from the ESP32 Azure device to Azure IoT Hub|
|azure-esp-starter-pnp||Send telemetry data from ESP32 Azure device to Azure IoT Hub with Azure IoT Plug and Play|
|azure-esp8266-posturesensor||Create a Posture Sensor ESP8266 device and send telemetry data and commands to/from to Azure IoT Hub (Sample graciously provided from our Azure IoT Intern, Sarah Rashid,@sarahrashid)|
The projects in the samples folder follow the folder structure specified by Espressif for ESP-IDF projects. See more information about ESP-IDF and the ESP-IDF build system in the Key Concepts section.
- Azure subscription: You will need an active Azure subscription. If you do not have one, you can register via one of these two methods:
- Azure IoT Hub: An active Azure IoT Hub
- ESP32/ESP8266 device: An Espressif development board which is registered in Azure IoT Hub as a device.
If you're not familiar with Azure IoT or need help setting up an Azure IoT Hub, please see Key Concepts section.
Installing Toolchain and Development Framework
To build and deploy a project on your ESP Board, you need to complete the following steps:
- Install the ESP toolchain
- Install the ESP development framework
- Setup PATH for ESP environment
Please follow the steps corresponding to your operating system below to ensure your development environment is ready for ESP32 or ESP8266 development.
Using Windows Subsystem Linux (WSL):
You can install the ESP32 toolchain and ESP-IDF on your windows machine using WSL. Start Windows Subsystem for Linux by typing
WSL in your start menu and running this setup script.
When choosing to install the ESP8266 toolchain and SDK using WSL, you should start the Windows Subsystem for Linux by typing
WSL and run this setup script instead.
For instructions on running the setup scripts, please review the details provided here. This is the recommended approach for novice ESP32 and ESP8266 developers using these samples.
For more information on setting up WSL on Windows 10 see how to setup WSL on Windows 10.
Using MSYS2 environment on Windows:
You can install the ESP32 toolchain on your windows machine using the MSYS2 environments aka MinGW on Windows. To install, follow the steps outlined in Espressif documentation for setup on Windows found here. The quick setup option provides a pre-prepared environment with all-in-one toolchain and MSYS2. There is also information around steps to update an existing Windows environment.
After setup of your environment and toolchain, you would setup ESP-IDF by following steps outlined in the Espressif documentation. Links to get the toolchain and setup path are provided below:
To install the ESP8266 toolchain and RTOS SDK development environment on Windows using MSYS2 environment, please follow these steps:
To install the stable version of the ESP32 toolchain and ESP-IDF development environment on Linux, please follow the setup steps outlined in the Espressif documentation. The links for these steps are provided below.
To install the ESP8266 toolchain and RTOS SDK development environment on Linux, please follow these steps:
To install the stable version of the ESP32 toolchain and ESP-IDF development environment on macOS, please follow the setup steps outlined in the Espressif documentation. The links for these steps are provided below.
To install the ESP8266 toolchain and RTOS SDK development environment on macOS, please follow these steps:
Setup the samples
Before running any of the samples within this repository, please ensure that you have an active Azure IoT Hub and setup the ESP-IDF development environment. Please see Prerequisites section for more information.
Clone this repository in your working directory.
For example, if you use WSL:
- Launch WSL (type WSL in the start menu).
- Once started, navigate to the mounted partition (this way you can see all the files with the Windows file explorer):
cd /mnt/c(or any other directory under C)
- Then clone this repository:
git clone https://github.com/Azure-Samples/ESP-Samples.git
Copy the Azure component esp-azure or esp-azure-pnp into the components folder of the sample you want to build.
Navigate to the project folder (within the repository's samples/ folder) for the sample you want to use and follow the instructions in that project's readme file.
Tip: For using Azure IoT SDK in your existing projects, just copy/clone the esp-azure or esp-azure-pnp folder in your components folder. That's it. You're ready to build!
If you are new to Azure IoT, it is good to understand the services available for working with hardware like Espressif and Azure IoT. Some of the key services for Azure IoT are:
The Azure IoT service used in for the samples in repository is Azure IoT Hub. To learn how to setup an Azure IoT Hub and add devices, please follow the steps outlined in the Azure IoT documentation for creating an Azure IoT Hub. Links are provided below:
To add your device, go to "IoT devices" within your IoT Hub in the Azure portal. Click New and fill the form this way:
For more information on working with devices with Azure IoT, check out the information noted in the documentation here.
There are various development frameworks available for working with ESP devices. The samples in this repository use the Espressif IoT Development Framework, otherwise known as ESP-IDF.
In using the ESP-IDF framework, it is recommended to utilize the ESP-IDF build system folder structure which brings a notion of “components”. Components to be used in your project, like Azure IoT, should be placed within the appropriate project folder with Makefile and/or CMakelists files at the root of each component's folder. Project code is then typically placed in the main folder. ESP-IDF projects have the components used and the project code built and statically linked at the same time. Learn more about the ESP-IDF build system and starting ESP projects from scratch in the Espressif documentation for the ESP-IDF build system.
To use Azure IoT in your own custom project, you can use the empty project template provided by Espressif. Once your folder structure is set up, copy the desired Azure IoT component into your components folder. The components provided in this repo are: azure-esp-sdk and esp-azure-pnp (Plug and Play)
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.