Files
memory/systems/homeassistant.md
T
2026-10-07 22:00:57 +00:00

4.3 KiB
Raw Blame History

title, category, tags, created, modified
title category tags created modified
Home Assistant systems
homeassistant
smart-home
mqtt
automation
2026-09-27 2026-09-27

Home Assistant

Smart Home Zentrale auf Proxmox. Steuerung, Automatisierung und Benachrichtigungen.

Infrastruktur

  • Host: 10.0.30.10 (HAOS VM)
  • SSH: hassio@10.0.30.10 (PW: 1P Vault "Hermes")
  • URL: https://homeassistant.familie-schoen.com
  • Container: homeassistant (Docker)

MQTT

  • Broker: Mosquitto Add-on v7.1.1 auf localhost:1883
  • HA MQTT User: ehemals opendtu (BROKEN — ACL blockiert), gefixt
  • ACL: /etc/mosquitto/acl definiert user homeassistant + user addons
  • Auth Plugin: go-auth.so (files,http backends)

Automations

  • File: /config/automations.yaml (35 Automations)
  • Schreibmethode: SSH → docker exec homeassistant chmod 666, danach restore 644
  • Reload: REST API mit JWT (HS256, signed from /config/.storage/auth)

Frigate Einfahrt Notification (ID 1714065780832)

  • MQTT trigger frigate/events → filter type=='new' + cameras [Einfahrt,Terrasse] + labels [person,car,...]
  • Mode: single, cooldown 600s
  • Dedup: input_text.frigate_last_event_id
  • Flow: delay 10s → snapshot → notify iPhone → optional LLM Vision
  • Siehe systems/frigate

Notify Services

Service Status
notify.mobile_app_iphone_dominik ✅ aktiv
notify.mobile_app_sarahs_iphone_app verfügbar
notify.mobile_app_ipad_2 verfügbar
notify.mobile_app_sm_x205 verfügbar

Entitäten

  • Kameras: camera.einfahrt_2, camera.terrasse_2 (Suffix _2 wegen verwaister Integration)
  • Motion: binary_sensor.einfahrt_motion_2, binary_sensor.terrasse_motion_2
  • Input Text: input_text.frigate_last_event_id (dedup storage, max 255 chars)

Snapshots

  • Gespeichert: /config/www/snapshots/{camera}_latest.jpg
  • URL: /local/snapshots/ (HTTP 200, keine Auth)

JWT Auth

  1. jwt_key aus /config/.storage/auth lesen
  2. Client Hermes_202606 (token id 1444b2c6757b4d66a6f8f8e5899b4e6a)
  3. HS256 signieren, Bearer Header
  4. ?return_response=true für Service-Call Responses

Integrations

  • Frigate (MQTT)
  • LLM Vision (noris AI gemma-4-31b-it)
  • Tibber (Strom)
  • Marstek Speicher (VENUS-E, IP 10.0.50.113)
  • NUT (APC Back-UPS ES 700G via ms-a2-1, 10.0.20.92:3493, User monuser; Sensors sensor.apc_*; Entry 5e1d2138235140eb9b476e9d6779c228; deployed via iac-homelab/epic-9-ups-nut)
  • Various sensors (Xiaomi BLE, etc.)

EMHASS Batteriesteuerung

  • Endpoint: http://10.0.30.10:5000 (v0.18.4)
  • Architektur: EMHASS = Sole Optimizer. Virtuelle 16 kWh Batterie (BYD 11k + Marstek 5k).
  • Config API: POST /set-config überschreibt GESAMTE Konfig (kein Partial-Update!). Immer alle Felder senden. Siehe Solution Doc integrations/2026-10-02-emhass-set-config-overwrite-pitfall.md.
  • Akuelle Config (2026-10-02):
    • Capacity 16000Wh, Charge/Discharge 6700W, Efficiency 0.9
    • Target SoC 0.15 (15%), Min SoC 0.1, Max SoC 1.0
    • set_battery_dynamic: True, set_use_battery: True
    • SoC sensor: sensor.total_soc, Power sensor: sensor.batteries_power_out_total
  • Kaskaden-Automation (1774430238377, ON): EMHASS target → BYD (803 Auto default, 802 bei target<=0 && pv<100) + Marstek (Rest via sensor.marstek_target_power)
  • Template Sensoren: sensor.smart_battery_target (EMHASS), sensor.marstek_target_power (Plan A: smart_target − actual_BYD_discharge). sensor.sma_target_power ENTFERNT (Double-Counting Bug).
  • Cron: a32005d62226 (no_agent, every 15m, runner script) ruft EMHASS Optimization auf.
  • Backup: .bak.20261001_175804 für configuration.yaml + automations.yaml
  • NFS-Backups (Fix 2026-10-07): Supervisor-Mounts Backup_NFS (usage=backup) + Medien_NFS (usage=media) → 10.0.20.100:/pool01_n2_redundant/HomeAssistant (vorher tote 10.0.30.100, verloren beim NAS-Crash-Reboot 03.10.). Volle automatische Backups ~03:27 UTC nightly. Monitoring: Hermes-Cron 2006a91fba21 (Alert bei Backup-Alter >30h). Lösungsdoku: docs/solutions/bug-fixes/2026-10-07-ha-audit-nfs-mount-failure-after-nas-crash.md