# Smart Home Project — HA + Domoticz Migration

## Systems

### Home Assistant (primary, growing)
- URL: http://192.168.66.113:8123
- MCP: connected via hass-mcp
- Entity naming: snake_case
- Prefer native HA constructs over Jinja2 templates
- Always confirm before deleting automations or entities

### Domoticz (legacy, stable)
- URL: http://192.168.66.157:8080
- API: no auth required (trusted IP)
- API endpoint: http://192.168.66.157:8080/json.htm
- Full access granted — changes allowed when explicitly requested

## Migration Strategy
- Pace: slow, step by step — nothing is broken, no rush
- Approach: replicate one device/automation at a time in HA
- Before migrating anything: query Domoticz API to understand current state
- After migrating: verify HA entity works before suggesting Domoticz removal
- Keep a running log in `migration_log.md` in this directory

## Workflow Rules
- Always check both systems before suggesting changes
- Prefer additive changes (add to HA) over removing from Domoticz
- When creating automations in HA, follow existing snake_case naming
- Ask before any bulk operations
- Never delete from Domoticz without explicit confirmation, even with full access


## Energy System

### Inverter
- Model: Deye SUN-12K-SG04LP3-EU
- Integration: deye-inverter-mqtt (Docker: ghcr.io/kbialek/deye-inverter-mqtt)
- Data arrives via MQTT → HA sensors

### Battery
- Capacity: 32 kWh
- Connected to Deye inverter

### EV Charger
- Brand: OpenEVSE
- Integration: OpenEVSE HA integration

### Spot Prices
- Integration: NordPool, zone: LV
- Currency: EUR/MWh

### EMHASS
- Add-on URL: http://192.168.66.113:5000
- Config file: /config/emhass/config_emhass.yaml
- Goal: minimize electricity bill via solar self-consumption, 
  battery charge/discharge, and EV charging schedule optimization
- Do not write config_emhass.yaml until sensor discovery is complete
  and all critical entity IDs are confirmed