In this PaaS demo solution you will setup and connect an Azure IoT DevKit device to the Azure IoT Hub and view sensor readings in a custom web application. The purpose of the demo is to showcase how the Azure IoT Hub is able to process messages in real-time from tangible devices. The demo also covers communicating to the device via Direct Methods and integrating to 3rd party API’s.
This repository contains a step-by-step guide on how to deploy your own instance of the demo.
The source code in this repository contains the following:
- React Frontend Web Application
- .NET WebApi
- C++ Arduino Project
This tutorial will focus on setting up the required Azure services and consuming them within each of the applications to create an e2e solution that is focussed around the Azure IoT Hub. The below image outlines the high-level architecture of the solution.
- Windows 10.
- MXChip IoT DevKit AZ3166 (Link).
- Visual Studio 2017 (Community/Professional/Enterprise) or later (Link).
- Visual Studio Code (If you don't have this already, you will install it as part of the
Install IoT DevKit Environment
step, later in the guide). - Azure subscription (Link).
- Twitter account (Link).
- Yarn Package Manager - requires node.js (Link).
All additional software that is required will be installed via the Install IoT DevKit Environment step later in the guide.
If you have git installed, you can run the following command: git clone https://github.com/Microsoft/MXDial-IoT-Sample.git
Alternatively, you can download the material directly: Download Material
IMPORTANT: Only complete the following two sections!! DO NOT complete the "Build your first project" section!
-
Install Development Environment (NOTE: In step 1 - Ensure to use the following Windows Installer)
NOTE: If you would like to setup the Azure resouces (next 3 steps) via ARM template, it is located at
./resources/mx-demo.json
.
NOTE: Throughout this setup you will be asked to add
<your intials>
as a way of uniquely identifying the resource you are creating. In the unlikely event the resource name has been taken, just add another random letter until it becomes unique.
The Azure App Service is an integrated offering for building and hosting web apps.
- From the Azure Portal, go to the Create a resource option.
- Search for
Web App
. - Select the first result and click the Create button.
- Provide the required information:
- App name:
mxchip-<your initials>
. - Create a new resource group with the name:
mxchip-demo-<your initials>
. - OS: Windows.
- App name:
- Click on App service plan/Location.
- Click Create New.
- Provide the required information:
- App Service plan name:
mxchip-demo-<your initials>
. - Location:
West US
. - Pricing Tier: S1 Standard.
- App Service plan name:
- Click OK to save the new App service plan.
- Click Create to deploy the service. This step might take a few moments.
- From the Azure Portal, go to the Create a resource option.
- Search for
IoT Hub
. - Select the first result and click the Create button.
- Provide the required information:
- Subscription: select your subscription.
- Select the resource group previously created:
mxchip-demo-<your initials>
. - Region:
West US
. - Name:
mxhub-<yourinitials>
.
- Click on Next: Size and scale.
- Pricing and scale tier: select F1(Free tier) if available, otherwise select S1(Standard).
- Click on Review + create.
- Review your IoT hub information, then click Create. This process might take a few moments.
To add a consumer group to your IoT hub, follow these steps:
- In the Azure portal, go to All Resources in the left pane and search for your IoT Hub:
mxhub-<yourinitials>
. - Click on the resource to open it.
- In the left pane, click Endpoints, select Events on the middle pane, look for the Consumer groups on the right pane.
- Add a new consumer group with the name
mxchip
and then click Save.
- Open your IoT Hub resource in Azure.
- In the left pane, click Shared access policies and select iothubowner on the middle pane.
- Copy the value of Connection string—primary key into Notepad as you will need it later.
NOTE: Twitter have recently updated how they manage developer accounts and they are need to be approved first. It is important to note that this can take some time and you will not be able to use Twitter integration until this process is completed. As a workaround - Leave the placeholder values in the
web.config
updates later in the lab. The integration will fail gracefully until you update the values and re-publish your Azure Web Application.
Create a Twitter App and get the following settings:
- Apply for a Twitter developer account and wait for approval.
- Once approved, you will be able to create new apps from developer.twitter.com.
- Create a new App and provide the application details.
NOTE: You can skip the callback url as we won't be using authentication.
NOTE: Website URL should be the same as the Azure Web App you created earlier. For example,
https://mxchip-<your initials>.azurewebsites.net
NOTE: Follow this link to get more information about creating Twitter Apps.
- Get the following information from the Keys and Access Tokens tab:
- Consumer Key (API Key)
- Consumer Secret (API Secret)
- Access token (create a new one with
Read and Write
access.) - Access token secret
NOTE: Copy these values into Notepad as you will need them later.
- Open Visual Studio 2017 and open the Web.config file which is located in the following location
.\MXDial-IoT-Sample\backend\MXApi\Web.config
. - Add the connection string for the IoT Hub:
- IoTHubConnectionString:
<your IoT Hub connection string>
- IoTHubConnectionString:
- Use the information previously obtained to complete the settings that will be used to connect to your twitter:
- TwitterAccountUrl:
https://twitter.com/<your_account_name>
- TwitterConsumerKey:
<your twitter consumer key>
- TwitterConsumerSecret:
<your twitter consumer secret>
- TwitterAccessToken:
<your twitter access token>
- TwitterAccessTokenSecret:
<your twitter access token secret>
- TwitterAccountUrl:
NOTE: We recommend leaving all over settings as the default value.
- Open a Command Prompt window and navigate to
frontend/mx
. - Run the following commands to output the frontend to a build directory:
- yarn install
- yarn build
- Create a wwwroot directory in
backend/MXApi
folder. - Copy the contents of the build directory to
backend/MXApi/wwwroot
For the purposes of our demo, we'll be deploying directly from Visual Studio.
- Open Visual Studio 2017 from the Start Menu.
- Click Open Project/Solution and select
backend\MxDialBackend.sln
. - Check your current connected account in the top right corner of Visual Studio.
NOTE: Ensure you are signed in with the same credentials you used to sign in to Azure. This will connect Visual Studio to your Azure subscription.
- Right-click the MxApi project.
- Click Publish.
- Mark the option Select Existing.
- Click Publish.
- Select the Web App previously created.
- Click OK and wait for the deployment to complete. This step might take a few minutes.
NOTE: Please ensure your MX Chip has the latest firmware. You can follow the instructions here: Firmware Upgrade.
NOTE: The MX AZ3166 Device only support basic authentication. Therefore, some corporate networks may not work correctly. One way of verifying this is connecting to a personal hotspot on your mobile device. This method should always work.
- Connect the Micro-USB end to the IoT DevKit.
- Connect the USB end to your computer.
- The green LED for power confirms the connection.
- Hold down button B, push and release the reset button, and then release button B. Your IoT DevKit enters AP mode for configuring the Wi-Fi connection. The screen displays the service set identifier (SSID) of the IoT DevKit and the configuration portal IP address:
- Use a Web browser on a different Wi-Fi enabled device (computer or mobile phone) to connect to the IoT DevKit SSID displayed in the previous step. If it asks for a password, leave it empty.
- Open 192.168.0.1 in the browser. Select the Wi-Fi network that you want the IoT DevKit to connect to, type the password for the Wi-Fi conection, and then click Connect.
- The IoT DevKit reboots in a few seconds. You then see the Wi-Fi name and assigned IP.
- Open VS Code then select
File > Open Workspace
. - Navigate to the
mxdevice
directory from the source code and open theproject
Workspace. - Open
config.h
and replace<Web App URL>
with the Web App URL you created earlier. It should look like:https://mxchip-<yourinitials>.azurewebsites.net/api/mx/device-credentials/
NOTE: If you don’t have Arduino extension in VS Code installed, click the Install in the notification pane if prompted. If you modified your password in the web.config, you will need to convert it to Base64.
- Save your project. Don't close it as you will need it for the next section.
- Ensure your DevKit is connected to your Windows machine and the
project
Workspace is open. If the IoT Workbench Examples window opens, you can close it. - Ensure you have the correct COM port selected. The correct port will have
STMicroelectronics
beside it. You can access the dropdown by clickingCOM<number>
in the bottom right of VS Code.
- Press
F1
on your keyboard. - Search for
IoT Workbench: Device
and select. - From the Device Menu, select
Device Upload
. - The code will compile and deploy to your device. Follow any prompts from the console if required.
- Plug in your device and get your Device ID from the mini display. It will be 6 characters.
- Open your Web App in a new browser window. It should look like
https://mxchip-<yourinitials>.azurewebsites.net
- The web site will request credentials to access, use the following:
- Username:
<Your 6 digit Device ID>
- Password:
Azure
.
- Username:
NOTE: Make sure that your device is on, otherwise you won't see anything in the web page.
- You should now see your device on your dashboard.
- Your Twitter feed should look like the following.
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.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., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.