summaryrefslogtreecommitdiff
path: root/prompts/skills/f3s/references/shelly-plug.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-07-03 20:53:09 +0300
committerPaul Buetow <paul@buetow.org>2026-07-03 20:53:09 +0300
commit05e78ceccdf55dbc06ff26e7bfdfb9e2105a67b5 (patch)
tree175f9bfa2cb38f0f6945d300063264a0605531fc /prompts/skills/f3s/references/shelly-plug.md
parente7b70bca2aa5ded509ae20ebea565c48b456ad0e (diff)
sync skills: drop Rocky->NetBSD migration narrative from pi0/pi1 docs
Trims dates, "reinstalled"/"converted"/"validated twice" framing, and forward-looking "next conversion" language from the f3s/pkgrepo skill docs. Keeps only current-state reference material: pi0 and pi1 run NetBSD, and how their services (WireGuard, bozohttpd, uptimed, npf, content sync, goprecords) are installed and configured. bootstrap-netbsd-pi.md is reframed from a migration runbook into a plain service-reference doc. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'prompts/skills/f3s/references/shelly-plug.md')
-rw-r--r--prompts/skills/f3s/references/shelly-plug.md21
1 files changed, 11 insertions, 10 deletions
diff --git a/prompts/skills/f3s/references/shelly-plug.md b/prompts/skills/f3s/references/shelly-plug.md
index 6021921..b91c36d 100644
--- a/prompts/skills/f3s/references/shelly-plug.md
+++ b/prompts/skills/f3s/references/shelly-plug.md
@@ -93,16 +93,17 @@ wake via WoL when this was set up — deploy when it is back online).
`wol-f3s` (dotfiles `scripts/wol-f3s`; deployed to `/home/paul/scripts/wol-f3s`
on earth and `/usr/local/bin/wol-f3s` on pi0/pi1/pi2) controls the plug as part
-of bulk power actions. On `pi0`/`pi1` (NetBSD) this needed: pkgsrc `bash`
-(already present as a dependency of other packages) and pkgsrc `wol` installed,
-the shebang changed from `#!/bin/bash` to `#!/usr/pkg/bin/bash` on the deployed
-copy (dotfiles' own copy for earth/Linux stays as-is), `~/.shelly_plug` copied
-over (missing on a fresh image), and `/etc/hosts` entries for `f0`–`f3`/`pi2`–`pi3`
-(cross-Pi/host `.lan.buetow.org` resolution isn't reliable — same DNS gap
-noted elsewhere in this skill). End-to-end verified from `pi0` (2026-07-03):
-woke `f3` via WoL, toggled the shelly plug off/on, shut `f3` back down via
-`wol-f3s shutdown-f3` — all worked. Note single-host `wol-f3s f3`/`shutdown-f3`
-does **not** touch the shelly plug (only the bulk `all`/`shutdown-all` paths do).
+of bulk power actions. On `pi0`/`pi1` (NetBSD) this needs: pkgsrc `bash` and
+pkgsrc `wol` installed, the shebang changed from `#!/bin/bash` to
+`#!/usr/pkg/bin/bash` on the deployed copy (dotfiles' own copy for
+earth/Linux stays as-is), `~/.shelly_plug` present, and `/etc/hosts` entries
+for `f0`–`f3`/`pi2`–`pi3` (cross-Pi/host `.lan.buetow.org` resolution isn't
+reliable — same DNS gap noted elsewhere in this skill). SSH trust from
+`pi0`/`pi1` to each `fN` host is required for the shutdown path (`ssh
+paul@fN "doas poweroff"`) — note the host key must be accepted for both the
+hostname **and** the bare IP, since the script connects by IP. Single-host
+`wol-f3s <host>`/`shutdown-<host>` does **not** touch the shelly plug — only
+the bulk `all`/`shutdown-all` paths do.
- `wol-f3s` / `all` → `shelly_set true` **before** sending WoL packets (fans on).
- `wol-f3s shutdown-all` → `shelly_set false` **after** all hosts/Pis are down