21 lines
1,008 B
Markdown
21 lines
1,008 B
Markdown
|
# ken-legacy — historical archive, do not deploy
|
||
|
|
|
||
|
|
This directory holds the `/config` import of the **pre-migration** Home
|
||
|
|
Assistant instance: the `homeassistant5` container on piha, wound down
|
||
|
|
2026-07. It is kept for historical reference only — e.g. recovering the
|
||
|
|
logic of an old automation — not as a live or deployable instance.
|
||
|
|
|
||
|
|
See `services/home-assistant/DESIGN.md`, "Incident log" (2026-07-22) for
|
||
|
|
why this instance exists separately from the canonical `ken` (now the
|
||
|
|
Home Assistant OS instance on the RPi4 at 192.168.31.7): this container
|
||
|
|
kept running after the real migration and was firing automations in
|
||
|
|
parallel with the real home instance until the cutover was caught and
|
||
|
|
fixed.
|
||
|
|
|
||
|
|
**Rules for humans and agents:**
|
||
|
|
- Never run `import.sh ken-legacy` expecting a deploy target — it isn't
|
||
|
|
one. `services/home-assistant/instances.yaml` marks it `status:
|
||
|
|
archived` for this reason.
|
||
|
|
- Never write back to `homeassistant5` from this directory.
|
||
|
|
- Treat everything here as read-only history.
|