How teodroro/tr-nder-parkering works
Project type and purpose
• From the README (“Prosjekt IELS2001”) and file names it’s clear this is an IoT-enabled parking‐space monitoring system.
• ESP32-based sensors publish parking data (occupied/free) over MQTT. A Raspberry Pi (or similar) runs a Python server that subscribes to these messages, stores them in a relational database, and serves a web interface for users to log in and view parking availability.
File structure
• Top-level code for the microcontroller:
• esp32_sender.ino – Arduino sketch for the ESP32 to read sensors and publish via MQTT.
• “ESP til RSPI” and “ESP_sensordata” directories likely contain helper scripts or data payload definitions.
• Messaging backbone:
• Mqtt – Presumably MQTT broker configuration or client utilities on the Pi.
• Backend/server:
• server.py – Main Python application, probably a Flask or FastAPI app that:
• Subscribes to the MQTT broker
• Processes and persists messages
• Exposes HTTP endpoints for the web UI
• schema.sql – Database schema (tables for users, sessions, sensor readings, parking spots).
• Frontend/web UI:
• html – Static assets, templates, CSS/JS.
• login – Pages or modules for user authentication.
• startside – The home/dashboard page.
• Parkeringsplasser oversikt – Parking overview pages or modules.
• Data‐oversikt – Possibly graphs or tables for historical data.
README for additional insights
• The README only conveys the course project name; architectural details must be inferred from code and file names.
Elements
• Green for IoT/devices,
• Blue for backend services,
• Orange for data stores,
• Yellow for user interfaces.
Final advice
• Every directory/function as a component or sub-component.
• Don’t over-complicate – stick to the five to seven major blocks and their interactions.