homelab-codex-ws/services/home-assistant/config/ken-legacy/automations/1744919280479.yaml
oskar 970b8cc023 feat(ha): archival import of ken-legacy config
Read-only import of the pre-migration homeassistant5 container (piha),
per DESIGN.md phase-0 scope: 60 automations (split one-file-per-id),
5 scenes, 1 script, plus curated .storage/* export (area/entity
registries, input_boolean/input_text, lovelace dashboards).

No token at ~/.config/ha-deploy/ken-legacy.token — fixtures step
fail-softed as designed, no repo import.sh changes needed. Verified:
gitignore-excluded paths (secrets.yaml, *.db*, logs, .storage/auth*,
core.restore_state, tts/, deps/, backups/, .cloud/) correctly stripped
from the pull; three consecutive import.sh runs produced byte-identical
output under config/ken-legacy/ and storage-export/ken-legacy/
(idempotent); automation count matches the 2026-07-22 recon estimate
(~60) exactly. README.md only touched to note the import date.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-22 16:49:09 +02:00

34 lines
701 B
YAML

actions:
- device_id: 7d930a7e75050bd061e0389d60a653fe
domain: switch
entity_id: 242582c1c93c5625129c90f888499fc7
type: turn_off
alias: Turn off piplayer power
conditions:
- condition: and
conditions:
- condition: device
device_id: 7eb1d0285898a07e62fb959f3cffda68
domain: binary_sensor
entity_id: a752fc33615b016173772b2930ec8bae
for:
hours: 0
minutes: 3
seconds: 0
type: is_not_connected
- condition: state
entity_id: switch.tasmota_tasmota2_2
for:
hours: 0
minutes: 6
seconds: 0
state: 'on'
description: ''
id: '1744919280479'
mode: single
triggers:
- hours: '*'
minutes: '*'
seconds: '15'
trigger: time_pattern