mirror of https://github.com/NickoScope/nickol-knx-mcp.git synced 2026-09-29 19:31:12 +02:00

Files

T

Nikolay MiroshnichenkoandClaude Fable 5 1aea8a6d9b feat(skills): ship ha-git-backup — two-circuit HA backup ops-companion skill

Circuit 1: real git in /config (deploy key, pre-commit secret scanner,
meaningful commits). Circuit 2: age-encrypted native HA backups in GitHub
Releases with rotation and a mandatory monthly restore drill. Ships
install/sync/scan/offsite/restore scripts, HA automations/snippets,
setup + architecture + incident + runbook references, EN + RU skill docs.
README/README.ru gain an ops-companion bullet in Scenario 3;
CHANGELOG [Unreleased] Added entry (no version bump).

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

2026-07-07 22:15:44 +02:00

1.8 KiB

Raw Permalink Blame History

Restore runbook

Scenario A: a broken file/config (frequent) — Circuit 1

cd /config
git log --oneline -10                 # find the last known-good commit
git diff <sha> --stat                 # what changed
git checkout <sha> -- automations.yaml   # surgical rollback
ha core check && ha core restart

Time: minutes. If HA won't start at all — same commands via the SSH add-on (it lives independently of Core).

Scenario B: dead SD/SSD/hardware — Circuit 2

Fresh HA OS install on the new medium.
On your workstation: download the latest backup/* release from ha-config, decrypt: age -d -i age_key.txt -o restored.tar ha-backup-*.tar.age
New HA onboarding → "Restore from backup" → upload restored.tar.
After start verify: entity registry intact, auth alive, dashboards present, ESPHome nodes reconnected, zigbee/z-wave network up.
Verify Circuit 1: cd /config && git status (the repo arrives inside the backup, .git and all).

Scenario C: need a year-old config

Circuit 1: git log --before="2025-07-01" -1 → checkout the needed file from that SHA.

The monthly DRILL (1st of the month, reminder ships in automations.yaml)

The goal — prove the "Releases → age → tar" chain is alive WITHOUT a real restore:

Download the latest release.
age -d with the private key (this doubles as "the key isn't lost" check!).
tar -tf restored.tar | grep -c . — the archive reads.
tar -tf restored.tar | grep core.config_entries — .storage is inside.
date +%F > /config/.git-sync/last_drill Any step failing = an incident: fix now, not when the SSD burns.

System health metrics

sensor.git_sync_status = ok, age < 26 h
.git-sync/last_offsite — age < 8 days
.git-sync/last_drill — age < 35 days

1.8 KiB Raw Permalink Blame History