DriMon — Drivhus Monitor

Greenhouse monitoring system for Rødtangen, Norway. ESP32 in the greenhouse posts sensor data every 5–15 min to ThingSpeak, a MATLAB scraper adds external weather from MET.no, and a web dashboard renders it all.

Live site: https://drimon.rodland.no/

The ESP32 sits inaccessible in a greenhouse: no serial monitor, no debugger, no live console. Every runtime signal has to be packed into the ≤255-byte ThingSpeak status string that rides on every POST.

Status page decodes those strings into a browsable dashboard:

• Per-day range charts for WiFi connect time, measure time, post time, total wake time, battery voltage (min / median / p95 / max)
• Daily WiFi-outcome stack (HIT / FBK / MISS / FAIL) and per-day HTTP-outcome bars per channel
• Distributions over the whole window: WiFi cache-hit rate, per-channel HTTP outcomes with a FEIL bucket for silent (all-3-fail) wakes, per-channel retry rescue rate, light/window/temp/battery/pressure class breakdowns, mesh-node BSSID resolution to friendly names
• Recent statuses table with row-click-to-copy raw string, anomaly rows tinted amber, per-channel retry +1/+2 superscripts on HTTP codes
• Top-of-page summary tiles for cold-boot count, silent-post-fail count, retries used, HTTP OK-rate, WT/TU/Post/Total time p50/p95, and more

Full historical post-mortem debugging from any browser — no infrastructure, no logs to rotate, no server-side database. See QUICK_REFERENCE.md for the exact meaning of each token in the status string.

Start here depending on what you need:

• Quick Reference — LED codes, buttons, status field decoder. Print-friendly, stick on the enclosure.
• URL Parameters — every query-string the live site accepts, with examples.
• Architecture — how ESP32 → ThingSpeak → MATLAB → dashboard connect. Data-flow diagram + per-channel field maps.
• Hardware — components, sensors, PCB, power budget, Li-Ion voltage table.
• Telemetry — querying and analyzing the ThingSpeak status field (jq/curl pipelines).
• Development Guide — webapp architecture and code organization.
• Future Enhancements — planned and completed items.
• Solar Charging Debug — historical incident notes.

Open source under the terms in LICENSE.