nanoFramework.Iot.Device.Dhtxx.Esp32 1.2.869

Prefix Reserved
dotnet add package nanoFramework.Iot.Device.Dhtxx.Esp32 --version 1.2.869
                    
NuGet\Install-Package nanoFramework.Iot.Device.Dhtxx.Esp32 -Version 1.2.869
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="nanoFramework.Iot.Device.Dhtxx.Esp32" Version="1.2.869" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="nanoFramework.Iot.Device.Dhtxx.Esp32" Version="1.2.869" />
                    
Directory.Packages.props
<PackageReference Include="nanoFramework.Iot.Device.Dhtxx.Esp32" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add nanoFramework.Iot.Device.Dhtxx.Esp32 --version 1.2.869
                    
#r "nuget: nanoFramework.Iot.Device.Dhtxx.Esp32, 1.2.869"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package nanoFramework.Iot.Device.Dhtxx.Esp32@1.2.869
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=nanoFramework.Iot.Device.Dhtxx.Esp32&version=1.2.869
                    
Install as a Cake Addin
#tool nuget:?package=nanoFramework.Iot.Device.Dhtxx.Esp32&version=1.2.869
                    
Install as a Cake Tool

DHT10/DHT11/DHT12/DHT21/DHT22 for Esp32 using RMT - Digital-Output Relative Humidity & Temperature Sensor Module

IMPORTANT This implementation will only work on with ESP32. Don't use this implementation for those MCU. This implementation requires 2 pins. One is used to write to the sensor and the other is used to read the data using RMT.

The DHT temperature and humidity sensors are very popular. This projects support DHT10, DHT11, DHT12, DHT21(AM2301), DHT22(AM2302).

Documentation

DHT10 DHT11 DHT12 DHT21 DHT22
Image dht10 dht11 dht12 dht21 dht22
Temperature Range -40 ~ 80 ℃ 0 ~ 60 ℃ -20 ~ 60 ℃ -40 ~ 80 ℃ -40 ~ 80 ℃
Humidity Range 0 ~ 99.9 % 2 ~ 95 % 20 ~ 95 % 0 ~ 99.9 % 0 ~ 99.9 %
Temperature Accuracy ±0.5 ℃ ±2 ℃ ±0.5 ℃ ±0.5 ℃ ±0.5 ℃
Humidity Accuracy ±3 % ±5 % ±4 % ±3 % ±2 %
Protocol I2C 1-Wire I2C, 1-Wire 1-Wire 1-Wire

Usage

1-Wire Protocol

// GPIO Pin
using (Dht11 dht = new Dht11(12, 24))
{
    var temperature = dht.Temperature;
    var humidity = dht.Humidity;
    // You can only display temperature and humidity if the read is successful otherwise, this will raise an exception as
    // both temperature and humidity are NAN
    if (dht.IsLastReadSuccessful)
    {
        Debug.WriteLine($"Temperature: {temperature.DegreesCelsius} \u00B0C, Humidity: {humidity.Percent} %");

        // WeatherHelper supports more calculations, such as saturated vapor pressure, actual vapor pressure and absolute humidity.
        Debug.WriteLine(
            $"Heat index: {WeatherHelper.CalculateHeatIndex(temperature, humidity).Celsius:0.#}\u00B0C");
        Debug.WriteLine(
            $"Dew point: {WeatherHelper.CalculateDewPoint(temperature, humidity).Celsius:0.#}\u00B0C");
    }
    else
    {
        Debug.WriteLine("Error reading DHT sensor");
    }
}

Note: On the RPi with any of the DHT sensor, 1-Wire works using Raspian but not with Windows 10 IoT Core. The device has to switch the 1-wire pin between input and output and vice versa. It seems that Windows IoT Core OS can't switch the pin direction quick enough. There have been suggestions for using two pins; one for input and one for output. This solution has not been implemented here, but these are some handy links that may help setting that up:

I2C Protocol

Important: make sure you properly setup the I2C pins especially for ESP32 before creating the I2cDevice, make sure you install the nanoFramework.Hardware.ESP32 nuget:

//////////////////////////////////////////////////////////////////////
// when connecting to an ESP32 device, need to configure the I2C GPIOs
// used for the bus
Configuration.SetPinFunction(21, DeviceFunction.I2C1_DATA);
Configuration.SetPinFunction(22, DeviceFunction.I2C1_CLOCK);

For other devices like STM32, please make sure you're using the preset pins for the I2C bus you want to use.

Only DHT12 can use I2C protocol.

I2cConnectionSettings settings = new I2cConnectionSettings(1, DhtSensor.DefaultI2cAddressDht12);
I2cDevice device = I2cDevice.Create(settings);

using (Dht12 dht = new Dht12(device))
{
    var tempValue = dht.Temperature;
    var humValue = dht.Humidity;
    if (dht.IsLastReadSuccessful)
    {
        Debug.WriteLine($"Temperature: {tempValue.Celsius:0.#}\u00B0C");
        Debug.WriteLine($"Relative humidity: {humValue:0.#}%");

        // WeatherHelper supports more calculations, such as saturated vapor pressure, actual vapor pressure and absolute humidity.
        Debug.WriteLine(
            $"Heat index: {WeatherHelper.CalculateHeatIndex(tempValue, humValue).Celsius:0.#}\u00B0C");
        Debug.WriteLine(
            $"Dew point: {WeatherHelper.CalculateDewPoint(tempValue, humValue).Celsius:0.#}\u00B0C");
    }
    else
    {
        Debug.WriteLine("Error reading DHT sensor");
    }
}

Reading frequency and quality measurement

In the case of I2C or GPIO, any type of DHT needs a bit of time between 2 readings. DHT22 documentation refer to a sensing period of 2 seconds and a collecting period higher than 1.7 seconds. Measuring with higher frequency won't give you more accurate numbers. As you can see from the specifications, the accuracy depends on the sensor type, it goes from ±2 ℃ for the DHT11 to ±0.5 ℃ for the others. Even if the parity check can come clear, we do recommend to check that the data are in a normal range. For example of humidity is higher than 100%, then it means that measurement is wrong. This check has not been done in the binding itself, so you may consider adding a check on your application side.

The DHT sensors are very sensitive, avoid too long cables, electromagnetic perturbations and compile the code as release not debug to increase the quality of measurement.

FAQ

I always get wrong measurements, what's happening?

Please check that the sensor is plugged correctly, make sure you are using the correct pin.

Please check you are using the correct sensor, only DHT10 and DHT12 supports I2C. All others support only GPIO with 1 wire protocol. DHT12 supports both.

The data I measure are not correct, humidity seems ok but temperature is always weird, what's the problem?

Please check you are using the correct sensor. Refer to the top part of this page to check which sensor you have. Using a DHT11 instead of a DHT22 will give you a wrong temperature.

I am trying to get a temperature and humidity 5 times per seconds but I mainly get wrong measurements, why?

This is absolutely normal, you should check the measurements once every 2 seconds approximately. Don't try to get more measures than once every 2 seconds.

When reading the temperature and humidity and trying to write the data in the console, I get an exception, why?

You need to check first if the measurement has been successful. If the measurement hasn't been successful, the default values will be NaN and so you won't be able to convert the temperature or humidity and you'll get an exception. This is the correct way of first reading the sensor and then checking the reading was correct and finally using the temperature and humidity data:

var tempValue = dht.Temperature;
var humValue = dht.Humidity;
if (dht.IsLastReadSuccessful)
{
    Debug.WriteLine($"Temperature: {tempValue.Celsius:0.#}\u00B0C");
    Debug.WriteLine($"Relative humidity: {humValue:0.#}%");
}

Example of DHTxx

Hardware Required

  • DHT10/DHT11/DHT12/DHT21/DHT22
  • Male/Female Jumper Wires

Circuit

1-Wire Protocol Circuit

Simply connect your DHTxx data pin to GPIO12 and GPIO14, the ground to the ground and the VCC to +3.3V.

schema

Some sensors are already sold with the 10K resistor. Connect the both GPIO12 and GPIO14 to the data pin, its position can vary depending on the integrator.

I2C Protocol Circuit

schematics

  • SCL - SCL
  • SDA - SDA
  • VCC - 5V
  • GND - GND

Code

// GPIO Pin
using (Dht11 dht = new Dht11(26))
{
    var temperature = dht.Temperature;
    var humidity = dht.Humidity;
    // You can only display temperature and humidity if the read is successful otherwise, this will raise an exception as
    // both temperature and humidity are NAN
    if (dht.IsLastReadSuccessful)
    {
        Debug.WriteLine($"Temperature: {temperature.DegreesCelsius} \u00B0C, Humidity: {humidity.Percent} %");

        // WeatherHelper supports more calculations, such as saturated vapor pressure, actual vapor pressure and absolute humidity.
        Debug.WriteLine(
            $"Heat index: {WeatherHelper.CalculateHeatIndex(temperature, humidity).Celsius:0.#}\u00B0C");
        Debug.WriteLine(
            $"Dew point: {WeatherHelper.CalculateDewPoint(temperature, humidity).Celsius:0.#}\u00B0C");
    }
    else
    {
        Debug.WriteLine("Error reading DHT sensor");
    }
}

Sample application navigation

This sample application allows you to select either a DHT10 through I2C either any other supported DHT through GPIO:

Select the DHT sensor you want to use:
 1. DHT10 on I2C
 2. DHT11 on GPIO
 3. DHT12 on GPIO
 4. DHT21 on GPIO
 5. DHT22 on GPIO

Just adjust the device variable. For example, if you want to test a DHT22, adjust it to 5.

// Set these values to test according to the list below:
var pinEcho = 12;
var pinTrigger = 14;
var device = 5;

This samples uses the pins 12 and 14. If you want to use the pin 26 and 10, then adjust the pinEcho and pinTrigger variables. This will then create a DHT22 sensor attached to pin 26 and start the measurement.

Please note that the few first measurements won't be correct, that's totally normal and related to the fact the sensor needs a bit of time to warm up and give data. Those sensors are very sensitive and too long wires, many perturbations, code compile as debug will increase the numbers of bad readings.

Result

dht22 output

Note: reading this sensor is sensitive, if you can't read anything, make sure you have it correctly cabled. Also note you'll get better results when running in Release mode.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.2.869 230 4/2/2025
1.2.864 190 4/2/2025
1.2.852 204 3/11/2025
1.2.846 202 3/10/2025
1.2.835 132 2/27/2025
1.2.829 126 2/27/2025
1.2.822 145 2/26/2025
1.2.775 148 2/4/2025
1.2.772 139 2/4/2025
1.2.755 131 1/31/2025
1.2.743 144 1/20/2025
1.2.737 118 1/13/2025
1.2.718 144 12/30/2024
1.2.696 158 12/16/2024
1.2.673 179 10/23/2024
1.2.662 140 10/11/2024
1.2.656 146 10/3/2024
1.2.639 169 9/6/2024
1.2.631 136 8/28/2024
1.2.613 159 8/9/2024
1.2.611 123 8/6/2024
1.2.601 125 7/26/2024
1.2.595 118 7/24/2024
1.2.590 137 7/17/2024
1.2.573 166 6/19/2024
1.2.570 143 6/14/2024
1.2.560 146 5/29/2024
1.2.548 139 5/15/2024
1.2.536 172 4/15/2024
1.2.514 171 3/22/2024
1.2.494 168 2/28/2024
1.2.474 193 1/24/2024
1.2.462 207 1/5/2024
1.2.458 190 12/20/2023
1.2.436 226 11/10/2023
1.2.416 170 11/8/2023
1.2.403 205 10/6/2023
1.2.396 189 9/27/2023
1.2.384 239 9/6/2023
1.2.378 225 8/16/2023
1.2.369 248 8/2/2023
1.2.363 211 7/28/2023
1.2.357 226 7/19/2023
1.2.354 220 7/14/2023
1.2.345 226 6/21/2023
1.2.341 220 6/14/2023
1.2.337 243 6/7/2023
1.2.335 235 6/2/2023
1.2.329 235 5/26/2023
1.2.316 243 5/16/2023
1.2.313 239 5/12/2023
1.2.302 235 5/10/2023
1.2.297 248 5/3/2023
1.2.273 377 3/17/2023
1.2.267 317 3/10/2023
1.2.263 325 3/8/2023
1.2.259 332 2/27/2023
1.2.256 350 2/24/2023
1.2.253 341 2/22/2023
1.2.235 359 2/13/2023
1.2.222 401 1/9/2023
1.2.217 393 1/6/2023
1.2.208 400 1/3/2023
1.2.203 391 12/28/2022
1.2.159 494 11/14/2022
1.2.153 453 11/5/2022
1.2.141 502 10/25/2022
1.2.128 496 10/22/2022
1.2.122 540 10/12/2022
1.2.114 517 10/8/2022
1.2.95 539 9/22/2022
1.2.87 576 9/15/2022
1.2.73 499 9/8/2022
1.2.63 537 9/3/2022
1.2.47 564 8/15/2022
1.2.40 535 8/6/2022
1.2.38 529 8/5/2022
1.2.28 524 8/1/2022
1.2.13 522 7/24/2022
1.2.10 531 7/23/2022
1.1.142.3202 568 7/7/2022
1.1.133.52556 546 6/30/2022
1.1.121.35854 557 6/26/2022
1.1.116.8772 519 6/24/2022
1.1.113.2032 536 6/23/2022
1.1.102.51394 515 6/15/2022
1.1.99.36719 527 6/14/2022
1.1.72.29765 552 5/31/2022
1.1.64.21380 559 5/26/2022
1.1.58.10097 551 5/23/2022
1.1.54.28879 543 5/23/2022
1.1.51.31918 559 5/20/2022
1.1.40 595 5/5/2022
1.1.3 568 4/15/2022
1.1.1 553 4/14/2022
1.0.300 559 3/31/2022
1.0.28-preview.114 190 3/25/2022
1.0.28-preview.113 180 3/25/2022
1.0.28-preview.103 176 3/21/2022
1.0.28-preview.100 179 3/19/2022
1.0.28-preview.99 187 3/18/2022
1.0.28-preview.98 173 3/18/2022
1.0.28-preview.94 192 3/15/2022
1.0.28-preview.93 182 3/15/2022
1.0.28-preview.86 194 3/8/2022
1.0.28-preview.77 192 2/27/2022
1.0.28-preview.75 181 2/26/2022
1.0.28-preview.65 194 2/18/2022
1.0.28-preview.63 180 2/16/2022
1.0.28-preview.61 191 2/12/2022
1.0.28-preview.58 182 2/10/2022
1.0.28-preview.53 191 2/9/2022
1.0.28-preview.48 208 2/4/2022
1.0.28-preview.42 203 1/31/2022
1.0.28-preview.41 200 1/31/2022
1.0.28-preview.29 197 1/28/2022
1.0.28-preview.22 189 1/27/2022
1.0.28-preview.20 196 1/27/2022
1.0.28-preview.19 211 1/27/2022
1.0.28-preview.18 197 1/27/2022
1.0.28-preview.5 197 1/24/2022
1.0.28-preview.3 196 1/21/2022
1.0.28-preview.1 194 1/21/2022
1.0.12 245 1/10/2022
1.0.2 427 12/23/2021
1.0.1 231 12/22/2021