Building IoT Projects with a Raspberry Pi 5: BME280 MQTT Sensor Node

When you start looking into projects with a Raspberry Pi for home automation, the jump from blinking an LED to publishing real-world sensor data over a network is where most builders hit a wall. The Raspberry Pi 5, with its new RP1 southbridge chip, handles I2C communication differently than the older BCM2711-based Pi 4. If you are wiring up environmental sensors and pushing data to an MQTT broker, you need to account for these hardware-level changes to avoid silent data drops.

This guide walks through building a headless, auto-reconnecting MQTT environmental node using a Raspberry Pi 5 and a BME280 sensor. We will cover the exact pinout, provide a production-ready Python script with robust error handling, and break down the specific I2C and network errors that plague Pi 5 builds.

Project Spec Sheet & Hardware Requirements

Bill of Materials

• Microcontroller: Raspberry Pi 5 8GB (The 4GB variant works, but 8GB is recommended if you plan to run a local Mosquitto broker and Home Assistant on the same node later).
• Sensor: Adafruit BME280 I2C/SPI Breakout (Product ID 2652). Note: Ensure you get the BME280, not the BMP280. The BMP280 lacks the humidity sensor.
• Power Supply: Official Raspberry Pi 27W USB-C Power Supply. The Pi 5 requires 5V/5A PD to prevent peripheral brownouts during I2C polling.
• Wiring: 4x Premium Female-to-Male jumper wires (28 AWG silicone jacket preferred for breadboard grip).
• Network: Active MQTT Broker (e.g., Mosquitto running on a local server or Home Assistant).

Wiring the BME280 to the Raspberry Pi 5

The Raspberry Pi 5 routes its primary I2C bus (I2C0) through the new RP1 chip. The default pull-up resistors on the Pi 5's SDA and SCL lines are 1.5kΩ, which is stronger than the Pi 4. This means the bus is generally more stable at higher speeds, but it also means you must strictly adhere to 3.3V logic levels. Feeding 5V into the SDA line will backfeed the RP1 GPIO bank and can permanently damage the southbridge.

Pin Mapping Table

1. Insert the BME280 breakout into the solderless breadboard, straddling the center trench.
2. Connect the Pi 5 Pin 1 (3V3) to the breadboard's positive power rail, and Pin 6 (GND) to the negative rail.
3. Jump the BME280 VIN to the positive rail, and GND to the negative rail.
4. Connect Pi 5 Pin 5 (SCL) directly to the BME280 SCK pin.
5. Connect Pi 5 Pin 3 (SDA) directly to the BME280 SDI pin.
6. Boot the Pi, SSH in, and run sudo raspi-config to enable the I2C interface under 'Interface Options'.
7. Verify the wiring by running i2cdetect -y 1. You should see 77 in the grid, which is the default I2C address for the Adafruit BME280.

Python MQTT Script with Error Handling

This script targets the Raspberry Pi 5 running Bookworm. We use the adafruit-circuitpython-bme280 library for sensor abstraction and paho-mqtt for network transport. Install the dependencies via your virtual environment:

pip install adafruit-circuitpython-bme280 paho-mqtt

The code below includes explicit pin definitions, exponential backoff for network reconnects, and try/except blocks to handle the exact I2C read failures common on the RP1 chip.

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

# --- Configuration ---
MQTT_BROKER = '192.168.1.100'
MQTT_PORT = 1883
MQTT_TOPIC = 'home/sensors/pi5_node1'
POLL_INTERVAL_SEC = 30

# --- Hardware Pin Definitions ---
# Using default I2C0 on the RP1 chip (GPIO 2 / SDA, GPIO 3 / SCL)
try:
    i2c = busio.I2C(board.SCL, board.SDA, frequency=100000)
    sensor = adafruit_bme280.Adafruit_BME280_I2C(i2c, address=0x77)
    sensor.sea_level_pressure = 1013.25
    print('[INFO] BME280 initialized successfully on I2C address 0x77')
except ValueError as e:
    print(f'[FATAL] Sensor not found. Check wiring and i2cdetect. Error: {e}')
    exit(1)

# --- MQTT Callbacks ---
def on_connect(client, userdata, flags, rc, properties=None):
    if rc == 0:
        print('[INFO] Connected to MQTT Broker')
    else:
        print(f'[ERROR] MQTT Connection failed with code {rc}')

def on_disconnect(client, userdata, rc, properties=None):
    print(f'[WARN] MQTT Disconnected (Code: {rc}). Attempting reconnect...')

# --- Setup MQTT Client (Paho v2.0 API) ---
client = mqtt.Client(mqtt.CallbackAPIVersion.VERSION2, client_id='Pi5_EnvNode')
client.on_connect = on_connect
client.on_disconnect = on_disconnect

try:
    client.connect(MQTT_BROKER, MQTT_PORT, keepalive=60)
    client.loop_start()
except ConnectionRefusedError as e:
    print(f'[FATAL] Cannot reach MQTT broker at {MQTT_BROKER}:{MQTT_PORT}. Error: {e}')
    exit(1)

# --- Main Telemetry Loop ---
print(f'[INFO] Starting telemetry loop. Publishing to {MQTT_TOPIC} every {POLL_INTERVAL_SEC}s')

try:
    while True:
        try:
            # Read sensor data
            temp_c = sensor.temperature
            humidity = sensor.humidity
            pressure = sensor.pressure
            
            payload = {
                'temperature_c': round(temp_c, 2),
                'humidity_pct': round(humidity, 1),
                'pressure_hpa': round(pressure, 1),
                'timestamp': int(time.time())
            }
            
            # Publish with QoS 1 to ensure delivery for home automation triggers
            result = client.publish(MQTT_TOPIC, json.dumps(payload), qos=1)
            
            if result.rc == mqtt.MQTT_ERR_SUCCESS:
                print(f'[TX] {payload}')
            else:
                print(f'[WARN] MQTT Publish failed with code {result.rc}')
                
        except OSError as e:
            # Catches RP1 I2C bus lockups or physical disconnects
            print(f'[ERROR] I2C Read Failure: {e}. Will retry next cycle.')
            
        time.sleep(POLL_INTERVAL_SEC)

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

Debugging Common I2C and MQTT Failures

When your node fails silently or crashes on boot, do not guess. Follow this diagnostic path. The first three things to check when the script fails are:

1. Run i2cdetect -y 1: If the grid is empty or shows UU, your hardware wiring is flawed, or the I2C kernel module isn't loaded.
2. Check Mosquitto Listener Binding: If the Pi is remote, ensure your MQTT broker is bound to 0.0.0.0, not just localhost.
3. Verify 3.3V Rail Under Load: Put your multimeter on the breadboard power rails while the script is running. If it drops below 3.1V, the RP1 chip will drop I2C packets.

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

Context: This exact string appears when the Python script attempts to read from the BME280, but the RP1 chip receives no ACK from the sensor.

Ranked Causes:

1. Loose Breadboard Contacts (80%): The Pi 5's 1.5kΩ pull-ups are unforgiving of high-resistance breadboard connections. Move the jumper wires to a different row or switch to a soldered perfboard.
2. Missing I2C Pull-ups (15%): If you are using a generic, unbranded BME280 clone from Amazon/AliExpress, it likely lacks onboard pull-up resistors. While the Pi 5 has internal pull-ups, long wires act as capacitors. Add external 4.7kΩ pull-ups to SDA and SCL.
3. Address Collision (5%): Another device on the bus is holding SDA low. Disconnect all other I2C devices and test the BME280 in isolation.

Error 2: ConnectionRefusedError: [Errno 111] Connection refused

Context: The Paho MQTT client attempts the initial TCP handshake on port 1883 and the remote host actively rejects it.

Ranked Causes:

1. Mosquitto Not Running: SSH into your broker and run sudo systemctl status mosquitto.
2. Listener Misconfiguration: In modern Mosquitto (v2.0+), you must explicitly define a listener. Add listener 1883 0.0.0.0 and allow_anonymous true (or configure passwords) in your mosquitto.conf.
3. UFW Firewall Blocking: If the broker is on Ubuntu, run sudo ufw allow 1883/tcp.

Extending and Simplifying the Build

Depending on your end goal, you might need to scale this project up or strip it down.

How to Simplify the Build

If you do not have an MQTT broker and just want to log data for a school project or basic analysis, drop the paho-mqtt dependency entirely. Replace the network publish block with a local CSV append operation using Python's built-in csv module. This removes all network failure modes, reduces power consumption by keeping the Wi-Fi radio in a lower power state, and allows you to run the script via a simple cron job instead of a continuous while True loop.

How to Extend the Build

To integrate this into a modern smart home, extend the MQTT payload to support Home Assistant MQTT Auto-Discovery. Instead of publishing raw JSON to a standard topic, publish a retained configuration message to homeassistant/sensor/pi5_node1/config containing the device identifiers, state topic, and value templates. Home Assistant will automatically create the entities without manual YAML configuration.

Hardware-wise, you can daisy-chain a second I2C device (like a TSL2591 light sensor) on the same bus, or utilize the Pi 5's secondary I2C bus (I2C1 on GPIO 44/45, accessible via the J5 connector) to isolate high-traffic sensors from your environmental node.

FAQ: Projects with a Raspberry Pi

What are the best beginner projects with a Raspberry Pi for home automation?

The most reliable beginner projects avoid moving parts and focus on data ingestion. Building an MQTT sensor node (like the one above), setting up a local Pi-hole DNS sinkhole, or running a Zigbee2MQTT bridge using a Sonoff Zigbee 3.0 USB Dongle Plus are the best starting points. These projects teach you Linux service management, networking, and hardware interfacing without the frustration of mechanical failures.

Can I use a Raspberry Pi Zero 2 W instead of the Pi 5 for these projects?

Yes, but with caveats. The Zero 2 W uses the older BCM2711 architecture (similar to the Pi 4). The Python code provided above will work perfectly, but the Zero 2 W has only 512MB of RAM. If you attempt to run a local Mosquitto broker and Home Assistant on the same Zero 2 W, it will thrash the swap file and corrupt your SD card. Use the Zero 2 W strictly as a headless sensor node, and offload the broker to a more powerful machine or a Pi 5.

How do I power projects with a Raspberry Pi reliably without brownouts?

The Pi 5 requires a 5V/5A (27W) USB-C Power Delivery power supply to unlock full peripheral current limits. If you use a standard 5V/3A phone charger, the firmware will restrict the downstream USB and GPIO current to prevent system instability. For embedded projects mounted in walls or ceilings, use a high-quality 5V/5A switching power supply (like a Mean Well LRS-35-5) wired to a USB-C PD trigger board. Never rely on long, thin micro-USB or cheap USB-C cables, as voltage drop over 24 AWG wire will trigger the Pi's low-voltage warning and cause I2C bus resets.