Update README.md (#389)
Kleine Korrekturen und die Eingangsfahrzeug/Herstellerauflistung etwas entschlackt Co-authored-by: andig <cpuidle@gmx.de>
This commit is contained in:
parent
285d3c94ab
commit
be235ffb2f
1 changed files with 4 additions and 4 deletions
|
|
@ -18,7 +18,7 @@ EVCC is an extensible EV Charge Controller with PV integration implemented in [G
|
|||
- simple and clean user interface
|
||||
- multiple [chargers](#charger): Wallbe, Phoenix (includes ESL Walli), go-eCharger, NRGkick (direct Bluetooth or via Connect device), SimpleEVSE, EVSEWifi, KEBA/BMW, openWB, Mobile Charger Connect, and any other charger using scripting
|
||||
- multiple [meters](#meter): ModBus (Eastron SDM, MPM3PM, SBC ALE3 and many more), Discovergy (using HTTP plugin), SMA Home Manager 2.0 and SMA Energy Meter, KOSTAL Smart Energy Meter (KSEM, EMxx), any Sunspec-compatible inverter or home battery devices (Fronius, SMA, SolarEdge, KOSTAL, STECA, E3DC), Tesla PowerWall
|
||||
- different [vehicles](#vehicle) to show battery status: Audi (eTron), BMW (i3), Ford (Kuga, Mustang), Tesla, Nissan (Leaf), Renault ZE (ZOE...), VW (eUp, ID.3, ID.4) and any other vehicle using scripting
|
||||
- wide support of vendor-specifig [vehicles](#vehicle) interfaces (remote charge, battery and preconditioning status): Audi, BMW, Ford, Tesla, Nissan, Renault, Porsche, Volkswagen and any other vehicle using scripting
|
||||
- [plugins](#plugins) for integrating with hardware devices and home automation: Modbus (meters and grid inverters), MQTT and shell scripts
|
||||
- status notifications using [Telegram](https://telegram.org) and [PushOver](https://pushover.net)
|
||||
- logging using [InfluxDB](https://www.influxdata.com) and [Grafana](https://grafana.com/grafana/)
|
||||
|
|
@ -208,18 +208,18 @@ Configuration examples are documented at [andig/evcc-config#meters](https://gith
|
|||
|
||||
Vehicle represents a specific EV vehicle and its battery. If vehicle is configured and assigned to the charger, charge status and remaining charge duration become available in the user interface.
|
||||
|
||||
Available vehicle implementations are:
|
||||
Available vehicle remote interface implementations are:
|
||||
|
||||
- `audi`: Audi (eTron, Q55)
|
||||
- `bmw`: BMW (i3)
|
||||
- `bmw`: Ford (Kuga, Mustang)
|
||||
- `ford`: Ford (Kuga, Mustang)
|
||||
- `kia`: Kia (Bluelink vehicles like Soul 2019)
|
||||
- `hyundai`: Hyundai (Bluelink vehicles like Kona or Ioniq)
|
||||
- `nissan`: Nissan (Leaf)
|
||||
- `tesla`: Tesla (any model)
|
||||
- `renault`: Renault (Zoe, Kangoo ZE)
|
||||
- `porsche`: Porsche (Taycan)
|
||||
- `vw`: VW (eGolf, eUp, ID.3, ID.4)
|
||||
- `vw`: Volkswagen (eGolf, eUp, ID.3, ID.4)
|
||||
- `default`: default vehicle implementation using configurable [plugins](#plugins) for integrating any type of vehicle
|
||||
|
||||
Configuration examples are documented at [andig/evcc-config#vehicles](https://github.com/andig/evcc-config#vehicles)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue