First run

The wizard asks for the things EOS Connect cannot guess — and nothing else.

First run

On first launch a setup wizard opens and asks, in order, for the things it cannot guess. It saves only the answers it actually asked for — everything else keeps its default until you change it.

Ten screens: a welcome, the eight below, and a Review & Finish that lists what you answered and names anything a choice of yours still needs. Optional steps have a Skip button, and a skipped step saves nothing at all.

  1. Optimizer — built-in local solver, or an external EOS or EVopt server. The built-in one is preselected and needs nothing.
  2. EVCC (optional) — for PV forecasts, inverter control or car-charging-aware behaviour. Skip if you do not run it.
  3. Data source — Home Assistant, OpenHAB, or built-in defaults.
  4. Inverter — for battery control. Leave it on default for display only.
  5. Battery — capacity and charge limits.
  6. Load — your consumption sensor. Skipped automatically if no data source is connected.
  7. Price — your electricity tariff provider.
  8. PV installations — your solar forecast. Preset to a built-in demo curve so the first run finishes without your roof geometry.

Restart EOS Connect when the wizard finishes, and the dashboard starts filling in.

The Default PV source is a fixed demo curve for an assumed 4 kW array — not a forecast for your roof. It exists so you can see the system working immediately. Swap it for a real provider under Settings › PV Source once you are up.

Why the wizard asks in that order

  • EVCC and Data Source come before Inverter because either one can act as the inverter controller. Leave the EVCC URL blank and that option is greyed out later.
  • Sensor fields only appear once Data Source names Home Assistant or OpenHAB. Left unset, load and battery fall back to built-in defaults and say so in the log — they are never quietly polling a name you did not choose.
  • Every sensor field has a Test button that reads the entity and shows its current value, so a typo surfaces before you restart.
  • PV installations only matter for location-based forecast providers (Akkudoktor, Open-Meteo, Forecast.Solar). Solcast, Victron, EVCC and Timeseries get their data elsewhere.
  • A few choices need a setting the wizard does not ask for, because it is not a getting-started field. The Review & Finish step lists anything still outstanding.

The wizard is the Getting Started level

EOS Connect sorts every setting into three levels, and the selector at the top of the settings dialog — and of these pages — is what chooses between them. They are cumulative: each one includes the ones before it.

Getting Started

The handful a first install cannot run without. This is exactly what the wizard asks — nothing more, and only for the eight areas below.

Standard

Everyday tuning. Efficiencies, allowed windows, price adders, the MQTT broker — things worth setting once you are running.

Expert

Everything else: solver limits, learned coefficients, timeouts. Sensible defaults, and mostly better left alone.

So the wizard finishing does not mean you are done tuning — it means nothing essential is missing. Four areas it never asks about keep their defaults until you go and set them: Managed loads, PV auto-scaling, MQTT and System.

Following a Learn more link out of the application carries your current level across to these pages, so what you see documented matches what you see in the dialog.

After the wizard