Configuration

Seven areas of settings, each explained on its own page — and every parameter in one list when you only know its name.

How configuration works

You configure EOS Connect in its web UI, behind the gear icon. Settings are stored in its own database — there is no config file to hand-edit, apart from the three bootstrap keys needed before that database is open.

  • Settings marked live take effect immediately.
  • Settings marked restart need EOS Connect restarted.
  • experimental may change without notice; deprecated still works but should not be used for a new setup.

The detail level selector above is the same one the application uses, and a compact copy of it appears in the header once you scroll. Getting Started is the handful of settings a first install needs; Standard adds everyday tuning; Expert shows everything. Each level includes the ones before it. Following a "Learn more" link from inside the app carries your level across.

The seven areas

Settings are grouped the same way here as in the application. Each page carries its own parameters and the explanation of what they do, so configuring one thing does not mean reading two pages.

Data & sensors

Home Assistant or openHAB, the sensors it reads your consumption from, and the array format for anything else.

Battery & inverter

The store the optimizer plans around, the hardware it drives, and what the stored energy cost.

Prices

What a kilowatt-hour costs you, what you are paid for one, and how the far end of the horizon is filled in.

Solar forecast

Who supplies the forecast, how your roof is described, and how it is kept honest against measurement.

Optimizer

Which solver plans your battery, how finely, and the grid limits it must stay inside.

Managed loads

Pool, sauna, hot water, heating — appliances the weekday-average forecast cannot follow.

System & MQTT

Port, timezone and logging, the broker connection, and the EVCC address.

I want to…

Most questions about this page are really questions about one of these. Each goes straight to the section that answers it.

Backup and restore

Menu › Backup & Restore writes one file containing your whole install: every setting, the measured PV yield history that the forecast auto-scaler learns from, and what each managed load has learned about its appliance.

  • That history is stored nowhere else and is purged on a rolling window (7 days by default), so a backup is the only way to keep it.
  • Every load that reads a temperature learns — a pool, a sauna, a hot-water tank, a buffer tank — and that learning is the slowest thing on the install to rebuild. A heat-loss figure needs weeks of overnight cooling and a spread of weather before it means anything, and a covered store has to be seen both covered and open before the cover is worth anything to the model. Restoring takes effect at the next restart, because each load rebuilds its calibration from the recorded samples when it starts.
  • Restoring previews first — including which settings it would remove — and writes nothing until you confirm.
  • An old backup's yield history can be shifted into the current window, so auto-scaling works from the first run instead of waiting a week.
  • Each dataset has its own checkbox on both sides, so you can back up everything and restore only the part you meant to.

The backup file holds your API tokens and inverter password in plain text. Store it accordingly.

Every setting

All 173 settings in one list, for when you know a name but not where it lives. It is generated from config_schema.json, which scripts/export_config_schema.py exports from the application's own configuration schema, so it cannot fall behind the code. Each group links to the page that explains it.

Loading the parameter reference…