How ersabby/webserver works
The project collects DHT11 readings through an ESP32 and MQTT, then offers two visible server-side paths: a Flask page backed by SQLite, and a Node MQTT subscriber that stores messages in MySQL. The README establishes the sensor-to-MQTT product workflow; the excerpts show the server-side subscriptions, persistence and page rendering. The Grafana directory contains no shown dashboard code, so it is represented only by the evidenced Node ingestion and storage behavior.
Main entry points: code.py Flask MQTT and web app · index.js MQTT subscriber · esp32_DHT11.ino ESP32 firmware · sensordata.db Sensor readings
Components 9
Sensing device
- DHT11 sensor
- ESP32 firmware
webserver/esp32_DHT11.ino
Flask service
- Flask MQTT and web app
webserver/DHT-server/code.py - Sensor readings
webserver/DHT-server/sensordata.db - Readings page
webserver/DHT-server/templates/main.html
Node ingestion
- MQTT subscriber
webserver/Grafana/index.js - MySQL messages
Other components
- Web user
- MQTT broker
Connections 11
- DHT11 sensor → ESP32 firmware: provides readings
README.md - ESP32 firmware → MQTT broker: publishes readings
README.md - Flask MQTT and web app → MQTT broker: subscribes to dht
webserver/DHT-server/code.py - MQTT broker → Flask MQTT and web app: delivers messages
webserver/DHT-server/code.py - Flask MQTT and web app → Sensor readings: writes readings
webserver/DHT-server/code.py - Web user → Flask MQTT and web app: requests page
webserver/DHT-server/code.py - Flask MQTT and web app → Sensor readings: reads latest
webserver/DHT-server/code.py - Flask MQTT and web app → Readings page: renders readings
webserver/DHT-server/code.py - MQTT subscriber → MQTT broker: subscribes to dht
webserver/Grafana/index.js - MQTT broker → MQTT subscriber: delivers messages
webserver/Grafana/index.js - MQTT subscriber → MySQL messages: inserts messages
webserver/Grafana/index.js