Skip to content

Car charging

STABLE COMMUNITY

For a car assigned to a charger, the app sets a target: a minimum SoC, a target SoC and a departure time. This page says what the box does with it on its own, with its rules, and what needs an optimizer.

Without an optimizer, the box plans neither the target SoC nor the departure time

On its own, the box serves the minimum SoC and stops at the target SoC during off-peak hours. It does not work out when to charge so that the car reaches its target SoC by the departure time: the charger follows its mode (Auto or Manual) as if no departure were set. A target SoC and a departure that are met, with the plan of the day and buying at the cheapest hours, need an optimizer.

The car and its state of charge

Everything starts from the car assigned to the charger, on the charger's page (Choose). Without an assigned car, the page says so: "No car assigned: minimum SoC, target SoC and departure inactive". The box reads the car's state of charge (SoC) through its integration, for instance its manufacturer's API.

The box reads the car again while it is plugged in. When it is plugged in, the box asks the car for a fresh SoC. Then, as long as the charger reports the car as plugged in, it asks again as soon as the last value is more than 30 minutes old, at most once every half hour, and once more when it stops charging a car that stays plugged in. Only an integration that allows this is read again; the others publish the SoC at their own pace.

A SoC read more than 12 hours ago is not used for any decision: the box does not act on the minimum with a value that old.

Schedule charging

The Schedule charging button is on the charger's card (charger page and EMS settings), on its tile in Favourites when a car is assigned, and on the car's page. Above it, under Target, the app sums up the setting, for instance "80 % for 07:30".

The Car charging screen has four settings:

Setting What it is
Minimum SoC The safety reserve. 0 = off.
Target SoC The level you want at departure. 0 = none. The minimum cannot exceed the target SoC.
Departure time One time, every day, or none. It is the box's time.
Margin before departure 0 to 2 hours, 30 minutes by default.

You need an account that is allowed to control; otherwise the screen is read-only. The confirmation only shows if the box reads back what was sent. An older box does not have these settings: the app then shows neither the button nor the target.

What the box does on its own

Setting The box on its own, with its rules With an optimizer
Minimum SoC Served. Below the minimum, the charger charges from the grid at full power, at any time, up to the minimum + 2 points. At the peak price, it asks for your consent first (see below). Served by the box in the same way: the optimizer must plan around it and cannot remove it.
Target SoC Not planned. One effect only: during off-peak hours, where the charger in Auto would charge at full power, it stops when the car reaches its target SoC. Outside off-peak hours, nothing changes: solar surplus keeps charging beyond it. Planned for the departure time.
Departure time and margin Not planned: the charger follows its mode. Plan of the day, buying at the cheapest hours, "Target will not be met" alert.

In practice, without an optimizer: set a minimum SoC to be sure you can leave, and rely on off-peak hours (Auto mode, peak/off-peak tariff) or on Manual to charge more. The target SoC then limits off-peak charging.

The app shows the target and the explanation of the margin ("Charging aims to finish at the departure time minus this margin…") whether an optimizer is connected or not: without an optimizer, that explanation does not apply.

The minimum and the modes. In Auto and in the old modes, the minimum is served. In Manual, the Charge switch decides: on, the charger is already at full power; off, it is a deliberate stop, and the box does not charge, even below the minimum.

At the peak price

A slot is at the peak price when its price is at least twice the lowest price of the tariff in use; the factor is set in the Tariff screen. With an ordinary peak/off-peak tariff, peak hours are not at the peak price.

At the peak price, without your consent, the box buys nothing from the grid for the car, whatever its SoC: only the sun charges. With Manual on, the charger charges anyway: that is your choice.

  • Car below its minimum: the app asks you to "Charge at the peak price" or to wait for the end of the peak price. Without an answer, charging starts at the end of the peak price. Your consent holds for that peak price, and survives a restart of the box.
  • Warning ahead: if the minimum will not be reached before a peak price that is already known, the request goes out before it starts.
  • A shortfall of one SoC point at most does not trigger a request.

Target will not be met

When an optimizer foresees that the car will not reach its target, the app opens Target will not be met, with the energy that will be missing and the SoC expected at departure, and the Schedule charging button. The same text is in Right now and on the page. If the box does not say how much will be missing, the app does not make up a figure.

This alert comes from the optimizer only: the box on its own does not issue it, since it does not plan the target. Without an optimizer, it never appears.

Notifications

The peak-price request and the target that will not be met also arrive as a phone notification, on Android and Linux, when the app runs in the background, each one only once. These are local notifications: the app must stay connected to the box. Nothing on iOS or in the browser, and an app that Android has put to sleep shows the request when it is reopened.

Car without a SoC: kWh per plug-in

For a car whose SoC the box does not know, the API can set a minimum energy per plug-in, with a departure time (06:00 by default). The box on its own delivers it at the latest by the departure minus the margin, then leaves the charger open at its minimum until departure, so that the car can preheat or cool from the mains. This setting is not in the app.

Going further: methods and codes

Per-car settings: NymeaEnergy.GetCarChargingSettings, SetCarChargingSettings (full replacement, control right) and the CarChargingSettingsChanged notification. The margin is departureMarginS (0 to 7,200 s, 1,800 by default); the energy per plug-in is sessionMinEnergyWh, with r:defaultDeparture (06:00) when no departure is set.

Car state in the charger's telemetry (GetLoadTelemetry): EV_BELOW_MIN_SOC (below the minimum, served), EV_MIN_SOC_STALE (SoC older than 12 h), EV_MIN_SOC_NOT_SERVED (charger in Manual, switched off), EV_MIN_SOC_AWAITING_CONFIRMATION (below the minimum, at the peak price), EV_TARGET_NOT_PLANNED (target SoC or departure set, not planned this cycle: cause noOptimizer or optimizerNotCommanding), EV_TARGET_WITH_OPTIMIZER. Decision reasons: EV_TARGET_SOC_REACHED (target SoC reached during off-peak hours), EV_PEAK_AWAITING_CONFIRMATION (nothing is bought at the peak price without consent), ECO_FLOOR_SCHEDULED, EV_PRECONDITIONING (kWh per plug-in). The request is MinSocConfirmationRequested (field kind), the answer ConfirmMinSocCharging, per car or per charger. The target that will not be met is an optimizer's TARGET_NOT_MET code (missingWh, socAtDeparturePercent).