Bobby NoelteandClaude Opus 5.5 faf37abfe7 feat(devices): add inverter profiles
An inverter profile describes the technical data of an inverter model: its
nominal AC power, the DC→AC and AC→DC efficiency curves over the load
fraction (AC power relative to the nominal power), the AC charge power
limit of the model, whether that limit also limits PV charging, and an
optional power derating over the ambient temperature. Curves are read
linearly and clamped at their ends, so every lookup yields a value. The
packaged profile generic-hybrid has typical hybrid inverter efficiencies,
no nominal power (the inverter device has to provide it) and full power up
to 45 degC.

Inverter settings name their profile (inverter_profile, default
generic-hybrid) and hold the differences of the unit in profile_adjustment:
nominal_power_w (replaces the profile value, required for a generic
profile), max_power_w and max_ac_charge_power_w (installation limits that
can only lower; an AC charge limit of 0 disables AC charging). The
effective parameters are resolved at the ambient temperature of the
inverter, given by the new measurement key <device_id>-temperature-degc
(45 degC without a fresh value); the power derating lowers the maximum
power and the AC charge limit.

Optimization parameters are always valid: the GENETIC and GENETIC0
parameter preparation resolve the inverter with
resolve_current_operating_parameters_or_defaults, which never raises. An
unusable profile gives the generic-hybrid profile, a missing nominal power
the fallback of 10000 W, an inverter derated to zero power the parameters
at 45 degC, and no usable profile at all the profile adjustment with
constant efficiency; each is logged as error. The GENETIC inverter takes
the AC→DC efficiency curve of the profile, solved exactly on each linear
piece of the curve (about 2 % longer runs); GENETIC0 keeps constant
efficiencies and no longer replaces the configured inverters with the demo
inverter; a battery, electric vehicle or inverter that cannot be prepared
is left out of the GENETIC0 run, never replaced by a demo device.

Configurations migrate: max_power_w becomes
profile_adjustment.nominal_power_w, max_ac_charge_power_w moves into the
adjustment, an ac_to_dc_efficiency of 0 keeps AC charging disabled, and
the efficiency fields are dropped with an error log, as for batteries, so
the profile efficiencies apply. Home Assistant config paths follow.

Additional changes
- Move the curve algorithms of the battery profile into profilecurve, so
  battery and inverter profiles share them; the battery profile keeps its
  document format and classes.
- Move ProfileBaseModel, the strict base of profile documents, into
  profilestore.
- Serve inverter profiles through the profile REST API. Refuse to delete a
  profile that a configured device uses and that has no packaged profile
  to revert to (409).
- Share the measurement access of the device settings in
  devicemeasurement.
- Rename check_battery_profiles to check_device_profiles; the device
  profile check at configuration setup covers inverters, too.
- Document inverter profiles, their configuration, defaults and sharing;
  regenerate the configuration and OpenAPI documentation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Code (claude-opus-5-5)
2026-11-11 22:08:18 +01:00
2026-11-11 22:08:18 +01:00
2025-01-24 20:08:48 +01:00
2026-11-11 22:08:18 +01:00
2025-04-07 22:23:35 +02:00
2024-05-03 10:43:31 +02:00
2024-11-15 22:27:25 +01:00
2026-11-11 09:36:16 +01:00

AkkudoktorEOS AkkudoktorEOS

Build optimized energy management plans for your home automation

AkkudoktorEOS is a comprehensive solution for simulating and optimizing energy systems based on renewable sources. Optimize your photovoltaic systems, battery storage, load management, and electric vehicles while considering real-time electricity pricing.

Why use AkkudoktorEOS?

AkkudoktorEOS can be used to build energy management plans that are optimized for your specific setup of PV system, battery, electric vehicle, household load and electricity pricing. It can be integrated into home automation systems such as NodeRED, Home Assistant, EVCC.

🏘️ Community

We are an open-source community-driven project and we love to hear from you. Here are some ways to get involved:

What do people build with AkkudoktorEOS

The community uses AkkudoktorEOS to minimize grid energy consumption and to maximize the revenue from grid energy feed in with their home automation system.

Why not use AkkudoktorEOS?

AkkudoktorEOS does not control your home automation assets. It must be integrated into a home automation system. If you do not use a home automation system or you feel uncomfortable with the configuration effort needed for the integration you should better use other solutions.

Quick Start

Upgrading an existing installation?

The next release includes a substantial energy-planning update: 15-minute GENETIC plans, EV departure targets, flexible household loads, optional battery export, and better measurement and PV-forecast tools. These features are currently unreleased.

Existing Home Assistant automations, Node-RED flows and custom API clients may need changes. Devices now use stable IDs, the new optimizer reads hardware settings from EOS configuration, and incomplete forecasts or outdated battery measurements can stop a run. The legacy POST /optimize remains available with GENETIC0; the new POST /v1/optimize has a different request format. Back up your configuration and data before updating.

Read the upgrade guide and changelog before switching an existing installation.

Start with Docker

Run EOS with Docker (access dashboard at http://localhost:8504):

docker run -d \
  --name akkudoktoreos \
  -p 8503:8503 \
  -p 8504:8504 \
  -e OPENBLAS_NUM_THREADS=1 \
  -e OMP_NUM_THREADS=1 \
  -e MKL_NUM_THREADS=1 \
  -e EOS_SERVER__HOST=0.0.0.0 \
  -e EOS_SERVER__EOSDASH_HOST=0.0.0.0 \
  -e EOS_SERVER__EOSDASH_PORT=8504 \
  --ulimit nproc=65535:65535 \
  --ulimit nofile=65535:65535 \
  --security-opt seccomp=unconfined \
  akkudoktor/eos:latest

System Requirements

  • Python: 3.11 or higher
  • Architecture: amd64, aarch64 (armv8)
  • OS: Linux, Windows, macOS

Note

: Other architectures (armv6, armv7) require manual compilation of dependencies with Rust and GCC.

Installation

Home Assistant add-on

Supports aarch64 Architecture Supports amd64 Architecture

To install the Akkudoktor-EOS add-on in Home Assistant:

Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.

  1. Add the repository URL:

    In Home Assistant, go to:

    Settings → Add-ons → Add-on Store → ⋮ (top-right menu) → Repositories
    

    and enter the URL of this Git repository:

    https://github.com/Akkudoktor-EOS/EOS
    
  2. Install the add-on:

    After adding the repository, the add-on will appear in the Add-on Store. Click Install.

  3. Start the add-on:

    Once installed, click Start in the add-on panel.

  4. Access the dashboard:

    Click Open Web UI in the add-on panel.

  5. Configure EOS (optional): In the dashboard, go to:

    Config
    
  1. create docker compose file:
services:
  eos:
    image: akkudoktor/eos:latest
    container_name: akkudoktoreos
    restart: unless-stopped
    environment:
      - OPENBLAS_NUM_THREADS=1
      - OMP_NUM_THREADS=1
      - MKL_NUM_THREADS=1
      - EOS_SERVER__HOST=0.0.0.0
      - EOS_SERVER__PORT=8503
      - EOS_SERVER__EOSDASH_HOST=0.0.0.0
      - EOS_SERVER__EOSDASH_PORT=8504
      # Change this to a random secret, e.g. output of: openssl rand -hex 32
      - EOS_SERVER__EOSDASH_SESSKEY=change-me
    ports:
      - "8503:8503"   # EOS API
      - "8504:8504"   # EOSdash
    volumes:
      - ./data:/data
  1. create a .env file with the secret:
echo "EOS_SESSKEY=$(openssl rand -hex 16)" > .env
  1. pull image and start:
docker pull akkudoktor/eos:latest
docker compose up -d
  1. Access EOS:

Configuration and data are stored in ./data.

Note: The docker-compose.yaml in the repository root is intended for development (it builds the image locally and relies on the repository's .env). Use the file above if you only want to run the published image.

From Source

git clone https://github.com/Akkudoktor-EOS/EOS.git
cd EOS

Linux:

python -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/pip install -e .
.venv/bin/python -m akkudoktoreos.server.eos

Windows:

python -m venv .venv
.venv\Scripts\pip install -r requirements.txt
.venv\Scripts\pip install -e .
.venv\Scripts\python -m akkudoktoreos.server.eos

Configuration

EOS uses EOS.config.json for configuration. If the file doesn't exist, a default configuration is created automatically.

Custom Configuration Directory

export EOS_DIR=/path/to/your/config

Configuration Methods

  1. EOSdash (Recommended) - Web interface at http://localhost:8504
  2. Manual - Edit EOS.config.json directly
  3. API - Use the Server API

See the documentation for all configuration options.

Port Configuration

Default ports: 8503 (API), 8504 (Dashboard)

If running on shared systems (e.g., Synology NAS), these ports may conflict with system services. Reconfigure port mappings as needed:

docker run -p 8505:8503 -p 8506:8504 ...

API Documentation

Interactive API docs available at:

  • Swagger UI: http://localhost:8503/docs
  • OpenAPI Spec: View Online

Resources

Contributing

We welcome contributions! See CONTRIBUTING for guidelines.

Contributors

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

S
Description
This repository features an Energy Optimization System (EOS) that optimizes energy distribution, usage for batteries, heat pumps& household devices. It includes predictive models for electricity prices (planned), load forecasting& dynamic optimization to maximize energy efficiency & minimize costs. Founder Dr. Andreas Schmitz (YouTube @akkudoktor)
Readme
48 MiB
Languages
Python 98.9%
Shell 0.4%
Batchfile 0.2%
PowerShell 0.2%
Makefile 0.2%
Other 0.1%