Two indoor sensors, wind compass, and stop framebuffer cache thrashing

Downstairs and upstairs are now separate readings. The station names them
backwards -- "temperature_4" is downstairs and "inside_temperature" is
upstairs -- so ha_config.h says which is which. Downstairs is the primary:
big number on the card, and it is what the furnace controls on, because it
is where people are and heat rises. Upstairs sits beside it, obviously
subordinate by size, and costs no vertical space in a layout that has none.

The anemometer came back on 2026-08-07, so wind gets its own column: a dial
whose needle points at the direction the wind is coming FROM (weather-vane
convention, matching the cardinal below it), the speed, and a 5-minute trend
arrow.

  - The needle does not animate. A spin would look better, but every animated
    frame is a redraw, and redrawing is what starves the bounce refill ISR.
  - Below 0.5 mph it shows "Calm" and draws no needle. A vane that is not
    being pushed reports whatever it last settled on, which on this station
    is a steady 0 degrees -- a confident needle pointing due north at zero
    wind. The live snapshot caught exactly that.
  - The trend is local, not HA's 10-minute average, so the window is ours to
    pick: 1-minute buckets over 5 minutes, threshold 1.5 mph.

That last point needed the trend engine to stop assuming one hour. Window,
bucket size, minimum age and threshold are now per-channel in a table, which
also removes the threshold arguments main.c was passing in.

Grid drops to 117px cells to make room, so the sun sub-line is just which
event it is and "RAIN TODAY" is "RAIN" -- both were overrunning.

On the artefacts: bounce mode is NOT a DMA read of the framebuffer. The
refill is a CPU memcpy in an ISR, which is why the driver skips the usual
write-back in draw_bitmap ("the data gets read by the CPU as well"). So the
panel streams 750KB per frame at ~44Hz through the DCache, evicting the
working set of everything else on the chip, continuously -- which is the real
reason this board is so sensitive to WiFi and to any extra rendering.
bb_invalidate_cache frees each chunk after it is copied. The header warns it
"can be dangerous if data is written from other core(s)"; that does not apply
here, because it invalidates the buffer being scanned and by design LVGL only
draws into the other one. Whether it is enough is for the panel to say.

Also gives tools/ha_snapshot.py a --token-file so the token no longer has to
travel through a shell command line to reach it.

Co-Authored-By: Claude <noreply@anthropic.com>

main/main.c

@@ -41,14 +41,6 @@ static const char *TAG = "main";
 /* Consecutive failed polls before the displayed reading is treated as stale. */
 #define STALE_AFTER_POLLS 2
 
-/*
- * Trend arrow thresholds, per hour. Below these a reading renders as flat:
- * a thermostat's indoor temp wobbles a couple of tenths continuously, and an
- * arrow that flickers on noise is worse than none.
- */
-#define TREND_TEMP_PER_HOUR_F     0.5f
-#define TREND_PRESS_PER_HOUR_INHG 0.02f
-
 /* Depth 8: a burst of taps while the network is slow should queue rather than
  * be dropped, but a user cannot meaningfully get more than a few ahead. */
 #define CMD_QUEUE_DEPTH 8
@@ -317,25 +309,31 @@ static void ha_task(void *arg)
              * lost on reboot; arrows reappear ~5 minutes later.
              */
             const uint32_t now_ms = xTaskGetTickCount() * portTICK_PERIOD_MS;
-            if (ha_data.indoor_temp_f.valid) {
-                ha_trend_feed(HA_TREND_CH_INDOOR, ha_data.indoor_temp_f.value, now_ms);
+            struct { int ch; const ha_value_t *v; } feeds[] = {
+                { HA_TREND_CH_INDOOR_DOWN, &ha_data.indoor_down_temp_f },
+                { HA_TREND_CH_INDOOR_UP,   &ha_data.indoor_up_temp_f   },
+                { HA_TREND_CH_OUTDOOR,     &ha_data.outdoor_temp_f     },
+                { HA_TREND_CH_PRESSURE,    &ha_data.pressure_inhg      },
+                { HA_TREND_CH_WIND,        &ha_data.wind_mph           },
+            };
+            for (size_t i = 0; i < sizeof(feeds) / sizeof(feeds[0]); i++) {
+                if (feeds[i].v->valid) {
+                    ha_trend_feed(feeds[i].ch, feeds[i].v->value, now_ms);
+                }
             }
-            if (ha_data.outdoor_temp_f.valid) {
-                ha_trend_feed(HA_TREND_CH_OUTDOOR, ha_data.outdoor_temp_f.value, now_ms);
-            }
-            if (ha_data.pressure_inhg.valid) {
-                ha_trend_feed(HA_TREND_CH_PRESSURE, ha_data.pressure_inhg.value, now_ms);
-            }
-            ha_data.trend_indoor =
-                ha_trend_compute(HA_TREND_CH_INDOOR, TREND_TEMP_PER_HOUR_F, now_ms);
-            ha_data.trend_outdoor =
-                ha_trend_compute(HA_TREND_CH_OUTDOOR, TREND_TEMP_PER_HOUR_F, now_ms);
-            ha_data.trend_pressure =
-                ha_trend_compute(HA_TREND_CH_PRESSURE, TREND_PRESS_PER_HOUR_INHG, now_ms);
+            ha_data.trend_indoor_down = ha_trend_compute(HA_TREND_CH_INDOOR_DOWN, now_ms);
+            ha_data.trend_indoor_up   = ha_trend_compute(HA_TREND_CH_INDOOR_UP, now_ms);
+            ha_data.trend_outdoor     = ha_trend_compute(HA_TREND_CH_OUTDOOR, now_ms);
+            ha_data.trend_pressure    = ha_trend_compute(HA_TREND_CH_PRESSURE, now_ms);
+            ha_data.trend_wind        = ha_trend_compute(HA_TREND_CH_WIND, now_ms);
 
-            /* Hand the reading to the control loop, which runs on its own
-             * task and does not care where it came from. */
-            publish_indoor_temp(&ha_data.indoor_temp_f);
+            /*
+             * Downstairs drives the furnace -- it is where people are, and
+             * heat rises, so controlling on upstairs would under-heat the
+             * living space. Change this line and the big card in ui_manager
+             * together if that ever needs to swap.
+             */
+            publish_indoor_temp(&ha_data.indoor_down_temp_f);
 
             ui_update(&ha_data);
             ui_set_stale(false);