Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 0 additions & 48 deletions docs/reference/configuration/loadpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -335,54 +335,6 @@ Ist dem Ladepunkt keine Wallbox, sondern eine der unterstützten schaltbaren Ste

---

### `minCurrent`

:::note veraltet in yaml
Dieser Wert kann nun im Einstellungsdialog am Ladepunkt gesetzt werden.
:::

Definiert die minimal genutzte Stromstärke in Ampere (A) pro angeschlossener Phase von der Zuleitung zur Wallbox.

Wie bereits bei `phases` beschrieben, wird über diesen Wert die Mindestladeleistung festgelegt.

Bei Wallboxen mit automatischer Phasenumschaltung wird in 3p solange geladen, bis dieser Wert (von oben) erreicht ist. Erst dann wird auf 1p umgeschaltet.

:::info
Im Allgemeinen benötigt ein Elektrofahrzeug mindestens eine Stromstärke von 6A pro Phase um zu Laden. Bei manchen Fahrzeugen wird jedoch auch eine höhere Mindeststromstärke benötigt!

Bei Wallboxen und Fahrzeugen welche über den ISO15118 Standard kommunizieren kann unter Umständen auch mit einer geringeren Stromstärke pro Phase geladen werden, wenn die Gesamtleistung trotzdem mindestens etwa 1,4kW beträgt.
:::

**Standardwert:** `6`

**Beispiel**:

```yaml
mincurrent: 6
```

---

### `maxCurrent`

:::note veraltet in yaml
Dieser Wert kann nun im Einstellungsdialog am Ladepunkt gesetzt werden.
:::

Definiert die maximal zulässige Stromstärke in Ampere (A) pro angeschlossener Phase von der Zuleitung zur Wallbox.

Bei Wallboxen mit automatischer Phasenumschaltung wird in 1p solange geladen, bis dieser Wert (von unten) erreicht ist. Erst dann wird auf 3p umgeschaltet.

**Standardwert:** `16`

**Beispiel**:

```yaml
maxcurrent: 16
```

---

### `priority`

Dient während der Ladung der Priorisierung von Loadpoints untereinander.
Expand Down
4 changes: 2 additions & 2 deletions docs/reference/configuration/messaging.md
Original file line number Diff line number Diff line change
Expand Up @@ -159,8 +159,8 @@ Die von evcc bereitgestellten Variablen (siehe auch /api/state) müssen als rege
- Ladepunkte (loadpoint)
- Konfiguration
- [`loadpoint`](loadpoints) - Laufende Nummer des Ladepunktes (_integer_)
- [`maxCurrent`](loadpoints#maxcurrent) - Maximale Lade-Stromstärke in Ampere (_float_)
- [`minCurrent`](loadpoints#mincurrent) - Minimale Lade-Stromstärke in Ampere (_float_)
- `maxCurrent` - Maximale Lade-Stromstärke in Ampere (_float_)
- `minCurrent` - Minimale Lade-Stromstärke in Ampere (_float_)
- [`mode`](loadpoints#mode) - Initialer Modus des Ladepunktes nach evcc-Start `off`/`now`/`min`/`pv` (_string_)
- [`phases`](loadpoints#phases) - Initial aktive Anzahl Stromphasen des Ladepunktes nach evcc-Start (_integer_)
- [`title`](loadpoints#title) - Bezeichnung des Ladepunktes in der evcc App (_string_)
Expand Down
43 changes: 0 additions & 43 deletions docs/reference/configuration/vehicles.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -119,49 +119,6 @@ cache: 5m

---

### `onIdentify`

Standardwerte die bei Erkennung des Fahrzeuges angewendet werden sollen:

**Mögliche Werte**:

- [`mode`](loadpoints#mode)
- [`minCurrent`](loadpoints#mincurrent)
- [`maxCurrent`](loadpoints#maxcurrent)
- [`priority`](https://docs.evcc.io/docs/reference/configuration/loadpoints#priority)

:::

**Beispiel**:

<Tabs groupId="config-type">
<TabItem value="Template" label="Template" default>
Wenn die Fahrzeuge über den <i>type=templates</i> in die Konfiguration eingebunden werdnen, z.b. bei Verwendung von <i>evcc configure</i>.

```yaml
mode: pv
mincurrent: 8
maxcurrent: 20
priority: 5
```

</TabItem>
<TabItem value="Native" label="Native">
Wenn die Fahrzeuge über ihren nativen Typ, z.b. <i>type=audi</i>, in die Konfiguration eingebunden werden.

```yaml
onIdentify: # set defaults when vehicle is identified
mode: pv
mincurrent: 8
maxcurrent: 20
priority: 5
```

</TabItem>
</Tabs>

---

### `identifiers`

Eine Liste mit einer oder mehreren Kennungen um das Fahrzeug zu identifizieren. Soll das Fahrzeug zum Beispiel an unterschiedlichen Wallboxen identifiziert werden können, müssen unter Umständen mehrere Kennungen verwendet werden. Die Erkennung kann dabei über folgende Mechanismen erfolgen:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -329,54 +329,6 @@ If the charging point is not assigned a charger but one of the supported control

---

### `minCurrent`

:::note deprecated in yaml
This value can now be set in the charging point settings dialog.
:::

Defines the minimum used current in amperes (A) per connected phase from the supply to the charger.

As mentioned with `phases`, this value sets the minimum charging power.

For chargers with automatic phase switching, it will continue to charge in 3p until this value (from above) is reached. Only then will it switch to 1p.

:::info
In general, an electric vehicle requires a minimum current of 6A per phase to charge. However, some vehicles might require a higher minimum current!

For chargers and vehicles communicating via the ISO15118 standard, it might be possible to charge with a lower current per phase if the total power is still at least around 1.4kW.
:::

**Default value:** `6`

**For example**:

```yaml
mincurrent: 6
```

---

### `maxCurrent`

:::note deprecated in yaml
This value can now be set in the charging point settings dialog.
:::

Defines the maximum allowable current in amps (A) per connected phase from the supply to the charger.

For chargers with automatic phase switching, it will continue to charge in single phase until this value (from below) is reached. Only then will it switch to three-phase.

**Default value:** `16`

**For example**:

```yaml
maxcurrent: 16
```

---

### `priority`

During charging, this parameter prioritises loadpoints with each other.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -160,8 +160,8 @@ The variables provided by evcc (also see /api/state) must be defined as `${<Vari
- Charging Point (loadpoint)
- Configuration
- [`loadpoint`](loadpoints) - Loadpoint index (_integer_)
- [`maxCurrent`](loadpoints#maxcurrent) - Maximum charging current in amperes (_float_)
- [`minCurrent`](loadpoints#mincurrent) - Minimum charging current in amperes (_float_)
- `maxCurrent` - Maximum charging current in amperes (_float_)
- `minCurrent` - Minimum charging current in amperes (_float_)
- [`mode`](loadpoints#mode) - Initial mode of the charging point after evcc start `off`/`now`/`min`/`pv` (_string_)
- [`phases`](loadpoints#phases) - Initial active number of phases of the charging point after evcc start (_integer_)
- [`title`](loadpoints#title) - Label of the charging point in the evcc app (_string_)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -115,49 +115,6 @@ cache: 5m

---

### `onIdentify`

Default values to be applied when the vehicle is identified:

**Possible Values**:

- [`mode`](loadpoints#mode)
- [`minCurrent`](loadpoints#mincurrent)
- [`maxCurrent`](loadpoints#maxcurrent)
- `minSoc` charge at the highest possible power until the specified SoC is reached, if the mode is not set to `off`
- `targetSoc` stop charging when this SoC is reached
- [`priority`](./loadpoints#priority)

**For example**:

<Tabs groupId="config-type">
<TabItem value="Template" label="Template" default>
When vehicles are integrated into the configuration using the <i>type=templates</i>, e.g., when using <i>evcc configure</i>.

mode: pv
mincurrent: 8
maxcurrent: 20
minSoc: 40
targetSoc: 80
priority: 5

</TabItem>
<TabItem value="Native" label="Native">
When vehicles are integrated using their native type, e.g., <i>type=audi</i>, in the configuration.

onIdentify: # set defaults when vehicle is identified
mode: pv
mincurrent: 8
maxcurrent: 20
minSoc: 40
targetSoc: 80
priority: 5

</TabItem>
</Tabs>

---

### `identifiers`

A list of one or more identifiers to identify the vehicle. If the vehicle needs to be identified at different chargers, multiple identifiers might be necessary. Identification can be achieved using the following mechanisms:
Expand Down
6 changes: 2 additions & 4 deletions static/rest-api.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -309,8 +309,7 @@ paths:
post:
summary: Update maximum current
description: >
Updates the maximum current of the loadpoint. [Read
more.](/en/docs/reference/configuration/loadpoints#maxcurrent)
Updates the maximum current of the loadpoint.
tags:
- Loadpoints
parameters:
Expand All @@ -323,8 +322,7 @@ paths:
post:
summary: Update minimum current
description: >
Updates the minimum current of the loadpoint. [Read
more.](/en/docs/reference/configuration/loadpoints#mincurrent)
Updates the minimum current of the loadpoint.
tags:
- Loadpoints
parameters:
Expand Down