EOS_connect

EOS Connect

For full documentation, guides, and configuration details, visit: https://ohAnd.github.io/EOS_connect/

---

Overview

EOS Connect is a comprehensive energy management and optimization platform. While it remains a flexible orchestration layer between your hardware and various optimization engines, it has evolved from a pure “data gateway” into a full-featured, self-contained optimization solution.

EOS Connect now ships with a built-in MILP optimizer (local_evopt) — providing a complete, high-performance energy management system out of the box. For specialized needs, it maintains its open nature by allowing connections to external backends:

• Built-in (Recommended): local_evopt — A high-performance, local optimizer based on evcc-io/optimizer.
• External: Akkudoktor EOS or EVopt.

EOS Connect fetches real-time and forecast data (solar, prices), runs the integrated optimization (or delegates it), and automatically controls your devices to maximize self-consumption and minimize grid costs.

---

Key Features

• All-in-One Optimization Solution: No external servers required for standard energy optimization.
• Privacy & Reliability: With local_evopt, all calculations happen on your device, ensuring faster response times and no dependency on external network reachability.
• Automated Energy Management: Uses real-time and forecast data into a cohesive control strategy to maximize self-consumption.
• Battery and Inverter Management: Precise charge/discharge control, grid/PV modes, and manufacturer-validated dynamic charging curves.
• Integration with Smart Home Platforms: Home Assistant (MQTT auto discovery, native inverter control via service calls), OpenHAB, EVCC, and REST APIs.
• Dynamic Web Dashboard: Live monitoring, manual overrides, and visualization of the optimization process.
• Cost Optimization: Automatic alignment with dynamic electricity prices (Tibber, smartenergy.at, EVCC, timeseries, etc.) with configurable resolution. Learn more →
• Dynamic Feed-In Pricing: Optimize battery discharge for maximum profit when export prices are favorable. Switch feed-in sources live without restart via hot reload. Supports fixed, Elpris DK, EPEX Spot, and EVCC. Learn more →
• Smart Price Prediction: Learned grid fees and taxes for accurate planning even when future prices aren’t yet available. Learn more →
• Dynamic PV Override: Intelligent discharge prevention during high solar production or intermittent clouds. Learn more →

---

How It Works

EOS Connect acts as the central brain of your energy system:

1. Data Collection: Periodically collects local consumption, battery states, and inverter data.
2. Forecasting: Fetches PV solar forecasts and upcoming energy prices for the next 48 hours.
3. Internal Optimization: The built-in optimizer processes this data locally to generate the most cost-efficient power strategy.
4. Active Control: Applies targeted commands to your devices (inverters, batteries, wallboxes) based on the calculated strategy.

All scheduling, logic, and interface management is handled by EOS Connect, providing a unified and reliable energy management experience.

Supported data sources and integrations:

• Home Assistant: MQTT publishing (dashboard, control, auto-discovery) and direct API integration for sensor/entity data collection.
• OpenHAB: MQTT publishing (dashboard, control, auto-discovery via MQTT binding) and direct API integration for item data collection.
• EVCC: Monitors and controls EV charging modes and states.
• Inverter Interfaces: Victron MultiPlus (3-phase ESS via Modbus/TCP), Fronius GEN24 (with automatic firmware detection), legacy fallback, generic Home Assistant inverter control (e.g., Marstek, Sungrow, Goodwe), and more via MQTT/web API/EVCC external inverter control.

Quick Start

Home Assistant Installation (Recommended)

1. Requirements:

   • Home Assistant (latest version recommended)
   • EOS or EVopt server (can be installed as part of the setup; see below)

2. Install EOS Connect Add-on:

   • Add the ohAnd/ha_addons repository to your Home Assistant add-on store.
   • Install the EOS Connect add-on from the store.
   • The built-in optimizer (local_evopt) works out of the box — no additional add-ons required.

3. (Optional) External optimization backend:

   • To use Akkudoktor EOS as backend, add the Duetting/ha_eos_addon or thecem/ha_eos_addon repository and install the EOS add-on.
   • To use EVopt, install thecem/hassio-evopt and make sure it is running.

4. Configure:

   • On first start, a Setup Wizard guides you through initial configuration via the web UI.
   • All settings are managed through the EOS Connect web interface — no manual editing of config files required.
   • The HA addon only handles bootstrap settings (web port, timezone, log level). All other configuration is stored in EOS Connect’s built-in database.
   • See the user-guide/configuration for full details.

5. Start & Access:

   • Start the EOS Connect add-on from the Home Assistant UI.
   • Open http://homeassistant.local:8081 (or your HA IP) to view the dashboard.

Note for Proxmox / VM Users: If the add-on crashes with a Segmentation Fault on startup, your VM might be using a generic CPU type.

• Go to your VM Settings > Hardware > Processor.
• Change Type from kvm64 (default) to host.
• Restart the VM.

This allows the add-on to correctly see and use your physical CPU’s instructions.

Note for Proxmox / local_evopt Users: If local_evopt fails with “CBC file not found” in Proxmox, force a full container rebuild:

docker rmi ghcr.io/ohand/ha-addon-eos_connect_develop_amd64:VERSION
# Then restart the addon from Home Assistant UI to pull and rebuild

Cached images may use system Python instead of the venv.

Note on SSL Certificate Verification: By default, EOS Connect validates SSL certificates when connecting to Home Assistant or OpenHAB. If you use a setup with self-signed or private CA certificates, you can disable verification in Settings → Data Source → SSL Ignore (expert level, requires restart). Only enable this in trusted private networks where you fully control the network path. Currently, EOS Connect does not support supplying custom root CA certificates — this feature is planned for future releases. For production setups, we recommend obtaining a valid certificate through Let’s Encrypt (free) or your organization’s certificate authority.

---

Other Installation Options:

• Docker, manual, and advanced setups are supported. See the docs for details.

---

Configuration

EOS Connect uses a web-based configuration system. All settings are managed through the built-in web UI at http://localhost:8081.

First Start (Setup Wizard)

On first launch, a Setup Wizard guides you through the essential configuration steps in optimal order:

1. Optimizer — Select your optimization backend (built-in Local EVopt, EOS Server, or external EVopt)
2. EVCC (Optional) — Configure if you want to use EVCC for PV forecasts, inverter control gateway, or car charging dependent control. Can be skipped if not using EVCC.
3. Inverter — Select your inverter type for battery control (display-only if not using hardware control). Can use EVCC as controller if configured in step 2.
4. Data Source — Connect to Home Assistant, OpenHAB, or use default sensors
5. Battery — Set capacity and SOC limits
6. Load — Connect your load sensor
7. Price — Choose your electricity pricing provider
8. PV Installations — Configure your solar forecast provider and PV systems (location-based sources only)

After the wizard completes, restart EOS Connect to apply the settings.

Note:

• EVCC configuration must come before Inverter so you can select EVCC as your inverter controller type. If EVCC URL is not configured, the option will be greyed out in both the Inverter and PV Source selection fields.
• PV Installations configuration is only required for location-based forecast sources (Akkudoktor, OpenMeteo, Forecast.Solar). Other sources (Default, Solcast, Victron, EVCC, Timeseries) configure their data elsewhere and do not need PV Installations defined.

Bootstrap Config (config.yaml)

Only 3 infrastructure settings live in config.yaml — everything else is stored in the database and managed via the web UI:

# config.yaml — bootstrap settings only
eos_connect_web_port: 8081  # Web server port
time_zone: Europe/Berlin    # System time zone
log_level: info             # Log level: debug, info, warning, error

Upgrading from an older version? On first start, EOS Connect automatically migrates your existing config.yaml settings into the database. After migration, you can reduce config.yaml to just the bootstrap keys above.

Changing Configuration

• Open http://localhost:8081 and click the gear icon to access the configuration page
• Changes marked as “hot-reloadable” (e.g., feed-in price, SOC limits) take effect immediately
• Other changes require a restart (the UI shows which fields need restart)

---

Troubleshooting & Advanced Configuration

For troubleshooting and advanced configuration, see the docs.

---

Support & Sponsoring

If you find this project useful and would like to support its development, please consider sponsoring: https://github.com/sponsors/ohAnd

Contributing

Contributions are welcome! See CONTRIBUTING.md for guidelines.

License

MIT License - see LICENSE for details.