The Backbone

The Hub

home assistant on kara · shared box, good fences

• Good-neighbor rules on the shared hub: own Postgres database and role, resource limits on every container, HA alone on host networking (Sonos and ESPHome discovery need it).
• Z2M over ZHA because it runs as its own process — a busy hub can't stall the Zigbee mesh.
• Coordinator value tier: the Sonoff ZBDongle-E (~$20) — same chip family, but USB, which drags the passthrough problem back onto the shared box. Worth it only as a spare; the PoE unit is the pick for a reason.
• kara housekeeping: a DHCP reservation (its IP wandered after the July outages), and Ethernet instead of WiFi when the attic run happens — an alert-critical box shouldn't ride wireless forever.
• ◆ decided Off-box backup: the HA backup, the Zigbee coordinator's network key, and the compose files get pushed nightly (restic/rsync) to a second machine. Free. A dead disk must never mean re-pairing 30 devices or losing the alert pipeline.
• Thread/Matter: skipped, and the framing changed — Zigbee smoke/CO listeners already exist as the supplement layer (see Resilience), so there's no more waiting on Matter for smoke/CO. Thread stays skipped everywhere else.

The Network

all fiber, no copper · wired APs, not mesh

• ◆ decided Presence, named: UniFi's own client presence detection is the arrival mechanism the exterior lights' "arrive-home" idea was always assuming — free once the network lands, no separate sensor needed.

Energy & the Fun Radio

measure the house · hear the neighborhood

• Emporia Vue 3 (~$170) on the panel — whole-house plus per-circuit, including the future mini-split run. One decision before install: stock cloud polling, or the community ESPHome reflash for full local (voids warranty). Given the local-first rule, the reflash is on-brand; decide with eyes open.
• ThirdReality Zigbee plugs (~$12–15) where device-level truth matters — they meter, they repeat the mesh, and one of them is already assigned: the radon fan's health monitor (Resilience).
• RTL-SDR Blog V4 (~$35) — one dongle, two hobbies: ADS-B flight tracking with the antenna already owned, and rtl_433 passively hearing every cheap 433MHz sensor and half the neighborhood's weather stations. The plane-overhead announcer (SDR → Ollama → Sonos) remains the wilder shelf's crown jewel — still unbuilt by anyone, per the June research.
• The mystery ESP32 (10.0.0.196): browse to it, check its MAC's device page, or serial in — cheapest identification first, reflashing decisions later.

Voice

"hey house" · mics in rooms · brains on the hub

What a home assistant looks like here, concretely: a small satellite mic per room listening for a wake word on-device (nothing streams until it hears it), piping speech to kara, where the whole pipeline runs local — Whisper for speech-to-text, a brain, Piper for the voice coming back.

• The brain is a dial, not a religion: HA's Assist handles device intents natively with no LLM at all ("lights off," "set the office to 72" — instant). Behind that, Ollama on kara (free, private, a few seconds on CPU with a small model) handles casual asks — and for the genuinely conversational layer, HA's Anthropic integration can route the hard questions to Claude. Local for commands, cloud only where it's worth it.
• The four asks, specifically: "check the weather" — answered from the Tempest's own readings, not a forecast site. "add milk to the grocery list" — HA's todo list, which the kitchen printer can tear off on demand. "log a diaper" — the flow Noctling's design notes already specify: speech → structured event → validated write into the app, tagged as voice-sourced. "play a song" — Music Assistant targets the Sonos by room name.
• Order of operations: this rides on the backbone — HA + the hub first, one satellite second, the diaper-logging bridge last (it touches Noctling, so it gets built with the same care as the app).