How to Create a Weather Station with Raspberry Pi Using BME280 and MQTT

To learn how to create a weather station with Raspberry Pi, you need three core elements: a reliable single-board computer, a hardware-I2C environmental sensor, and a lightweight messaging protocol to log the data. This guide targets the Raspberry Pi 4 Model B (4GB variant) running Raspberry Pi OS (Bookworm 64-bit). We will interface a Bosch BME280 sensor to read temperature, humidity, and barometric pressure, and push that telemetry to an MQTT broker using Python.

Hardware Spec Sheet & Parts List

Generic sensor clones often cause I2C address conflicts and lack proper pull-up resistors. The bill of materials below specifies exact variants to ensure bench-level reliability.

Pin Mapping & Physical Wiring

The BME280 communicates via I2C. We will use the Raspberry Pi's primary hardware I2C bus (I2C1). Do not use software-bit-banged I2C for environmental logging; OS thread scheduling delays will cause dropped reads.

1. De-energize the Pi: Disconnect the USB-C power supply before wiring the GPIO header.
2. Connect the I2C Lines: Map SDA to Pin 3 and SCL to Pin 5. Double-check these; swapping them won't fry the board, but it will halt communication.
3. Enable I2C in OS: Boot the Pi, open the terminal, and run sudo raspi-config. Navigate to Interface Options > I2C and enable it. Reboot.
4. Verify Hardware Address: Run sudo i2cdetect -y 1. You should see 77 in the grid (Adafruit breakouts default to 0x77; cheap clones often show 76).

Python MQTT Code with Error Handling

This script uses the adafruit-circuitpython-bme280 library for sensor abstraction and paho-mqtt for telemetry. Note: This code is written for Paho MQTT v2.0+, which changed the on_connect callback signature. Using v1.x syntax will throw a TypeError in current environments.

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

# --- PIN DEFINITIONS (BCM mapping via Blinka) ---
# SDA maps to GPIO 2 (Physical Pin 3)
# SCL maps to GPIO 3 (Physical Pin 5)
I2C_SDA = board.SDA
I2C_SCL = board.SCL

# --- NETWORK CONFIGURATION ---
MQTT_BROKER = "192.168.1.100"  # Replace with your Mosquitto broker IP
MQTT_PORT = 1883
MQTT_TOPIC = "home/weather/outside"

# Paho MQTT 2.0+ Callback Signature (includes reason_code and properties)
def on_connect(client, userdata, flags, reason_code, properties):
    if reason_code == 0:
        print("[MQTT] Connected to Broker successfully.")
    else:
        print(f"[MQTT] Connection failed with reason code: {reason_code}")

# --- SENSOR INITIALIZATION ---
try:
    i2c = busio.I2C(I2C_SCL, I2C_SDA)
    # Adafruit breakouts use 0x77. Change to 0x76 if using generic clones.
    bme280 = adafruit_bme280.Adafruit_BME280_I2C(i2c, address=0x77)
    # Set oversampling to reduce noise without oversaturating the I2C bus
    bme280.oversampling_humidity = adafruit_bme280.OVERSAMPLING_X2
    bme280.oversampling_temperature = adafruit_bme280.OVERSAMPLING_X2
    print("[SENSOR] BME280 initialized on I2C bus 1.")
except ValueError as e:
    print(f"[FATAL] I2C Init Error: {e}")
    exit(1)
except OSError as e:
    print(f"[FATAL] I2C Bus Error: {e}. Is I2C enabled in raspi-config?")
    exit(1)

# --- MQTT CLIENT SETUP ---
client = mqtt.Client(mqtt.CallbackAPIVersion.VERSION2)
client.on_connect = on_connect

try:
    client.connect(MQTT_BROKER, MQTT_PORT, 60)
    client.loop_start()  # Runs network loop in a background thread
except Exception as e:
    print(f"[FATAL] MQTT Connection Error: {e}")
    exit(1)

# --- MAIN TELEMETRY LOOP ---
try:
    while True:
        try:
            payload = {
                "temp_c": round(bme280.temperature, 2),
                "humidity": round(bme280.humidity, 2),
                "pressure_hpa": round(bme280.pressure, 2),
                "altitude_m": round(bme280.altitude, 1)
            }
            # QoS 1 ensures delivery to the broker at least once
            client.publish(MQTT_TOPIC, json.dumps(payload), qos=1)
            print(f"[TX] Published: {payload}")
            time.sleep(60)  # 1-minute sample rate prevents sensor self-heating
        except Exception as e:
            print(f"[ERROR] Read/Publish fault: {e}. Retrying in 10s...")
            time.sleep(10)
except KeyboardInterrupt:
    print("\n[SYSTEM] Halting telemetry loop.")
    client.loop_stop()
    client.disconnect()

Debugging: First Three Things to Check When It Fails

When deploying embedded I2C sensors on a multitasking OS like Linux, hardware faults manifest as specific Python exceptions. Here are the exact error strings and how to fix them.

1. ValueError: No I2C device at address: 0x77

Ranked Causes:

1. Clone Address Mismatch: You are using a generic eBay/Amazon BME280 breakout. These often tie the SDO pin to GND, shifting the address to 0x76. Fix: Change address=0x77 to address=0x76 in the Python script.
2. Missing Pull-ups: Your breakout board lacks onboard I2C pull-up resistors, and the Pi's internal pull-ups are too weak for the bus capacitance. Fix: Solder 4.7kΩ resistors between SDA/VCC and SCL/VCC.

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

Ranked Causes:

1. I2C Not Enabled: You skipped the raspi-config step. Fix: Run sudo raspi-config, enable I2C, and reboot.
2. Loose Breadboard Contact: Female-to-female jumpers on cheap breadboards often lose tension. Fix: Squeeze the female connector ends with pliers or solder the header directly.
3. Baud Rate Too High: The Pi defaults to 100kHz I2C clock. If wiring is long (>30cm), signal edges degrade. Fix: Add dtparam=i2c_baudrate=50000 to /boot/firmware/config.txt to halve the speed.

3. ConnectionRefusedError: [Errno 111] Connection refused

Ranked Causes:

1. Broker Offline: Mosquitto isn't running on the target IP. Fix: SSH into the broker and run sudo systemctl status mosquitto.
2. Firewall Block: UFW or iptables is blocking port 1883. Fix: Run sudo ufw allow 1883/tcp on the broker machine.

Extending vs. Simplifying the Build

Depending on your deployment environment, you may need to scale this architecture up for commercial-grade logging or down for low-power off-grid use.

FAQ: Long-Tail Weather Station Questions

How to create a weather station with Raspberry Pi without WiFi?

If your deployment site lacks WiFi (e.g., a remote agricultural field), you have two reliable alternatives. First, use a LoRaWAN HAT (like the Dragino LoRa/GPS HAT) to transmit small JSON payloads over several kilometers to a gateway. Second, use a wired Ethernet connection with a PoE (Power over Ethernet) splitter, which provides both network backhaul and power over a single CAT6 cable, completely eliminating the need for local power supplies and WiFi antennas.

Why is my Raspberry Pi weather station reading higher temperatures than reality?

This is the most common physics-related failure in Pi weather builds. The Raspberry Pi 4 CPU generates significant heat (often idling at 45°C+). If your BME280 sensor is mounted in the same enclosure as the Pi, or directly above it on a short breadboard, the sensor will read the Pi's thermal exhaust, not the ambient air. The fix: Mount the BME280 outside the main enclosure inside a louvered Stevenson screen, connected via a shielded 4-core cable, ensuring at least 1 meter of physical separation from the Pi's CPU heat sink.

Can I use a DHT22 instead of a BME280 for this Raspberry Pi weather station?

While physically possible, it is highly discouraged for Linux-based systems. The DHT22 uses a proprietary one-wire protocol that requires precise microsecond bit-banging. Because Raspberry Pi OS is not a real-time operating system (RTOS), background tasks (like cron jobs, network polling, or logging) will interrupt the CPU, causing the DHT22 timing to fail and returning None or checksum errors. The BME280 uses hardware I2C, meaning the Pi's dedicated I2C peripheral handles the timing independently of the main CPU threads, guaranteeing reliable reads regardless of OS load.