oskar/homelab-codex-ws
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
homelab-codex-ws/services/home-assistant/instances.yaml

52 lines
2.1 KiB
YAML
Raw Normal View History

feat(ha): skeleton for Home Assistant configs-as-code subproject Structure only, no deploy path: DESIGN.md decision registry (phasing, per-instance adapter, bidirectional sync with drift-abort on deploy, reload-vs-restart gating, token handling), instances.yaml (ken/piha via docker-exec, chelsty-ha via api), config/storage-export/fixtures dirs, and a read-only scripts/ha/import.sh (docker-exec adapter only) with a canonical YAML normalize+split library and an offline determinism test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-21 12:40:21 +02:00
# Home Assistant instances managed as config-as-code.
# Schema and adapter rationale: see DESIGN.md ("Deploy path: adapter per instance").
# This file is read by scripts/ha/import.sh — do not add secrets/tokens here,
# only the path to where each instance's token is expected on disk.
instances:
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
# Cutover 2026-07-22: repo previously pointed "ken" at the piha container
# (homeassistant5), but that container is a pre-migration legacy instance
# that kept running and firing automations in parallel with the real home
# instance below. See DESIGN.md, "Incident log" for the full writeup.
feat(ha): skeleton for Home Assistant configs-as-code subproject Structure only, no deploy path: DESIGN.md decision registry (phasing, per-instance adapter, bidirectional sync with drift-abort on deploy, reload-vs-restart gating, token handling), instances.yaml (ken/piha via docker-exec, chelsty-ha via api), config/storage-export/fixtures dirs, and a read-only scripts/ha/import.sh (docker-exec adapter only) with a canonical YAML normalize+split library and an offline determinism test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-21 12:40:21 +02:00
ken:
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
host: ken-haos
adapter: api
base_url: "http://192.168.31.7:8123"
token_path: ~/.config/ha-deploy/ken.token
status: active
site: ken
# Confirmed 2026-07-22: Home Assistant OS on a dedicated RPi4, LAN
# 192.168.31.7:8123, ingress ha.kapala.org via NPM. HACS installed,
# 118 automations. HAOS has no SSH access, so there is no
# docker-exec/filesystem path here — full `/config` import is deferred
# until an alternative access path exists. For now import.sh's scope
# for this instance is whatever the api adapter can reach: automations,
# scripts, scenes, dashboards.
ken-legacy:
feat(ha): skeleton for Home Assistant configs-as-code subproject Structure only, no deploy path: DESIGN.md decision registry (phasing, per-instance adapter, bidirectional sync with drift-abort on deploy, reload-vs-restart gating, token handling), instances.yaml (ken/piha via docker-exec, chelsty-ha via api), config/storage-export/fixtures dirs, and a read-only scripts/ha/import.sh (docker-exec adapter only) with a canonical YAML normalize+split library and an offline determinism test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-21 12:40:21 +02:00
host: piha
container: homeassistant5
config_mount: /home/pi/homeassistant/config
adapter: docker-exec
ssh:
user: oskar
host: piha
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
token_path: ~/.config/ha-deploy/ken-legacy.token
base_url: "http://localhost:8123" # confirmed 2026-07-22
status: archived
feat(ha): skeleton for Home Assistant configs-as-code subproject Structure only, no deploy path: DESIGN.md decision registry (phasing, per-instance adapter, bidirectional sync with drift-abort on deploy, reload-vs-restart gating, token handling), instances.yaml (ken/piha via docker-exec, chelsty-ha via api), config/storage-export/fixtures dirs, and a read-only scripts/ha/import.sh (docker-exec adapter only) with a canonical YAML normalize+split library and an offline determinism test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-21 12:40:21 +02:00
site: ken
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
# Pre-migration instance (HA 2026.4.3, location_name "KEN"), superseded
# by `ken` above (192.168.31.7). Still alive and MQTT-connected as of
# 2026-07-22 — being wound down, not deleted yet. Import is
# archival-only (historical reference); this instance is NEVER a deploy
# target. See DESIGN.md, "Incident log".
feat(ha): skeleton for Home Assistant configs-as-code subproject Structure only, no deploy path: DESIGN.md decision registry (phasing, per-instance adapter, bidirectional sync with drift-abort on deploy, reload-vs-restart gating, token handling), instances.yaml (ken/piha via docker-exec, chelsty-ha via api), config/storage-export/fixtures dirs, and a read-only scripts/ha/import.sh (docker-exec adapter only) with a canonical YAML normalize+split library and an offline determinism test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-21 12:40:21 +02:00
chelsty-ha:
host: chelsty-ha
tailscale_ip: 100.70.180.90
adapter: api
base_url: "http://100.70.180.90:8123"
token_path: ~/.config/ha-deploy/chelsty-ha.token
status: offline
site: chelsty
Reference in a new issue Copy permalink