{"id":34638,"date":"2020-07-20T08:16:06","date_gmt":"2020-07-20T00:16:06","guid":{"rendered":"\/blog\/?p=34638"},"modified":"2020-07-20T09:37:16","modified_gmt":"2020-07-20T01:37:16","slug":"improve-health-wellbeing-and-productivity-by-tracking-your-home-workspace-co2-levels","status":"publish","type":"post","link":"https:\/\/www.seeedstudio.com\/blog\/2020\/07\/20\/improve-health-wellbeing-and-productivity-by-tracking-your-home-workspace-co2-levels\/","title":{"rendered":"Improve health, wellbeing, and productivity by tracking your home workspace CO2 levels"},"content":{"rendered":"\n

The following content is written by Dave Glover<\/a>, Microsoft Cloud Developer Advocate. Feel free to follow him on Twitter @dglover<\/p>\n\n\n\n

How to build a healthier working environment by monitoring CO2, temperature, and humidity levels with a Seeed Studio Azure Sphere device<\/a>, an SDC30 sensor<\/a>, and Azure IoT Central<\/a>.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

<\/p>\n\n\n\n

\n\n\n\n

<\/a>#JulyOT<\/h2>\n\n\n\n

This is part of the #JulyOT IoT Tech Community<\/a> series, a collection of blog posts, hands-on-labs, and videos designed to demonstrate and teach developers how to build projects with Azure Internet of Things (IoT) services. Please also follow #JulyOT<\/a> on Twitter.<\/p>\n\n\n\n

\n\n\n\n

<\/a>Source code and learning resources<\/h2>\n\n\n\n

Source code: Track CO2 levels in your workspace to improve health, wellbeing, and productivity<\/a>.<\/p>\n\n\n\n

Learning resources: Azure Sphere Developer Learning Path<\/a>.<\/p>\n\n\n\n

\n\n\n\n

<\/a>Are CO2 levels making you grumpy, sleepy, or sad<\/h2>\n\n\n\n

Working from home it is easy to close the door to shut out the noise of everyday life while we get on with work. Closing the door can lead to a build-up of CO2 gas, a by-product of our breathing, which can impact our wellbeing, concentration, and productivity levels.<\/p>\n\n\n\n

Check out “Indoor carbon dioxide levels could be a health hazard, scientists warn<\/a>“.<\/p>\n\n\n\n

The problem is we cannot see or smell Carbon Dioxide, it just keeps building up, and we have no way of knowing it is happening other than getting tired or a headache. So, with that in mind, I figured it was the Internet of Things to the rescue!<\/p>\n\n\n\n

\n\n\n\n

<\/a>The solution<\/h2>\n\n\n\n

I wanted to build a secure IoT device with Azure Sphere<\/a> using the Seeed Studio Grove CO2 & Temperature & Humidity Sensor<\/a> I had in my box of bits. The folks at Sensirion made it super easy to port their SCD30 driver<\/a> to Azure Sphere. It was just a matter of implementing the I2C init\/read\/write functions, a microsecond sleep function, plus setting up CMake build. It all just worked. The ported driver is included in this project.<\/p>\n\n\n\n

\n\n\n\n

<\/a>Azure IoT Central<\/h2>\n\n\n\n

Azure IoT Central<\/a> provides an easy way to connect, monitor, and manage your Internet of Things (IoT) assets at scale.<\/p>\n\n\n\n

I created a free trial of Azure IoT Central<\/a> and in no time I had CO2, temperature, and humidity telemetry displayed (yes, the data is real, so we have made some changes at home!). By the way, you can continue to connect two devices for free to IoT Central after the trial period expires.<\/p>\n\n\n\n

\"\"\/<\/a><\/figure>\n\n\n\n

<\/a>Extend and integrate Azure IoT Central applications with other cloud services<\/h3>\n\n\n\n

Azure IoT Central is also extensible using rules and workflows. For more information, review Use workflows to integrate your Azure IoT Central application with other cloud services<\/a><\/p>\n\n\n\n

\n\n\n\n

<\/a>Parts list<\/h2>\n\n\n\n

The solution supports two configurations.<\/p>\n\n\n\n

<\/a>Seeed Studio Azure Sphere Mini Dev Board<\/h3>\n\n\n\n
  1. Seeed Studio Seeed Studio MT3620 Mini Dev Board<\/a><\/li>
  2. MT3620 Grove Breakout<\/a><\/li>
  3. Seeed Studio Grove CO2 & Temperature & Humidity Sensor<\/a><\/li>
  4. Optional, 3 x Grove LEDs<\/a>, or a Grove Relay<\/a> to drive a bigger warning light!<\/li><\/ol>\n\n\n\n

    <\/a>Connect Grove peripherals<\/h3>\n\n\n\n

    Attach the Azure Sphere to the Grove Breakout board and plug in the following peripherals.<\/p>\n\n\n\n

    1. Green LED plugged into Grove Socket D1<\/li>
    2. Red LED plugged into Grove Socket D0<\/li>
    3. Blue LED plugged into Grove Socket UART0<\/li>
    4. CO2, Temperature, & Humidity sensor into Grove Socket I2C<\/li><\/ol>\n\n\n\n
      \"\"<\/a><\/figure><\/div>\n\n\n\n

      <\/a>AVNET Azure Sphere Starter Kit<\/h3>\n\n\n\n
      1. AVNET Azure Sphere Starter Kit<\/a><\/li>
      2. Seeed Studio Grove CO2 & Temperature & Humidity Sensor<\/a><\/li>
      3. Optional, 1 x Click Relay<\/a> to drive a bigger warning light.<\/li><\/ol>\n\n\n\n

        <\/a>Connect the Grove peripheral<\/h3>\n\n\n\n
        1. Plug the CO2, Temperature, & Humidity sensor into Grove Socket I2C on the AVNET Starter Kit.<\/li><\/ol>\n\n\n\n
          \"\"<\/a><\/figure><\/div>\n\n\n\n
          \n\n\n\n

          <\/a>Calibrating the SCD20 CO2 Sensor<\/h2>\n\n\n\n

          IMPORTANT<\/strong>. Be sure to read up on calibrating the Grove – CO2 & Temperature & Humidity Sensor (SCD30) Calibration<\/a> sensor. This solution will enable auto-calibration.<\/p>\n\n\n\n

          \n\n\n\n

          <\/a>How to build the solution<\/h2>\n\n\n\n

          Clone the Azure Sphere CO2 Monitor<\/strong> solution to your desktop.<\/p>\n\n\n\n

          git clone https:\/\/github.com\/gloveboxes\/Track-CO2-levels-in-your-workspace-to-improve-health-wellbeing-and-productivity.git azure-sphere-co2-monitor<\/pre>\n\n\n\n
          \n\n\n\n
          <\/a>Set up your developer tools and your Azure Sphere<\/h2>\n\n\n\n
          Follow the Azure Sphere Developer Learning Path Lab Set Up<\/a> to set up the developer tools, claim you Azure Sphere, and configure the device WiFi, and enable developer mode.<\/p>\n\n\n\n
          \n\n\n\n
          <\/a>Azure IoT Central<\/h2>\n\n\n\n
          Your Azure Sphere device can securely connect and communicate with cloud services. Azure Sphere includes built-in library support for both Azure IoT Hub and Azure IoT Central. This lab focuses on Azure IoT Central. Take a moment to read Your IoT journey: simplified and secure with Azure IoT Central and Azure Sphere<\/a>.<\/p>\n\n\n\n
          Azure IoT Central<\/a> provides an easy way to connect, monitor, and manage your Internet of Things (IoT) assets at scale.<\/p>\n\n\n\n
          \"Azure<\/a><\/figure><\/div>\n\n\n\n
          \n\n\n\n
          <\/a>Step 1: Create a new IoT Central Application<\/h2>\n\n\n\n
          1. So the lab instructions are still visible, right mouse click, and open this link “Azure IoT Central<\/a>” in a new window.<\/li>
          2. Click Build a solution<\/strong>.<\/li>
          3. Next, you will need to sign with your Microsoft Personal, or Work, or School account. If you do not have a Microsoft account, then you can create one for free using the Create one!<\/strong> link.<\/a><\/li>
          4. Expand the sidebar menu by clicking on the Burger menu<\/strong> icon.<\/a><\/li>
          5. Click + New application<\/strong> to create a new Azure IoT Central application.<\/li>
          6. Select Custom app<\/strong><\/a><\/li><\/ol>\n\n\n\n
            <\/a>Create a new application<\/h3>\n\n\n\n
            1. Specify the Application name<\/strong>, the URL<\/strong>, select the Free<\/strong> pricing plan, and complete the registration form.<\/a><\/li>
            2. Then click Create<\/strong>.<\/li><\/ol>\n\n\n\n
              <\/a>Create a new device template<\/h3>\n\n\n\n
              A device template is a blueprint that defines the characteristics and behaviors of a type of device that connects to an Azure IoT Central application.<\/p>\n\n\n\n
              For more information on device templates, review the Define a new IoT device type in your Azure IoT Central application<\/a> article.<\/p>\n\n\n\n
              1. <\/a>Click Device templates<\/strong>, then + New<\/strong>. <\/li>
              2. Click the IoT device<\/strong> template type.<\/a><\/li>
              3. Create an IoT Device<\/strong> Template.
                1. Select IoT device<\/strong>,<\/li>
                2. Click Next:Customise<\/strong>,<\/li>
                3. Name your template Carbon Dioxide Monitor<\/strong>,<\/li>
                4. Click Next: Review<\/strong>,<\/li>
                5. Click Create<\/strong>.<\/li><\/ol><\/li><\/ol>\n\n\n\n
                  <\/a>Import a Capability Model<\/h3>\n\n\n\n
                  1. Click Import capability model<\/strong><\/li>
                  2. Navigate to the folder you cloned the CO2 Monitor solution into.<\/li>
                  3. Navigate to the iot_central<\/strong> folder.<\/li>
                  4. Select CO2_Monitor_Capability_Model.json<\/strong> and open<\/li><\/ol>\n\n\n\n
                    <\/a>Create a device visualization view<\/h3>\n\n\n\n
                    1. Click Views<\/strong>. <\/a><\/li>
                    2. Select Visualizing the device<\/strong>. <\/a><\/li>
                    3. Expand the Telemetry<\/strong> section<\/li>
                    4. Select Carbon Dioxide (ppm)<\/strong><\/li>
                    5. Click Add Tile<\/strong><\/li>
                    6. Select Humidity<\/strong> and Temperature<\/strong> telemetry items.<\/li>
                    7. Click Add Tile<\/strong>.<\/li>
                    8. Click Save<\/strong> to save the view. <\/a><\/li><\/ol>\n\n\n\n
                      <\/a>Create a properties form<\/h3>\n\n\n\n
                      1. Click Views<\/strong>.<\/li>
                      2. Click the Editing device and cloud data<\/strong> option. <\/a><\/li>
                      3. Expand the Properties<\/strong> section.<\/li>
                      4. Select all properties<\/strong>.<\/li>
                      5. Click Add Section<\/strong>.<\/li>
                      6. Click Save<\/strong> to save the form. <\/a><\/li><\/ol>\n\n\n\n
                        <\/a>Publish the device template<\/h3>\n\n\n\n
                        1. <\/a>Click Publish<\/strong> to publish the template. Publishing the template makes it available for devices. 
                          <\/li>
                        2. Next, confirm and click Publish<\/strong><\/li><\/ol>\n\n\n\n
                          See Define a new IoT device type in your Azure IoT Central application<\/a> for information on creating your own device templates.<\/p><\/blockquote>\n\n\n\n
                          \n\n\n\n
                          <\/a>Step 2: Link your Azure Sphere Tenant to IoT Central<\/h2>\n\n\n\n
                          You need to set up a trust relationship between your Azure Sphere tenant and your IoT Central application.<\/p>\n\n\n\n
                          Devices claimed by your Azure Sphere tenant will be automatically enrolled when it first connects to your IoT Central application.<\/p>\n\n\n\n
                          <\/a>Download the tenant authentication CA certificate<\/h3>\n\n\n\n
                          1. Open an Azure Sphere Developer Command Prompt<\/strong><\/li>
                          2. Be sure to make a note of the current directory, or change to the CO2 Monitor directory. You will need the name of this directory in the next step.<\/li>
                          3. Download the Certificate Authority (CA) certificate for your Azure Sphere tenant:azsphere tenant download-CA-certificate –output CAcertificate.cerThe output file must have the .cer extension.<\/li><\/ol>\n\n\n\n
                            <\/a>Upload the tenant CA certificate to Azure IoT Central and generate a verification code<\/h3>\n\n\n\n
                            1. In Azure IoT Central, go to Administration > Device Connection > Manage primary certificate.<\/li>
                            2. Click the folder icon next to the Primary box and navigate to the directory where you downloaded the certificate. If you don’t see the .cer file in the list, make sure that the view filter is set to All files (*). Select the certificate and then click the gear icon next to the Primary box.<\/li>
                            3. The Primary Certificate dialog box appears. The Subject and Thumbprint fields contain information about the current Azure Sphere tenant and primary root certificate.<\/li>
                            4. Click the Refresh icon to the right of the Verification Code box to generate a verification code. Copy the verification code to the clipboard.<\/a><\/li><\/ol>\n\n\n\n
                              <\/a>Verify the tenant CA certificate<\/h3>\n\n\n\n
                              1. Return to the Azure Sphere Developer Command Prompt.<\/li>
                              2. Download a validation certificate that proves that you own the tenant CA certificate. Replace code in the command with the verification code from the previous step.azsphere tenant download-validation-certificate –output ValidationCertification.cer –verificationcode <code><\/li>
                              3. The Azure Sphere Security Service signs the validation certificate with the verification code to prove that you own the CA.<\/li><\/ol>\n\n\n\n
                                <\/a>Use the validation certificate to verify the tenant identity<\/h3>\n\n\n\n
                                1. Return to Azure IoT Central and click Verify.<\/li>
                                2. When prompted, navigate to the validation certificate that you downloaded in the previous step and select it. When the verification process is complete, the Primary Certificate dialog box displays the Verified message. Click Close to dismiss the box.<\/a><\/li><\/ol>\n\n\n\n
                                  After you complete these steps, any device that is claimed into your Azure Sphere tenant will automatically be enrolled in your Azure IoT Central application when it first connects.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  <\/a>Step 3: Explicitly allow connections to Azure IoT Central Endpoints<\/h2>\n\n\n\n
                                  Remember, applications on Azure Sphere are locked down by default, including hardware and network endpoints. You must explicitly allow connections to the network endpoints of your Azure IoT Central application otherwise your Azure Sphere application will not be able to connect.<\/p>\n\n\n\n
                                  Follow these steps:<\/p>\n\n\n\n
                                  1. Open the Azure Sphere Developer Command Prompt<\/strong>.<\/li>
                                  2. Navigate to the Samples -> AzureIoT -> Tools directory. You cloned the Azure Sphere samples repository in the first lab.
                                    1. On Windows, navigate to the Samples\\AzureIoT\\Tools\\win-x64 directory.<\/li>
                                    2. On Linux, navigate to the Samples\\AzureIoT\\Tools\\linux-x64 directory. On Linux, you may need to explicitly set execution permissions for the ShowIoTCentralConfig tool. From a terminal, run chmod +x ShowIoTCentralConfig<\/code> to add execution permissions for the tool.<\/li><\/ol><\/li>
                                    3. When you run the ShowIoTCentralConfig<\/strong> tool, you will be prompted for input data. The following table outlines what information you will be prompted for and where to obtain the required data. <\/li><\/ol>\n\n\n\n
                                      Input data<\/th>From<\/th><\/tr><\/thead>
                                      Are you using a legacy (2018) IoT Central application (Y\/N)<\/strong><\/td>Respond N<\/strong><\/td><\/tr>
                                      IoT Central App URL<\/strong><\/td>This can be found in your browser address bar. For Example https:\/\/myiotcentralapp.azureiotcentral.com\/<\/a><\/td><\/tr>
                                      API token<\/strong><\/td>This can be generated from your IoT Central application. In the Azure IoT Central application select Administration<\/strong>, select API Tokens<\/strong>, select Generate Token<\/strong>, provide a name for the token (for example, “AzureSphereSample”), select Administrator<\/strong> as the role, and click Generate<\/strong>. Copy the token to the clipboard. The token starts with SharedAccessSignature<\/strong>.<\/td><\/tr>
                                      ID Scope<\/strong><\/td>In the Azure IoT Central application, select Administration<\/strong> > Device Connection<\/strong> and then copy the ID Scope<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                      4. Run the ShowIoTCentralConfig<\/strong> tool. Now follow the prompts that the tool provides, and copy the information from the output into the app_manifest.json file in Visual Studio. <\/p>\n\n\n\n
                                      Note<\/strong>: Your organization might require consent for the ShowIoTCentralConfig tool to access your Azure IoT Central data in the same way that the Azure API requires such consent. In some organizations, enterprise application permissions<\/a> must be granted by an IT administrator.<\/em><\/p>\n\n\n\n
                                      5. Review the output from the ShowIoTCentralConfig<\/strong> tool. It will look similar to the following text.
                                      Find and modify the CmdArgs, AllowedConnections and DeviceAuthentication lines in your app_manifest.json so each includes the content from the below:<\/p>\n\n\n\n
                                      \"CmdArgs\": [ \"0ne000BDC00\" ],\n\"Capabilities\": {\n    \"AllowedConnections\": [ \"global.azure-devices-provisioning.net\", \"iotc-9999bc-3305-99ba-885e-6573fc4cf701.azure-devices.net\", \"iotc-789999fa-8306-4994-b70a-399c46501044.azure-devices.net\", \"iotc-7a099966-a8c1-4f33-b803-bf29998713787.azure-devices.net\", \"iotc-97299997-05ab-4988-8142-e299995acdb7.azure-devices.net\", \"iotc-d099995-7fec-460c-b717-e99999bf4551.azure-devices.net\", \"iotc-789999dd-3bf5-49d7-9e12-f6999991df8c.azure-devices.net\", \"iotc-29999917-7344-49e4-9344-5e0cc9999d9b.azure-devices.net\", \"iotc-99999e59-df2a-41d8-bacd-ebb9999143ab.azure-devices.net\", \"iotc-c0a9999b-d256-4aaf-aa06-e90e999902b3.azure-devices.net\", \"iotc-f9199991-ceb1-4f38-9f1c-13199992570e.azure-devices.net\" ],\n    \"DeviceAuthentication\": \"--- YOUR AZURE SPHERE TENANT ID---\",\n}<\/code><\/pre>\n\n\n\n
                                      7. Copy<\/strong> the output from the ShowIoTCentralConfig tool to Notepad<\/em><\/strong> as you will need this information soon.<\/p>\n\n\n\n
                                      \n\n\n\n
                                      <\/a>Step 4: Get the Azure Sphere Tenant ID<\/h2>\n\n\n\n
                                      We need the ID of the Azure Sphere Tenant that is now trusted by Azure IoT Central.<\/p>\n\n\n\n
                                      1. From the Azure Sphere Developer Command Prompt<\/strong>, run azsphere tenant show-selected<\/code><\/strong>.