MeteoHub - v1.63.1

MeteoHub 1.63.1

• History clear job: the batch erase (ClearJob) never gave up when the SD card refused file removals, because the budget decreased even when remove() failed, so the "no progress" guard never fired and the erase looped on every loop() turn. Progress is now the count of successful removals; after 20 consecutive passes without any, the job aborts with a clear error log and leaves a consistent state (a new clear request restarts from scratch). No file format change. New native test with a card that refuses removals.

MeteoHub - v1.61.2

MeteoHub 1.61.2

• Feed the task watchdog while /api/battery reads the monthly battery CSV files on the SD card. A long range (several months) ran inside the async_tcp task without yielding and could trigger a TASK_WDT reboot.

MeteoHub - v1.61.1

MeteoHub 1.61.1

• data/graph_config.js claimed to be "generated automatically at build time". No script produces it: it is a static file edited by hand. The stale comment is replaced by an accurate one (the minifier strips comments, so the embedded page is unchanged).

MeteoHub - v1.60.2

MeteoHub 1.60.2

• The probe firmware is removed from the hub automatically as soon as a live frame reports exactly that version (the update is done). The "Retirer" button stays for cancelling an offer that is still pending.

MeteoHub - v1.59.1

MeteoHub 1.59.1

• Humidity is now shown and served with one decimal everywhere: dashboard, history charts and tooltips, statistics, trend and synthesis tables, system page, and the /api JSON (stats, history, long-term buckets). It was rounded to a whole number. The probe sends full-precision floats and the DHT22 (now the probe's temperature and humidity reference) resolves 0.1 %. Stored data is unchanged.
• The humidity trend threshold in the synthesis goes from 0.5 to 0.1. The OLED keeps whole percents.

MeteoHub - v1.59.0

MeteoHub 1.59.0

• Battery history of the sensor. Every NEW measurement of the associated sensor (live or caught up, at its measurement time, never a duplicate) is archived on the SD card in /history/battery/YYYY-MM.csv (ts,volts,pct, ~200 KB per month). Kept apart from the weather history on purpose: its binary format is read by morfAnalytics and the battery is not a weather measurement. No SD: nothing archived (one warning); "clear history" does not erase it.
• GET /api/battery?days=N (7 by default, 365 max): points averaged into buckets (<= ~400 points, bucket >= 5 min), so a 90-day query stays light on the ESP32 and the browser.
• System page: "Battery of the sensor" card, voltage curve over 24 h / 7 d / 30 d / 90 d (plain SVG, no library).

MeteoHub - v1.57.1

Source release for MeteoHub 1.57.1.

MeteoHub - v1.57.0

MeteoHub 1.57.0

• History page charts now match morfAnalytics (Weather > Graphs): same filters (metric checkboxes, source, 6 h to 30 j periods, free period with day + hour, discarded points), same colors (temperature, humidity, pressure, OUT/IN), same scales (dynamic min/max + 8 % margin, first metric on the left axis, others on the right, IN thinner and faded), same hover tooltip. Chart.js (CDN) is gone: the chart is plain SVG, so the page no longer needs Internet access.
• The fixed/dynamic/mixed scale selector and the zoom slider are removed (the scale is always dynamic, as in morfAnalytics).
• Isolated spikes are shown as grey crosses instead of silently dropped.

MeteoHub - v1.56.7

MeteoHub 1.56.7

• Build environments renamed with a hub- prefix: esp32-s3-supermini -> hub-supermini, esp32-s3-oled -> hub-oled, esp32-s3-oled-test -> hub-oled-test. MeteoHubSensor now uses sonde-supermini: both projects target a Super Mini, and a shared env name led to flashing the hub firmware onto the probe board (two hubs on the network, same mDNS name and MH-NOW SoftAP). Build with pio run -e hub-supermini. morfproject.json env values follow; the target keys (esp32s3-supermini-ota...) are unchanged, so release asset names do not change.
• Docs, README (en/fr), CONTRIBUTING and header comments updated to the new names.

MeteoHub - v1.56.6

MeteoHub 1.56.6

• Documentation only: the 1.x entry below blamed the registry for resolving an unpinned espressif32 to a Tasmota fork. Wrong. The official registry (platformio/espressif32, tier "official") resolves it to 7.1.3 with the official core (checked). The switch to pioarduino/Tasmota happened through a PlatformIO core contaminated on 2026-10-01 (exact trigger not proven; a project pointing at a pioarduino URL is the likely candidate). The pin stays, for reproducibility.