Guten Tag ,
zu erst mal ein großes Lob an die Entwickler, tolle Arbeit .
Als erstes gesagt ich bin absoluter Neuling im Raspi Bereich, habe mich jedoch etwas schlau gelesen und es auch geschafft HA und evcc zu laufen zu bekommen.
Soweit so gut , habe nun folgendes Problem evcc weckt meinen Tesla nich auf zum Laden. Sobald ich in meiner Tesla App das Fahrzeug wecke geht es auch los.
Fehlermeldung [lp-1 ] ERROR 2024/08/09 10:49:34 max charge current 2A: vehicle not capable of current control
zu meiner Konfiguration
Evcc auf HA
Tesla WC 3
Tesla Model Y
Huawei Solar
werde das Log und meine Config noch anhängen . Hoffe ihr könnt mir helfen.
name: White_Ghost
type: template
template: tesla
title: White Ghost # Wird in der Benutzeroberfläche angezeigt (optional)
icon: car # Icon in der Benutzeroberfläche (optional)
accessToken: xxxxxxxx
refreshToken: EU_xxxxx
vin: xxxxxxx # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
capacity: 78 # Akkukapazität in kWh (optional)
phases: 3 # Die maximale Anzahl der Phasen welche genutzt werden können (optional)
commandProxy: https://tesla.evcc.io/ # Bei Verwendung eines TWC3 (oder eines anderen 'dummen' Ladegeräts, das nicht steuerbar ist) kann evcc die Ladung direkt verwalten, indem es über einen Command Proxy mit dem Fahrzeug kommuniziert. Standardmäßig wird der von evcc bereitgestellte Proxy verwendet. Dieses parameter setzt die Basis-URL eines benutzerdefinierten Command Proxy, der anstelle des standardmäßigen evcc-Proxy verwendet werden soll. Siehe zum Beispiel https://github.com/wimaha/TeslaBleHttpProxy für einen Proxy, der Kommandos über Bluetooth sendet. (optional)
mode: PV # Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional)
minCurrent: 2 # Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)
maxCurrent: 16 # Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)
identifiers: # Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional)
priority: # Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)
site describes the EVU connection, PV and home battery
site:
title: Home # display name for UI
meters:
grid: my_grid # grid meter
pv:
my_pv # list of pv inverters/ meters
battery:
my_battery # list of battery meters
residualPower: 100 # additional household usage margin
maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value
loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
title: Ladeplatz # display name for UI
charger: TeslaWallconnector # charger
meter: charge # charge meter
mode: pv # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available
remaining settings are experts-only and best left at default values
priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
soc:
polling defines usage of the vehicle APIs
Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
poll:
poll mode defines under which condition the vehicle API is called:
# charging: update vehicle ONLY when charging (this is the recommended default)
# connected: update vehicle when connected (not only charging), interval defines how often
# always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
mode: charging
# poll interval defines how often the vehicle API may be polled if NOT charging
interval: 60m
estimate: true # set false to disable interpolating between api updates (not recommended)
enable: # pv mode enable behavior
delay: 1m # threshold must be exceeded for this long
threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
disable: # pv mode disable behavior
delay: 3m # threshold must be exceeded for this long
threshold: 0 # maximum import power (W)
homeid: xxxxxxxx # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)
#charges: # Zusätzlicher fester Aufschlag pro kWh (z.B. 0.05 für 5 Cent) (optional)
#tax: # Zusätzlicher prozentualer Aufschlag (z.B. 0.2 für 20%) (optional)
feedin:
rate for feeding excess (pv) energy to the grid
type: fixed
price: 0.082 # EUR/kWh
# type: octopusenergy
# tariff: AGILE-FLEX-22-11-25 # Tariff code
# region: A # optional
# type: amber
# token: # api token from https://app.amber.com.au/developers/
# siteid: # site ID returned by the API
# channel: feedIn
co2:
co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
# type: grünstromindex # GrünStromIndex (Germany only)
# zip: <zip>
# type: electricitymaps # https://app.electricitymaps.com/map
# uri: <uri>
# token: <token> # needs to be a token with forecast (not in the free tier)
# zone: DE
# type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
# provides national data if both region and postcode are omitted - Choose ONE only!
# region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
# postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only
mqtt message broker
mqtt:
broker: localhost:1883
topic: evcc # root topic for publishing, set empty to disable
Guten Tag , zu erst mal ein großes Lob an die Entwickler, tolle Arbeit .
Als erstes gesagt ich bin absoluter Neuling im Raspi Bereich, habe mich jedoch etwas schlau gelesen und es auch geschafft HA und evcc zu laufen zu bekommen. Soweit so gut , habe nun folgendes Problem evcc weckt meinen Tesla nich auf zum Laden. Sobald ich in meiner Tesla App das Fahrzeug wecke geht es auch los.
Fehlermeldung [lp-1 ] ERROR 2024/08/09 10:49:34 max charge current 2A: vehicle not capable of current control
zu meiner Konfiguration Evcc auf HA Tesla WC 3 Tesla Model Y Huawei Solar
werde das Log und meine Config noch anhängen . Hoffe ihr könnt mir helfen.
[main ] INFO 2024/08/09 10:44:22 evcc 0.129.0 [main ] INFO 2024/08/09 10:44:22 using config file: /config/evcc.yaml [db ] INFO 2024/08/09 10:44:22 using sqlite database: /data/evcc.db [main ] INFO 2024/08/09 10:44:23 listening at :7070 [site ] INFO 2024/08/09 10:44:24 site config: [site ] INFO 2024/08/09 10:44:24 meters: grid ✓ pv ✓ battery ✓ [site ] INFO 2024/08/09 10:44:24 grid: power ✓ energy ✓ currents ✓ [site ] INFO 2024/08/09 10:44:24 pv 1: power ✓ energy ✓ currents ✗ [site ] INFO 2024/08/09 10:44:24 battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗ [site ] INFO 2024/08/09 10:44:24 vehicles: [site ] INFO 2024/08/09 10:44:24 vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓ [lp-1 ] INFO 2024/08/09 10:44:24 loadpoint 1: [lp-1 ] INFO 2024/08/09 10:44:24 mode: pv [lp-1 ] INFO 2024/08/09 10:44:24 charger: power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗ [lp-1 ] INFO 2024/08/09 10:44:24 meters: charge ✓ [lp-1 ] INFO 2024/08/09 10:44:24 charge: power ✓ energy ✗ currents ✓ [site ] DEBUG 2024/08/09 10:44:24 set buffer soc: 70 [site ] DEBUG 2024/08/09 10:44:24 set priority soc: 70 [site ] DEBUG 2024/08/09 10:44:24 set battery discharge control: true [lp-1 ] DEBUG 2024/08/09 10:44:24 set smart cost limit: 0 [lp-1 ] DEBUG 2024/08/09 10:44:24 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger) [lp-1 ] DEBUG 2024/08/09 10:44:24 phase timer inactive [lp-1 ] DEBUG 2024/08/09 10:44:24 pv timer inactive [site ] DEBUG 2024/08/09 10:44:24 ---- [lp-1 ] DEBUG 2024/08/09 10:44:24 charge power: 0W [lp-1 ] DEBUG 2024/08/09 10:44:24 charge currents: [0.4 0 0.3]A [site ] DEBUG 2024/08/09 10:44:31 pv power: 2097W [site ] DEBUG 2024/08/09 10:44:32 battery soc: 82% [site ] DEBUG 2024/08/09 10:44:32 battery power: -1682W [site ] DEBUG 2024/08/09 10:44:33 grid meter: -3W [site ] DEBUG 2024/08/09 10:44:36 grid currents: [-0.34 0.62 -0.34]A [site ] DEBUG 2024/08/09 10:44:37 site power: -1585W [lp-1 ] DEBUG 2024/08/09 10:44:37 charge voltages: [0 0 0]V [lp-1 ] DEBUG 2024/08/09 10:44:37 charger status: B [lp-1 ] INFO 2024/08/09 10:44:37 car connected [lp-1 ] DEBUG 2024/08/09 10:44:37 vehicle api refresh [lp-1 ] DEBUG 2024/08/09 10:44:37 pv timer elapse [lp-1 ] DEBUG 2024/08/09 10:44:37 pv timer inactive [lp-1 ] DEBUG 2024/08/09 10:44:37 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger) [lp-1 ] DEBUG 2024/08/09 10:44:37 pv charge current: 2.3A = 0A + 2.3A (-1585W @ 3p) [lp-1 ] DEBUG 2024/08/09 10:44:37 site power -1585W <= 0W enable threshold [lp-1 ] DEBUG 2024/08/09 10:44:37 pv enable in 0s [lp-1 ] DEBUG 2024/08/09 10:44:37 pv enable timer elapsed [lp-1 ] ERROR 2024/08/09 10:44:37 max charge current 2A: vehicle not capable of current control [lp-1 ] DEBUG 2024/08/09 10:46:36 set smart cost limit: 0.33 [lp-1 ] DEBUG 2024/08/09 10:46:37 set smart cost limit: 0.325 [lp-1 ] DEBUG 2024/08/09 10:46:38 set smart cost limit: 0.325 [lp-1 ] DEBUG 2024/08/09 10:46:39 set smart cost limit: 0.295 [lp-1 ] DEBUG 2024/08/09 10:46:40 set smart cost limit: 0.295 [lp-1 ] DEBUG 2024/08/09 10:46:40 set smart cost limit: 0.295 [lp-1 ] DEBUG 2024/08/09 10:46:41 set smart cost limit: 0.295 [lp-1 ] DEBUG 2024/08/09 10:46:41 set smart cost limit: 0.295 [lp-1 ] DEBUG 2024/08/09 10:46:45 set smart cost limit: 0.195 [lp-1 ] DEBUG 2024/08/09 10:46:46 set smart cost limit: 0.195 [lp-1 ] DEBUG 2024/08/09 10:46:46 set smart cost limit: 0.195 [lp-1 ] DEBUG 2024/08/09 10:46:49 set smart cost limit: 0.185 [lp-1 ] DEBUG 2024/08/09 10:46:50 set smart cost limit: 0.185 [lp-1 ] DEBUG 2024/08/09 10:46:50 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:51 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:52 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:52 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:53 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:54 set smart cost limit: 0.18 [site ] DEBUG 2024/08/09 10:46:54 ---- [lp-1 ] DEBUG 2024/08/09 10:46:54 charge power: 0W [lp-1 ] DEBUG 2024/08/09 10:46:54 charge currents: [0.4 0 0.3]A [lp-1 ] DEBUG 2024/08/09 10:46:54 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:55 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:56 set smart cost limit: 0.18 [lp-1 ] DEBUG 2024/08/09 10:46:57 set smart cost limit: 0.18 [site ] DEBUG 2024/08/09 10:46:59 pv power: 2268W [lp-1 ] DEBUG 2024/08/09 10:47:01 set smart cost limit: 0 [site ] DEBUG 2024/08/09 10:47:03 battery soc: 82% [site ] DEBUG 2024/08/09 10:47:03 battery power: -1851W [site ] DEBUG 2024/08/09 10:47:05 grid meter: 3W [site ] DEBUG 2024/08/09 10:47:07 grid currents: [-0.37 0.62 -0.31]A [site ] DEBUG 2024/08/09 10:47:08 site power: -1748W [lp-1 ] DEBUG 2024/08/09 10:47:08 charge voltages: [0 0 0]V [lp-1 ] DEBUG 2024/08/09 10:47:08 charger status: B [lp-1 ] DEBUG 2024/08/09 10:47:08 vehicle api refresh [lp-1 ] DEBUG 2024/08/09 10:47:09 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger) [lp-1 ] DEBUG 2024/08/09 10:47:09 pv charge current: 2.53A = 0A + 2.53A (-1748W @ 3p) [lp-1 ] DEBUG 2024/08/09 10:47:09 site power -1748W <= 0W enable threshold [lp-1 ] DEBUG 2024/08/09 10:47:09 pv enable in 0s [lp-1 ] DEBUG 2024/08/09 10:47:09 pv enable timer elapsed [lp-1 ] ERROR 2024/08/09 10:47:09 max charge current 2A: vehicle not capable of current control [site ] DEBUG 2024/08/09 10:49:24 ---- [lp-1 ] DEBUG 2024/08/09 10:49:24 charge power: 0W [lp-1 ] DEBUG 2024/08/09 10:49:24 charge currents: [0.4 0 0.3]A [site ] DEBUG 2024/08/09 10:49:26 pv power: 1838W [site ] DEBUG 2024/08/09 10:49:29 battery soc: 83% [site ] DEBUG 2024/08/09 10:49:29 battery power: -1503W [site ] DEBUG 2024/08/09 10:49:30 grid meter: 14W [site ] DEBUG 2024/08/09 10:49:32 grid currents: [0.32 0.68 -0.45]A [site ] DEBUG 2024/08/09 10:49:34 site power: -1389W [lp-1 ] DEBUG 2024/08/09 10:49:34 charge voltages: [0 0 0]V [lp-1 ] DEBUG 2024/08/09 10:49:34 charger status: B [lp-1 ] DEBUG 2024/08/09 10:49:34 vehicle api refresh [lp-1 ] DEBUG 2024/08/09 10:49:34 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger) [lp-1 ] DEBUG 2024/08/09 10:49:34 pv charge current: 2.01A = 0A + 2.01A (-1389W @ 3p) [lp-1 ] DEBUG 2024/08/09 10:49:34 site power -1389W <= 0W enable threshold [lp-1 ] DEBUG 2024/08/09 10:49:34 pv enable in 0s [lp-1 ] DEBUG 2024/08/09 10:49:34 pv enable timer elapsed [lp-1 ] ERROR 2024/08/09 10:49:34 max charge current 2A: vehicle not capable of current control
Config yaml
network:
schema is the HTTP schema
setting to
https
does not enable https, it only changes the way URLs are generatedschema: http
host is the hostname or IP address
if the host name contains a
.local
suffix, the name will be announced on MDNSdocker: MDNS announcements don't work. host must be set to the docker host's name.
host: xxx.xxx.xxx.xxx
port is the listening port for UI and api
evcc will listen on all available interfaces
port: 7070
interval: 150s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
database configuration for persisting charge sessions and settings
database:
type: sqlite
dsn:
sponsor token enables optional features (request at https://sponsor.evcc.io)
trial token, valid until 2024-08-23
sponsortoken: xxxxxxxxxx
telemetry enables aggregated statistics
#
Telemetry allows collecting usage data (grid and green energy, charge power).
Data is aggregated, no individual charging sessions are tracked. The collected,
anonymous data can be retrieved using https://api.evcc.io.
#
See https://github.com/evcc-io/evcc/pull/4343 or details.
#
For time being, this is only available to sponsors, hence data is associated with
the sponsor token's identity.
#
telemetry: true
log settings
log: info levels: site: debug lp-1: debug lp-2: debug cache: error db: error
modbus proxy for allowing external programs to reuse the evcc modbus connection
each entry will start a proxy instance at the given port speaking Modbus TCP and
relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
- port: 5200
uri: solar-edge:502
rtu: true
readonly: true # use
deny
to raise modbus errorsmeter definitions
name can be freely chosen and is used as reference when assigning meters to site and loadpoints
for documentation see https://docs.evcc.io/docs/devices/meters
meters:
name: my_grid type: template template: huawei-dongle-powersensor usage: grid
Modbus TCP
modbus: tcpip id: 1 host: xxx.xxx.xxx.xxx # Hostname port: 502 # Port timeout: 15s # optional
name: my_pv type: template template: huawei-dongle-powersensor usage: pv
Modbus TCP
modbus: tcpip id: 1 host: xxx.xxx.xxx.xxx # Hostname port: 502 # Port timeout: 15s # optional
name: my_battery type: template template: huawei-dongle-powersensor usage: battery
Modbus TCP
modbus: tcpip id: 1 host: xxx.xxx.xxx.xxx # Hostname port: 502 # Port timeout: 15s # optional
charger definitions
name can be freely chosen and is used as reference when assigning charger to vehicle
for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
vehicle definitions
name can be freely chosen and is used as reference when assigning vehicle to loadpoint
for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
site describes the EVU connection, PV and home battery
site: title: Home # display name for UI meters: grid: my_grid # grid meter pv:
loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
title: Ladeplatz # display name for UI charger: TeslaWallconnector # charger
meter: charge # charge meter
mode: pv # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available
remaining settings are experts-only and best left at default values
priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority) soc:
polling defines usage of the vehicle APIs
Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
poll:
poll mode defines under which condition the vehicle API is called:
estimate: true # set false to disable interpolating between api updates (not recommended) enable: # pv mode enable behavior delay: 1m # threshold must be exceeded for this long threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable disable: # pv mode disable behavior delay: 3m # threshold must be exceeded for this long threshold: 0 # maximum import power (W)
tariffs are the fixed or variable tariffs
tariffs: grid: type: template template: tibber token: xxxxxxxxxxxxxx-
homeid: xxxxxxxx # Nur erforderlich, wenn du mehrere Häuser in deinem Tibber-Konto hast. (optional)
feedin:
rate for feeding excess (pv) energy to the grid
co2:
co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
mqtt message broker
mqtt:
broker: localhost:1883
topic: evcc # root topic for publishing, set empty to disable
user: xxx-xxxxx
password: xxxxxxx
influx database
influx:
url: http://localhost:8086
database: evcc
user:
password:
eebus credentials
eebus:
uri: # :4712
interfaces: # limit eebus to specific network interfaces
- en0
certificate: # local signed certificate, required, can be generated via
evcc eebus-cert
public: # public key
private: # private key
push messages
messaging: events: start: # charge start event title: Charge started msg: Started charging in "${mode}" mode stop: # charge stop event title: Charge finished msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}. connect: # vehicle connect event title: Car connected msg: "Car connected at ${pvPower:%.1fk}kW PV" disconnect: # vehicle connected event title: Car disconnected msg: Car disconnected after ${connectedDuration} soc: # vehicle soc update event title: Soc updated msg: Battery charged to ${vehicleSoc:%.0f}% guest: # vehicle could not be identified title: Unknown vehicle msg: Unknown vehicle, guest connected? services