This guide helps hobbyists and homelab operators build reliable environmental and security sensors using commonly available hardware. You will find parts lists, wiring and integration patterns, data logging and visualization tips, and troubleshooting.
Projects at a glance
- Project 1: Temperature and humidity monitor using an ESP32 with local logging and a Graylog-friendly pipeline.
- Project 2: Raspberry Pi security alarm using PIR motion sensors and Home Assistant automations.
- Project 3: Specialty boat or mobile monitoring using NMEA-compatible environmental sensors.
A short comparison toward the end explains non-intrusive thermal/occupancy sensing as a next step for building-scale deployments.
Pick components to match your goals: ultra-cheap prototypes, mid-range reliable sensors, or commercial-grade replacements for long-term use.
Sensors
- Budget: DHT22 (temperature + humidity) — cheap and easy, okay for hobby logging.
- Reliable: BME280 or SHT35 — better accuracy, long-term stability, and pressure sensing in some models.
- Motion: standard PIR modules — simple occupancy detection for alarms.
- Thermal/occupancy: small thermal/IR sensors or arrays for presence detection (non-identifying heat maps).
- Specialty: NMEA-capable sensors or adapters for boats and vehicles.
Controllers
- Budget/maker: ESP32 variants — Wi‑Fi, inexpensive, plenty of community firmware options.
- Hub/edge: Raspberry Pi 4/5 — handles local aggregation, Home Assistant, or Graylog forwarding.
Power & connectivity
- Power: 5 V USB supplies for ESP32 and RPi; consider PoE for Raspberry Pi with compatible HATs.
- Backup: small UPS for Raspberry Pi if logging must survive power outages.
- Networking: reliable Wi‑Fi, or wired Ethernet for fixed hubs.
Tools
- Breadboard or small prototyping PCBs, wire kit, multimeter, soldering iron for final builds.
Budget tiers
- Starter build: ESP32 + DHT22 + USB power (minimal cost).
- Reliable homelab node: ESP32 + BME280 with enclosure + local MQTT broker on Raspberry Pi.
- Production-like: wired sensors with PoE or battery-backed gateways and enterprise dashboards.
Goal
Reliable environmental logging with local retention and easy dashboarding.
Hardware and placement
- Use an ESP32 module paired with a BME280 for improved accuracy. Place sensor away from direct heat sources and vents.
- Enclose sensors in ventilated housings to reduce radiative bias.
Bootstrapping and firmware steps (high level)
- Install a firmware option that supports MQTT or HTTP posting and sensor drivers; many community firmwares are available for ESP32 platforms.
- Configure the device to publish sensor samples at a sensible cadence (1–5 minutes typical for temperature logging).
- Use retained messages or small local buffering on the device when connectivity drops.
Local ingestion and Graylog
- Run a local ingestion pipeline: collect sensor messages with an MQTT broker or direct HTTP collector on a Raspberry Pi. From there, forward to Graylog or write to a local time-series DB.
- In Graylog, create streams and dashboards with fields for temperature, humidity, and device metadata. Keep sample sizes and retention tuned to your storage.
Dashboard and alerts
- Visualize rolling averages and set threshold-based alerts for critical devices like freezers. Use local notifications (email or push via an automation hub) to avoid cloud dependency.
Maintenance tips
- Calibrate sensors against a trusted reference before long-term logging.
- Record metadata: location, mounting height, and last calibration date.