Now, let's install the Azure IoT Edge Dev Tool via pip.

Click on the following command to install the IoT Edge Dev Tool.

pip install -U azure-iot-edge-dev-tool

Click Continue after the IoT Edge Dev Tool successfully installs.

Now, we'll create an Azure IoT Edge Solution that has everything you need to get started in your IoT Edge Development, including configuration and a sample module.

Click on the following command to create an Azure IoT Edge Solution:

iotedgedev solution --create iotedge

Click on the following command to navigate to the root of your new solution:

cd iotedge

You will notice that the directory tree you see to the right will refresh and contain the iotedge folder. Feel free to explore the files there to familiarize yourself with the solution files.

Click Continue

The Azure IoT Edge Dev Tool is driven by Environment Variables. The only two variables required to get started are IOTHUB_CONNECTION_STRING and DEVICE_CONNECTION_STRING. When the Edge Dev Tool runs it loads all the variables in the .env file, so we need to place those two variables in that file before we run further commands. The Edge Dev Tool has an azure --setup command to help you retrieve those settings and store them in the solution's .env file.

Click on the following command to start that process:

iotedgedev azure --setup

You will be asked to open a browser and go to https://aka.ms/devicelogin and enter a code. You will then need to login to your Azure account. Complete that process and then come back here.

When you come back to the terminal you will see your Azure subscriptions. You'll select the appropriate subscription, create or select and IoT Hub and then create or select and Edge Device.

After the IoT Hub and Device are selected, the connection strings will be printing in the terminal and it will prompt you to save the connection strings to your .env file. Enter y and then hit click enter to do that.

Then, click the following command to see the .env file with your connection strings.

iotedge/.env

Click Continue after you have verified that the .env file contains your connection strings.

Each module in your IoT Edge solution needs built and packaged up into an image to be pulled from the Azure IoT Edge runtime.

The modules --build command will dotnet restore, build, publish and then docker build, tag and push each module it finds in your solution. In this case, it will find the filtermodule. If you have more modules in the modules folder the IoT Edge Dev Tool will automatically discover them and do the same process for each of them.

The modules --deploy command will take the dynamically generated .config/deployment.json file and deploy it to your edge device.

iotedgedev modules --build --deploy

Click Continue when you see the DEPLOY COMPLETE message.

We now want to setup and start the Edge Runtime so that we can download the images from our container and start sending messages to IoT Hub.

The runtime --setup command will apply the .config/runtime.json file to the runtime. This file has everything you need to start the runtime, including paths to the EdgeAgent image and container registry credentials.

The runtime --start command will start the Azure IoT Edge runtime, which will retrieve the latest configuration that was deployed in the last step and start the process of downloading and running modules.

Click on the following command to setup and start the IoT Edge Runtime.

iotedgedev runtime --setup --start

Click Continue after you see the RUNTIME STARTED message.

We now have messages flowing from the simulated temperature sensor module, to the filter module, to the EdgeHub and then up to IoT Hub. Let's see those messages now:

Click on the following command to view the messages flowing to IoT Hub from our IoT Edge device.

iotedgedev iothub --monitor-events

Please be patient as you wait for messages to appear in the terminal as it takes a few moments for the Edge Runtime to load the modules.

Click Summary after you see the messages printed in the terminal.