docs(handoff): nest-temp question pivoted to standalone nest-alert project — no POS changes

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 14:13:27 -04:00
parent 1dfe8dadc2
commit ce9438f5f5
1 changed files with 61 additions and 0 deletions
@@ -0,0 +1,61 @@
+# Handoff: Nest-temp question pivoted out — nothing changed in POS-Automation
+
+## Session Metadata
+- Created: 2026-07-17 14:12
+- Project: /home/claude/bin/POS-Automation
+- Branch: master
+- Session duration: one evening (2026-07-16)
+
+### Recent Commits (for context)
+  - 1dfe8da docs: session handoff — Google Home print button (complete)
+  - 93f6c33 feat: simplify Google switch to on-only (state push restored)
+
+## Handoff Chain
+
+- **Continues from**: 2026-06-11-045021-pos-google-home-button.md
+- **Supersedes**: nothing — the 2026-06-11 handoff remains the authoritative
+  state of the POS briefing feature (complete, live).
+
+## Current State Summary
+
+**No POS-Automation code, config, or deployment changed this session.**
+
+The session started here with "does the Google Home integration allow exposure
+of the Nest thermostat temperatures?" — initially assumed to be a
+receipt-printing feature. Seth then clarified he doesn't use HA for this and
+wanted **SMS alerts when the temp goes out of range**, which is not POS scope.
+The work spun off into a new standalone project:
+
+→ **`~/bin/nest-alert/`** — SDM API poller (5-min systemd timer on steel141)
+  that texts Seth via the hola-bot Twilio number when the Nest thermostat
+  leaves 60–80°F. Live and verified. See its CLAUDE.md, DECISIONS.md, and
+  `.claude/handoffs/2026-07-16-nest-alert-live.md` for everything (Device
+  Access project, OAuth saga, known SDM limits).
+
+## Important Context
+
+- The POS briefing pipeline (Google Home switch → MQTT → printer) is
+  untouched and was working as of 2026-06-11. Do not conflate the
+  `google_assistant` integration on the HA VM (push-only, POS button) with
+  the new SDM/Device-Access setup (pull, nest-alert project) — they are
+  separate Google surfaces and separate GCP projects.
+- If a future session wants Nest temperature **on the printed receipt**, the
+  lazy path is importing `read_temps_f`/`access_token` from
+  `/home/claude/bin/nest-alert/nest_alert.py` (stdlib-only, its .env already
+  has the refresh token) — not building anything new here.
+
+## Immediate Next Steps
+
+1. None for POS-Automation. Feature state is unchanged from the 2026-06-11
+   handoff; its optional deferred items (print latency, DHCP reservation,
+   dashboard None-fields, SA key rotation) still stand.
+
+## Decisions Made
+
+- Nest alerting deliberately kept **out of POS-Automation** (and out of
+  hola-bot) — recorded in `~/bin/nest-alert/DECISIONS.md`.
+
+## Potential Gotchas
+
+- None new for this repo. See the 2026-06-11 handoff's gotchas (pytest
+  rootdir pin, bridge deploy path, google_assistant 404 red herring).