Top Uses of Raspberry Pi: Build an MQTT Data Logger

When evaluating the uses of Raspberry Pi in embedded engineering, it is easy to get distracted by desktop-replacement benchmarks or media center projects. However, the most robust industrial and hobbyist applications leverage the Pi's GPIO headers, low-power variants, and native Linux environment to act as edge gateways, data loggers, and protocol translators.

Rather than treating the Pi as a generic microcontroller, successful embedded deployments match the specific board variant to the power, compute, and I/O constraints of the environment. Below, we break down which Pi model fits which embedded use case, followed by a complete, code-backed build for a remote MQTT environmental logger.

Matching Raspberry Pi Models to Their Best Embedded Uses

Not every project needs an 8GB powerhouse. Selecting the wrong board leads to wasted budget, thermal throttling, or unnecessary power draw on battery-backed nodes. Here is a data-dense comparison of current models for embedded applications.

For remote environmental monitoring where power efficiency and physical footprint matter, the Raspberry Pi Zero 2 W remains the undisputed champion. It draws less than a watt at idle but packs a quad-core Cortex-A53, allowing it to handle TLS-encrypted MQTT handshakes without the multi-second latency seen on the original Pi Zero.

Project Build: Pi Zero 2 W MQTT Environmental Logger

This build targets the Raspberry Pi Zero 2 W. We will interface an I2C BME280 sensor to read temperature, humidity, and barometric pressure, then publish the JSON payload to a local MQTT broker every 10 seconds.

Parts List

• Microcontroller: Raspberry Pi Zero 2 W (with pre-soldered 40-pin header)
• Sensor: Adafruit BME280 I2C Breakout (Product ID: 2652) — Note: Adafruit's version defaults to I2C address 0x76, while generic clones often use 0x77.
• Storage: 16GB SanDisk High Endurance microSD card (Class 10, U1)
• Wiring: 4x Silicone jumper wires (26 AWG, female-to-female)
• Power: 5V/2.5A USB-C power supply (Critical: lower amperage causes Wi-Fi brownouts during MQTT transmission)

Pin Mapping Table

The BME280 operates at 3.3V logic, which perfectly matches the Pi's native GPIO levels. No logic level converter is required.

Wiring and Configuration Steps

1. Prepare the OS: Flash Raspberry Pi OS Lite (64-bit, Bookworm) onto the microSD card using the official Imager. Enable SSH and configure your Wi-Fi SSID/password in the Imager's advanced settings.
2. Enable I2C: Boot the Pi, SSH in, and run sudo raspi-config. Navigate to Interface Options > I2C and select Yes. Reboot the Pi.
3. Verify Hardware: After reboot, install the I2C tools: sudo apt install i2c-tools. Run i2cdetect -y 1. You should see 76 (or 77) in the grid output. If the grid is empty, check your SDA/SCL wiring.
4. Install Python Dependencies: Create a virtual environment to keep system packages clean.

   python3 -m venv env
   source env/bin/activate
   pip install adafruit-circuitpython-bme280 paho-mqtt

Complete Python Data Logger Code

Save the following code as logger.py. This script includes explicit pin definitions, graceful error handling for I2C bus dropouts, and MQTT connection state management.

import time
import board
import busio
import adafruit_bme280
import paho.mqtt.client as mqtt
import json

# --- PIN & HARDWARE DEFINITIONS ---
# Maps to physical Pi Pin 3 (SDA) and Pin 5 (SCL)
I2C_SDA = board.SDA
I2C_SCL = board.SCL
BME_ADDRESS = 0x76  # Change to 0x77 if using generic non-Adafruit clones

# --- MQTT CONFIGURATION ---
MQTT_BROKER = "192.168.1.100"
MQTT_PORT = 1883
MQTT_TOPIC = "environment/lab/bme280"

# --- CALLBACKS ---
def on_connect(client, userdata, flags, rc):
    if rc == 0:
        print("[MQTT] Connected to broker successfully.")
    else:
        print(f"[MQTT] Connection failed with code: {rc}")

# --- INITIALIZATION ---
client = mqtt.Client()
client.on_connect = on_connect

try:
    client.connect(MQTT_BROKER, MQTT_PORT, 60)
    client.loop_start()
except Exception as e:
    print(f"[FATAL] MQTT Connection Error: {e}")
    exit(1)

try:
    i2c = busio.I2C(I2C_SCL, I2C_SDA)
    bme280 = adafruit_bme280.Adafruit_BME280_I2C(i2c, address=BME_ADDRESS)
    bme280.sea_level_pressure = 1013.25  # Calibrate for accurate altitude
    print("[INFO] BME280 sensor initialized.")
except ValueError as e:
    print(f"[FATAL] I2C Initialization Error: {e}")
    exit(1)

# --- MAIN LOOP ---
try:
    while True:
        try:
            temp_c = bme280.temperature
            humidity = bme280.relative_humidity
            pressure = bme280.pressure
            
            payload = json.dumps({
                "temp_c": round(temp_c, 2),
                "humidity": round(humidity, 2),
                "pressure_hpa": round(pressure, 2)
            })
            
            result = client.publish(MQTT_TOPIC, payload, qos=1)
            if result.rc == mqtt.MQTT_ERR_SUCCESS:
                print(f"[TX] {payload}")
            else:
                print(f"[WARN] Publish failed, rc={result.rc}")
                
            time.sleep(10)
            
        except OSError as e:
            print(f"[ERROR] I2C Read Failure: {e}. Retrying in 5s...")
            time.sleep(5)
            # Re-initialize I2C bus on failure
            i2c = busio.I2C(I2C_SCL, I2C_SDA)
            bme280 = adafruit_bme280.Adafruit_BME280_I2C(i2c, address=BME_ADDRESS)

except KeyboardInterrupt:
    print("\n[INFO] Stopping logger...")
    client.loop_stop()
    client.disconnect()

Debugging: Fixing Common I2C and MQTT Errors

When deploying embedded Linux devices, hardware interfaces are rarely plug-and-play. Here is how to diagnose the two most common failure modes in this build.

Error 1: FileNotFoundError: [Errno 2] No such file or directory: '/dev/i2c-1'

What it means: The Linux kernel has not loaded the I2C device tree overlay, meaning the OS does not recognize the hardware bus.

Ranked Causes & Fixes:

1. I2C disabled in config: Run sudo raspi-config and re-enable I2C. Alternatively, edit /boot/firmware/config.txt and ensure dtparam=i2c_arm=on is present and uncommented.
2. Missing kernel modules: Run lsmod | grep i2c. If i2c_dev is missing, load it manually with sudo modprobe i2c-dev and add i2c-dev to /etc/modules.

Error 2: OSError: [Errno 121] Remote I/O error

What it means: The Pi's I2C controller sent a clock signal, but the sensor did not acknowledge (NACK) on the SDA line. This is a physical layer failure.

Ranked Causes & Fixes:

1. Incorrect I2C Address: You are using a generic BME280 breakout that defaults to 0x77, but the code specifies 0x76. Run i2cdetect -y 1 to confirm the address and update the BME_ADDRESS variable.
2. Missing Pull-up Resistors: I2C requires pull-up resistors on SDA and SCL. Adafruit breakouts include 4.7kΩ pull-ups. If you wired a raw BME280 chip or a cheap clone without pull-ups, the bus will float. Add 4.7kΩ resistors from SDA to 3.3V and SCL to 3.3V.
3. Wi-Fi Power Brownout: On the Pi Zero 2 W, a weak power supply causes the 3.3V voltage regulator to sag when the Wi-Fi chip transmits. This resets the I2C sensor mid-read. Upgrade to a verified 5V/2.5A supply.

Extending and Simplifying the Build

Understanding the practical uses of Raspberry Pi means knowing how to scale a project up for production or down for rapid prototyping.

How to Simplify (Local Logging)

If you do not have a network infrastructure or MQTT broker available, strip out the paho-mqtt library entirely. Replace the MQTT publish block with standard Python file I/O to append the JSON payload to a local CSV file on the SD card. To prevent SD card wear from constant write cycles, buffer 100 readings in RAM before executing a single fsync() to the disk.

How to Extend (Off-Grid LoRaWAN)

For agricultural or remote weather station uses where Wi-Fi is unavailable, swap the MQTT-over-Wi-Fi approach for LoRaWAN. Stack a Dragino LoRa/GPS HAT onto the Pi Zero 2 W. Instead of using Python, you will use the dragino Python library to send the BME280 payload as raw hex bytes over the 915MHz (US) or 868MHz (EU) ISM band to a gateway like The Things Network (TTN). This reduces power consumption dramatically and extends range to several kilometers line-of-sight.

For production deployments, ensure you wrap your Python script in a systemd service with Restart=always and RestartSec=10 to automatically recover from transient Wi-Fi dropouts or I2C bus lockups. For deeper configuration details on I2C bus speeds and baud rate adjustments, refer to the official Raspberry Pi I2C documentation. For MQTT payload structuring, consult the Eclipse Paho Python Client guide.