@mxpicture/tesla-superchargers-mate 0.1.44 → 0.1.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mxpicture/tesla-superchargers-mate",
-  "version": "0.1.44",
+  "version": "0.1.45",
   "description": "TeslaMate integration",
   "type": "module",
   "author": "MXPicture",
@@ -49,7 +49,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@mxpicture/tesla-superchargers-generated": "^0.1.44",
+    "@mxpicture/tesla-superchargers-generated": "^0.1.45",
     "postgres": "^3.4.9",
     "short-uuid": "^6.0.3",
     "zod": "^4.3.6"

package/sql/setup.sql

@@ -151,18 +151,34 @@ END $$;
 ALTER TABLE pic_pricebooks
 ADD COLUMN IF NOT EXISTS fetched_at TIMESTAMPTZ;
 
--- backfill: the current group was confirmed by the charger's last fetch (both
--- carry that fetch's uuid); a superseded group was only ever seen at its own
--- valid_since.
+-- backfill: the current group was confirmed by the charger's last fetch; a
+-- superseded group was only ever seen at its own valid_since. The current
+-- group is the one with the max valid_since — resolving it via
+-- c.last_fetch_uuid = p.last_fetch_uuid (as this first did) silently missed
+-- every charger whose uuid had drifted off its pricebooks, and those fell
+-- through to the fallback below: fetched_at = valid_since, which
+-- pic_price_bound_v then reads as "last confirmed the day the price changed"
+-- and truncates the site's history to that single day.
+-- GREATEST over COALESCE keeps fetched_at >= valid_since even if the charger
+-- row somehow predates its own current group (a zero-day interval would drop
+-- the site from the history views entirely), and covers a NULL c.fetched_at
+-- the same way COALESCE did.
 UPDATE pic_pricebooks p
 SET
-  fetched_at = COALESCE(c.fetched_at, p.valid_since)
+  fetched_at = GREATEST(c.fetched_at, p.valid_since)
 FROM
   pic_chargers c
 WHERE
   c.id = p.pic_chargers_id
-  AND c.last_fetch_uuid = p.last_fetch_uuid
-  AND p.fetched_at IS NULL;
+  AND p.fetched_at IS NULL
+  AND p.valid_since = (
+    SELECT
+      max(cur.valid_since)
+    FROM
+      pic_pricebooks cur
+    WHERE
+      cur.pic_chargers_id = p.pic_chargers_id
+  );
 
 UPDATE pic_pricebooks
 SET
@@ -174,6 +190,35 @@ ALTER TABLE pic_pricebooks
 ALTER COLUMN fetched_at
 SET NOT NULL;
 
+-- repair for databases the uuid-joined backfill above already ran on: it left
+-- every drifted charger's current group at fetched_at = valid_since, and the
+-- guard it used (fetched_at IS NULL) no longer holds, so re-running setup
+-- cannot heal them. Raise those to the charger's last contact — the value the
+-- corrected backfill would have written. Idempotent: after this runs
+-- fetched_at > valid_since, so the row no longer matches; a no-op on a fresh
+-- database (no rows) and on one that was migrated correctly (the current group
+-- already carries the charger's fetched_at). A group whose only contact really
+-- was its own creation is raised to the charger's last fetch too, which is at
+-- worst the same claim the backfill makes; the next successful re-fetch
+-- overwrites it with a real confirmation either way.
+UPDATE pic_pricebooks p
+SET
+  fetched_at = c.fetched_at
+FROM
+  pic_chargers c
+WHERE
+  c.id = p.pic_chargers_id
+  AND p.fetched_at = p.valid_since
+  AND c.fetched_at > p.fetched_at
+  AND p.valid_since = (
+    SELECT
+      max(cur.valid_since)
+    FROM
+      pic_pricebooks cur
+    WHERE
+      cur.pic_chargers_id = p.pic_chargers_id
+  );
+
 CREATE INDEX IF NOT EXISTS pic_pricebooks_loc_idx ON pic_pricebooks (pic_chargers_id);
 
 -- group lookups: current group / group at a point in time. Resolved by
@@ -660,6 +705,10 @@ SELECT
   h.start_uuid AS last_fetch_uuid,
   h.is_tou,
   h.time_zone,
+  -- how far this snapshot is actually known: its successor's valid_since, or
+  -- the last fetch that confirmed it. Carried through so a consumer can stop a
+  -- series where the knowledge stops instead of extending the last value on.
+  h."end" AS valid_until,
   EXTRACT(
     DOW
     FROM
@@ -681,6 +730,10 @@ FROM
 CREATE VIEW pic_price_history_v AS
 SELECT
   ((k.date + b.start_time) AT TIME ZONE k.time_zone) AS TIMESTAMP,
+  -- the instant this row's snapshot stops being known — see
+  -- pic_price_history_key_v. A panel drawing a step series must stop there;
+  -- carrying the last value past it claims a price nobody checked.
+  k.valid_until,
   k.pic_chargers_id,
   c.location_url_slug,
   k.last_fetch_uuid,