oskar/homelab-codex-ws
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
homelab-codex-ws/services/home-assistant/config/ken-legacy/README.md
oskar 77d55caf07 feat(ha): cutover ken to 31.7 HAOS, archive legacy container instance 
instances.yaml pointed "ken" at the piha container (homeassistant5), a
pre-migration instance that never actually stopped running — it kept
firing automations in parallel with the real home instance (HAOS on a
dedicated RPi4, 192.168.31.7), causing duplicate triggers on shared
buttons/scenes. Repoint ken to the real instance (api adapter),
demote the container to ken-legacy (archived, import-only, never a
deploy target), and log the incident in DESIGN.md.
2026-07-22 16:17:18 +02:00

1,008 B
Raw Blame History

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.