andig
commented
3 years ago @martinez81 ich würde gerne den SoC Refresh asynchron machen, dafür bräuchte ich Zugangsdaten zum Testen. Falls Du helfen willst gerne per Mail melden (cpuidle@gmx.de).
Closed martinez81 closed 3 years ago
andig
commented
3 years ago @martinez81 ich würde gerne den SoC Refresh asynchron machen, dafür bräuchte ich Zugangsdaten zum Testen. Falls Du helfen willst gerne per Mail melden (cpuidle@gmx.de).
martinez81
commented
3 years ago Hi Andreas!
Ja, du kannst den Zugang nochmal nutzen.
E-Mail: @.***
Passwort: XXX
Viele Grüße Martin
Am 13.05.2021 um 11:03 schrieb andig @.***>:
@martinez81 ich würde gerne den SoC Refresh asynchron machen, dafür bräuchte ich Zugangsdaten zum Testen. Falls Du helfen willst gerne per Mail melden @.***).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
andig
commented
3 years ago Super- PW habe ich entfernt. Weisst Du evtl, wie ich den Status eines Refreshes anhand der ID abfragen kann?
{"data":{"type":"RefreshBatteryStatus","id":"5638e62f-8aa2-4ed8-9575-39445bf36cbc","attributes":{}}}Falls nein müsste ich mich einfach am Timestamp des Ergebnisses orientieren:
{
"data": {
"type": "Car",
"id": "XXX",
"attributes": {
"rangeHvacOn": 163,
"chargeStatus": 1,
"timeRequiredToFullNormal": 450,
"timeRequiredToFullSlow": 0,
"plugStatusDetail": 1,
"rangeHvacOff": 169,
"batteryLevel": 65,
"plugStatus": 1,
"chargePower": 2,
"lastUpdateTime": "2021-05-13T11:13:08Z",
"timeRequiredToFullFast": 0,
"batteryCapacity": 40000,
"batteryBarLevel": 156
}
}
}Nein, tut mir leid. Wenn du die ID zum einloggen meinst, geht das nicht. Der Login mit einer ID ist ein altes System BJ vor 2019.
Gruß Martin
Am 13.05.2021 um 13:46 schrieb andig @.***>:
Super- PW habe ich entfernt. Weisst Du evtl, wie ich den Status eines Refreshes anhand der ID abfragen kann?
{"data":{"type":"RefreshBatteryStatus","id":"5638e62f-8aa2-4ed8-9575-39445bf36cbc","attributes":{}}} Falls nein müsste ich mich einfach am Timestamp des Ergebnisses orientieren:
{ "data": { "type": "Car", "id": "XXX", "attributes": { "rangeHvacOn": 163, "chargeStatus": 1, "timeRequiredToFullNormal": 450, "timeRequiredToFullSlow": 0, "plugStatusDetail": 1, "rangeHvacOff": 169, "batteryLevel": 65, "plugStatus": 1, "chargePower": 2, "lastUpdateTime": "2021-05-13T11:13:08Z", "timeRequiredToFullFast": 0, "batteryCapacity": 40000, "batteryBarLevel": 156 } } } — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Describe the bug Fahrzeug: Nissan Leaf Nach erneuten Anstecken des Fahrzeuges wird der SOC nicht angezeigt und wahrscheinlich nicht aktualisiert. Dadurch beginnt der Ladevorgang nicht. Erst wenn man das Ladeziel auf 100% setzt beginnt der Ladevorgang. Auch jetzt wird der SOC weder angezeigt noch aktualisiert. In der Nissan App kann der SOC aktualisiert werden. EVCC Neustart bewirkt, dass es wieder normal funktioniert.
Expected behavior SOC sollte bei angesteckten Fahrzeug immer angezeigt und aktualisiert werden.
EVCC details: Show output of
evcc -v:Show output of
evcc dump -c configfile:Show evcc configuration file
evcc.yaml:uri: 0.0.0.0:7070 # uri for ui interval: 10s # control cycle interval # log settings log: error levels: core: debug lp-1: debug lp-2: debug # meter definitions meters: - name: sma-grid type: sma serial: 3006138723 - name: sma-pv type: modbus model: sunspec uri: 192.168.0.165:502 id: 126 power: Power energy: Sum # charger definitions chargers: - name: GO-eCharger1 type: go-e # GO-eCharger uri: http://192.168.0.192 - name: GO-eCharger2 type: go-e uri: http://192.168.0.193 # vehicle definitions vehicles: - name: model3 type: tesla title: Model 3 capacity: 79 user: xxx # your email address used on Tesla website password: xxx # your password used on Tesla website password vin: xxx # the VIN of you car (can be obtained from Tesla website) tokens: access: xxx refresh: xxx cache: 5m - name: nissan type: nissan title: Leaf # display name for UI capacity: 40 # kWh user: xxx password: xxx region: DE # carwings region, leave empty for Europe cache: 5m # cache API response # site describes the EVU connection, PV and home battery site: title: Vogelhaus # display name for UI meters: grid: sma-grid # grid meter pv: sma-pv # pv meter # loadpoint loadpoints: - title: Wallbox 1 charger: GO-eCharger1 vehicle: nissan mode: now soc: poll: mode: charging interval: 15m min: 0 # immediately charge to 0% regardless of mode unless "off" (disabled) target: 90 # always charge to 100% estimate: true # set true to interpolate between api updates levels: # target soc levels for UI - 50 - 80 - 90 - 100 onDisconnect: # set defaults when vehicle disconnects mode: now # switch back to pv mode targetSoC: 90 # charge to 100% phases: 1 # ev phases (default 3) enable: # pv mode enable behavior delay: 1m # threshold must be exceeded for this long threshold: 0 # minimum export power (W). If zero, export must exceed minimum charge power to enable disable: # pv mode disable behavior delay: 5m # threshold must be exceeded for this long threshold: 200 # maximum import power (W) guardduration: 5m # switch charger contactor not more often than this (default 10m) mincurrent: 6 # minimum charge current (default 6A) maxcurrent: 16 # maximum charge current (default 16A) - title: Wallbox 2 charger: GO-eCharger2 vehicle: model3 mode: now soc: poll: mode: charging interval: 15m min: 0 # immediately charge to 0% regardless of mode unless "off" (disabled) target: 100 # always charge to 100% estimate: false # set true to interpolate between api updates levels: # target soc levels for UI - 50 - 80 - 90 - 100 onDisconnect: # set defaults when vehicle disconnects mode: now # switch back to pv mode targetSoC: 100 # charge to 100% phases: 3 # ev phases (default 3) enable: # pv mode enable behavior delay: 1m # threshold must be exceeded for this long threshold: 0 # minimum export power (W). If zero, export must exceed minimum charge power to enable disable: # pv mode disable behavior delay: 5m # threshold must be exceeded for this long threshold: 200 # maximum import power (W) guardduration: 5m # switch charger contactor not more often than this (default 10m) mincurrent: 6 # minimum charge current (default 6A) maxcurrent: 16 # maximum charge current (default 16A) hems: type: sma allowcontrol: true #false # set true to allow SHM controlling charger in PV modes # mqtt message broker mqtt: broker: 192.168.0.15:1883 topic: evcc # root topic for publishing, set empty to disable user: xxx password: xxx # influx database influx: # url: http://localhost:8086 # database: evcc # user: # password: # 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} services: # - type: pushover # app: # app id # recipients: # - # list of recipient ids # - type: telegram # token: # bot id # chats: # - # list of chat ids # - type: email # uri: smtp://:@:/?fromAddress=&toAddresses=
Show evcc log output with
--log trace:systemd zum ausführen von Evcc benutzt