EOS-HA

A Home Assistant custom integration for Akkudoktor EOS energy optimization.

EOS-HA uses the EOS native Home Assistant Adapter for bidirectional data exchange:

1. Configures your EOS server at startup — battery, inverter, PV arrays, price provider, devices, and adapter entity mappings
2. EOS reads entity states directly from Home Assistant — battery SOC, consumption, energy meters
3. EOS runs automatic optimization at configurable intervals (default: every hour)
4. EOS writes optimization results back as HA entities (sensor.eos_*)
5. EOS-HA wraps those results with proper entity IDs, device grouping, translations, and extra features (SG-Ready, battery price tracking, blueprints)

You keep full control — EOS-HA provides recommendations as sensor entities. You decide how to act on them with your own automations.

• Home Assistant 2024.1+
• A running Akkudoktor EOS server (addon or standalone)
• A battery SOC sensor (standard HA percentage entity, 0–100%)
• An electricity price sensor (only if using "External" price source) or a Tibber API key (from developer.tibber.com)

Tip: For the best experience, run EOS as a Home Assistant addon — the HA Adapter provides direct entity access for seamless integration.

1. Click the badge above, or go to HACS → Integrations → ⋮ → Custom repositories
2. Add https://github.com/rockinglama/eos-ha as an Integration
3. Search for EOS HA and install
4. Restart Home Assistant

1. Copy custom_components/eos_ha/ to your HA config/custom_components/ directory
2. Restart Home Assistant

1. Go to Settings → Devices & Services → EOS HA
2. Click ⋮ → Delete
3. Restart Home Assistant
4. (Optional) Uninstall via HACS or remove custom_components/eos_ha/

Add the integration via Settings → Devices & Services → + Add Integration → EOS HA.

All parameters can be changed at runtime via Settings → Devices & Services → EOS HA → Configure.

If EOS runs as a Home Assistant addon, the integration detects it via the Supervisor API and pre-fills the server URL.

The integration configures the EOS HA Adapter at startup:

EOS reads from HA:

• Battery SOC (via device_measurement_entity_ids)
• Energy meter readings: load, grid import/export, PV production (for forecast correction)

EOS writes to HA:

• sensor.eos_battery1 — battery operation mode and instructions
• sensor.eos_genetic_ac_charge_factor — AC charge schedule
• sensor.eos_genetic_dc_charge_factor — DC charge schedule
• sensor.eos_genetic_discharge_allowed_factor — discharge allowed
• sensor.eos_battery1_soc_factor — SOC forecast
• sensor.eos_costs_amt / sensor.eos_revenue_amt — costs and revenue
• sensor.eos_grid_consumption_energy_wh / sensor.eos_grid_feedin_energy_wh
• Plus battery operation mode entities for all supported modes

EOS-HA wraps these with proper unique_id, device grouping under "EOS", and translations.

Adjustable at runtime:

Trigger an immediate optimization (updates predictions then refreshes).

Override the optimization mode:

service: eos_ha.set_override
data:
  mode: charge  # charge | discharge | auto
  duration: 120  # minutes (1–1440)

Trigger EOS to recalculate all predictions without full optimization.

Override SG-Ready mode:

service: eos_ha.set_sg_ready_mode
data:
  mode: 3  # 1=Lock, 2=Normal, 3=Recommend, 4=Force
  duration: 60  # minutes (0=permanent)

Reset battery storage price tracking to zero.

Control SG-Ready heat pumps via one or two relay switches. Single-contact heat pumps (e.g. BWWPs with only a Zwangsstart relay) only need Contact 2.

The SG-Ready Mode sensor recommends a mode based on:

• PV surplus vs. configurable threshold
• Current vs. average electricity price
• Battery SOC level

The SG-Ready Auto switch automatically controls your relay entities based on the recommended mode.

Add appliances like a Brauchwasserwärmepumpe that the optimizer schedules at the cheapest time:

Multiple appliances supported, each with individual time windows. Results in the appliance_schedule sensor.

Configure a weather entity or temperature sensor for temperature-aware optimization. Falls back to 15°C if not configured. Supports:

• Weather entities (uses forecast attribute for 48h)
• Temperature sensors (uses current value for all 48h)

Tracks the weighted average cost of energy stored in the battery (EUR/kWh):

• Grid-charged energy valued at current electricity price (adjusted for efficiency)
• PV-charged energy valued at 0 EUR/kWh
• Persists across restarts (RestoreEntity)
• Reset via button or service

Four ready-to-use blueprints included in blueprints/:

All forecast sensors expose a forecast attribute with the full 48-hour array. Example with ApexCharts Card:

type: custom:apexcharts-card
series:
  - entity: sensor.eos_pv_forecast
    data_generator: |
      return entity.attributes.forecast.map((val, idx) => {
        const d = new Date();
        d.setMinutes(0, 0, 0);
        d.setHours(d.getHours() + idx);
        return [d.getTime(), val];
      });

A ready-to-use dashboard is included at dashboards/eos-energy.yaml with status, PV forecast, electricity price, battery SOC, charge plan, consumption, SG-Ready, and battery price cards.

Requires: apexcharts-card via HACS → Frontend.

Full translations available:

• 🇬🇧 English
• 🇩🇪 German (Deutsch)

Download via Settings → Devices & Services → EOS HA → ⋮ → Download Diagnostics. Sensitive data is automatically redacted.

MIT License — see LICENSE for details.