How jake-herrera/weather-station-firmware works
This is ESP32 weather-station firmware: it connects to Wi-Fi, samples a BME280, and periodically POSTs readings to a backend. The firmware entry point coordinates these stages; the sensor and network services provide the internal acquisition and transport layers. The README documents the workflow, but the entry-point source and configuration values are not in the tree, so those orchestration links rely on README evidence.
Main entry points: weather-station-firmware.ino Firmware loop · sensor_service.cpp Sensor service · wifi_service.cpp Wi-Fi service · api_service.cpp HTTP API service
Components 9
Device orchestration
- Firmware loop
weather-station-firmware.ino - Shared config
config.h
Sensor acquisition
- Sensor service
sensor_service.cpp - Reading model
sensor_service.h - BME280 sensor
Connectivity and API
- Wi-Fi service
wifi_service.cpp - HTTP API service
api_service.cpp
Other components
- Wi-Fi network
- Weather backend
Connections 10
- Firmware loop → Wi-Fi service: connects through
README.md - Firmware loop → Sensor service: initializes and reads
README.md - Firmware loop → HTTP API service: sends readings
README.md - Firmware loop → Shared config: uses send interval
README.md - Sensor service → BME280 sensor: reads over I2C
sensor_service.cpp - Sensor service → Reading model: produces
sensor_service.cpp - Wi-Fi service → Shared config: reads credentials
wifi_service.cpp - Wi-Fi service → Wi-Fi network: connects to
README.md - HTTP API service → Shared config: reads endpoint and ID
api_service.cpp - HTTP API service → Weather backend: POSTs reading
README.md