Arduino Coding Basics: Build and Debug a DHT22 Sensor Station

Project Overview and Hardware Spec Sheet

Mastering arduino coding basics means moving beyond blinking an LED to reading real-world sensors, handling I2C displays, and managing library dependencies. The core paradigm relies on the setup() function for initialization and the loop() function for continuous execution. To prove this, we will build an environmental monitoring station that reads temperature and humidity, then outputs the data to an OLED screen.

This guide targets the Arduino Uno R4 WiFi (ABX00080). While the older Uno R3 is still common, the R4 WiFi is the current 2026 standard for new builds, featuring a 32-bit ARM Cortex-M4 processor, 256KB flash, and native WiFi/BLE via the ESP32-S3 coprocessor. It operates at 5V logic but includes a dedicated 3.3V LDO, making it highly versatile for mixed-voltage sensor networks.

Required Parts List

Pin Mapping Table

Correct pin mapping is where most beginners fail. The Uno R4 WiFi has dedicated I2C headers, but they map to specific digital pins internally.

Arduino Coding Basics: The Complete Sketch

Below is the complete, compilable C++ sketch. It includes explicit pin definitions, library imports, and crucial error handling for both the sensor read cycle and the display initialization. You must install the Adafruit SSD1306 and DHT sensor library (by Adafruit) via the Arduino IDE Library Manager before compiling.

#include 
#include 
#include 
#include 

// --- PIN DEFINITIONS ---
#define DHTPIN 2          // Digital pin connected to the DHT sensor
#define DHTTYPE DHT22     // Sensor type (DHT11, DHT22, or DHT21)
#define SCREEN_WIDTH 128  // OLED display width, in pixels
#define SCREEN_HEIGHT 64  // OLED display height, in pixels
#define OLED_RESET -1     // Reset pin (or -1 if sharing Arduino reset pin)
#define SCREEN_ADDRESS 0x3C // I2C address (usually 0x3C or 0x3D)

// --- OBJECT INITIALIZATION ---
DHT dht(DHTPIN, DHTTYPE);
Adafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, OLED_RESET);

void setup() {
  Serial.begin(115200);
  // Wait for serial port to connect (useful for native USB boards like R4)
  while (!Serial && millis() < 5000) { delay(100); }
  
  Serial.println("Initializing DHT22 and OLED...");
  dht.begin();

  // Error handling: Check if OLED is actually connected and responding
  if(!display.begin(SSD1306_SWITCHCAPVCC, SCREEN_ADDRESS)) {
    Serial.println(F("SSD1306 allocation failed or I2C address incorrect!"));
    Serial.println(F("Check wiring and run an I2C Scanner sketch to verify address."));
    // Halt execution if display fails to prevent null pointer crashes later
    for(;;); 
  }

  // Clear the buffer and set text parameters
  display.clearDisplay();
  display.setTextColor(SSD1306_WHITE);
  display.setTextSize(1);
  display.setCursor(0, 0);
  display.println("System Ready.");
  display.display();
  delay(1000);
}

void loop() {
  // DHT22 requires a minimum 2-second delay between reads
  delay(2000); 

  float humidity = dht.readHumidity();
  float tempC = dht.readTemperature();
  float tempF = dht.readTemperature(true);

  // Error handling: Check if any reads failed (returns NaN)
  if (isnan(humidity) || isnan(tempC) || isnan(tempF)) {
    Serial.println(F("Failed to read from DHT sensor! Check wiring and pull-up."));
    display.clearDisplay();
    display.setCursor(0,0);
    display.println("DHT22 Read Error!");
    display.display();
    return; // Skip the rest of the loop and try again next cycle
  }

  // Print to Serial Monitor
  Serial.print("Humidity: "); Serial.print(humidity);
  Serial.print("% | Temp: "); Serial.print(tempC);
  Serial.print("C / "); Serial.print(tempF); Serial.println("F");

  // Render to OLED
  display.clearDisplay();
  display.setCursor(0, 0);
  display.setTextSize(2);
  display.print(tempF, 1);
  display.println(" F");
  
  display.setTextSize(1);
  display.print("Humidity: ");
  display.print(humidity, 1);
  display.println(" %");
  
  display.display();
}

Debugging: First Three Things to Check When It Fails

When your sketch fails to compile or the hardware acts dead, do not immediately rewrite your code. Follow this ranked checklist to isolate the fault.

1. Verify Board and Port Selection: In the Arduino IDE, go to Tools > Board and ensure Arduino Uno R4 WiFi is selected (not the Minima or the old R3). Then check Tools > Port. If the port is greyed out, your USB cable is likely charge-only (lacking data lines). Swap to a known data-capable USB-C cable.
2. Confirm Exact Library Versions: Go to Sketch > Include Library > Manage Libraries. Search for "Adafruit SSD1306" and "DHT sensor library". Install them directly from the manager. Do not download random ZIP files from GitHub forums; dependency mismatches between the GFX library and the SSD1306 library are a primary cause of compilation failures.
3. Run an I2C Scanner: If the code compiles but the OLED stays black, the I2C address might be 0x3D instead of 0x3C. Upload a basic "I2C Scanner" sketch (available via Arduino official docs) to print all responding addresses to the Serial Monitor. Update the SCREEN_ADDRESS define in your code to match.

Common Error Strings and Ranked Causes

Error String: fatal error: DHT.h: No such file or directory

• Cause 1 (Most Likely): The DHT library is not installed. Install "DHT sensor library" by Adafruit via the Library Manager.
• Cause 2: You installed the library but forgot to restart the Arduino IDE. The IDE sometimes fails to index new libraries until a restart.
• Cause 3: Typo in the include statement. It must be exactly #include (case-sensitive on Linux/macOS file systems).

Error String: DHT timeout reading! (Printed to Serial Monitor during runtime)

• Cause 1 (Most Likely): Missing pull-up resistor. If you are using a bare 3-pin DHT22 component instead of the 4-pin module, you must solder a 10kΩ resistor between VCC and the DATA pin.
• Cause 2: Polling too fast. The DHT22 hardware requires a strict 2-second minimum delay between read requests. Ensure your delay(2000) is present.
• Cause 3: Voltage sag. Powering the DHT22 from the 3.3V pin on a long breadboard run can cause signal degradation. Switch to the 5V pin.

Extending and Simplifying the Build

Once you have the arduino coding basics down and the sensor reading reliably, you can scale the project up or down based on your needs.

How to Extend: Add MQTT over WiFi

Because we chose the Uno R4 WiFi, you can push this data to a home automation hub like Home Assistant. Add the WiFiS3.h and ArduinoMqttClient.h libraries. In your setup(), connect to your local 2.4GHz network. In the loop(), format the tempC and humidity floats into a JSON string and publish them to an MQTT broker (like Mosquitto) every 10 seconds. This transforms a local desk gadget into an IoT node.

How to Simplify: Strip the Display

If you only need data logging and want to reduce the BOM cost and code complexity, remove the OLED entirely. Delete the Wire.h, Adafruit_GFX.h, and Adafruit_SSD1306.h includes. Remove all display.* function calls. Rely solely on Serial.println() to output CSV-formatted data to your PC, which you can then pipe into a Python script or Excel for graphing.

Arduino Coding Basics FAQ

What are the core arduino coding basics for reading analog vs digital pins?

Digital pins read binary states: HIGH (approx 5V on the Uno R4) or LOW (0V). You use digitalRead(pin) for buttons and digitalWrite(pin, state) for relays. Analog pins, however, use an internal Analog-to-Digital Converter (ADC) to measure voltage gradients. On the Uno R4, analogRead(pin) returns a 14-bit value (0 to 16383) representing 0V to 5V. Use digital pins for the DHT22 because it uses a proprietary single-bus digital protocol, not a raw voltage output.

How do I fix the "expected unqualified-id before '{' token" error in Arduino?

This is a classic syntax error indicating a stray semicolon or a missing function declaration. It usually happens when you accidentally place a semicolon after a function definition, like void loop(); {. Remove the semicolon. It can also occur if you define a macro with #define that accidentally conflicts with a variable name used later in the code. Check your #define statements at the top of the sketch for naming collisions.

Why is my Arduino sketch compiling but the serial monitor is blank?

First, ensure your Serial Monitor baud rate (bottom right corner of the IDE window) exactly matches the Serial.begin() value in your code (e.g., 115200). If they mismatch, you will see garbled text or nothing at all. Second, on native USB boards like the Uno R4, the serial port resets when the board reboots. Add while (!Serial && millis() < 5000) { delay(100); } immediately after Serial.begin() to pause the sketch until the PC actually connects to the virtual COM port.

Can I use arduino coding basics learned on an Uno R3 for the ESP32?

Yes, the core C++ syntax, setup()/loop() structure, and most standard libraries (like Wire and SPI) transfer directly. However, the ESP32 operates at 3.3V logic, not 5V. Connecting a 5V sensor directly to an ESP32 GPIO pin without a logic level shifter will permanently damage the silicon. Additionally, the ESP32 ADC is non-linear and operates on a 0-3.3V scale with 12-bit resolution (0-4095), requiring different mapping math than the Uno.