Closed TobiasHuber1980 closed 3 months ago
Was sagt /api/state in dem Moment?
Ich habe versucht den "richtigen Zeitpunkt" zu erwischen.
connect_1.txt connect_2.txt disconnect_1.txt disconnect_2.txt disconnect_3.txt während_ladevorgang.txt
bei connect:
invalid message template for connect: wanted: [vehicleTitle], got: [chargerIcon tariffPriceLoadpoints phasesActive influx maxGridSupplyWhileBatteryCharging connected charging vehicleName planOverrun disableThreshold vehicles effectiveMaxCurrent chargerFeatureIntegratedDevice limitEnergy enabled statistics currency version greenShareHome effectiveMinCurrent vehicleRange smartCostActive phasesEnabled vehicleClimaterActive bufferSoc bufferStartSoc planEnergy planTime effectivePlanSoc chargeTotalImport auth phaseAction batteryDischargeControl mode title siteTitle greenShareLoadpoints sponsor loadpoint maxCurrent tariffPriceHome minCurrent fatal chargeRemainingDuration mqtt gridConfigured chargerFeatureHeating vehicleLimitSoc smartCostType pvAction sessionSolarPercentage sessionPricePerKWh chargerPhysicalPhases homePower phaseRemaining chargeDuration pvPower sessionPrice limitSoc gridPower pv circuits priority vehicleOdometer chargeCurrents chargedEnergy connectedDuration planProjectedStart effectivePlanTime phasesConfigured tariffGrid residualPower vehicleSoc chargeRemainingEnergy pvRemaining chargePower batteryMode network sessionCo2PerKWh prioritySoc effectiveLimitSoc effectivePriority sessionEnergy chargerPhases1p3p tariffFeedIn enableThreshold pvEnergy vehicleDetectionActive chargeCurrent interval battery]
bei disconnect:
invalid message template for disconnect: wanted: [vehicleTitle], got: [connectedDuration charging planProjectedStart tariffGrid phasesActive effectivePriority phaseAction pvPower sessionPrice version sessionPricePerKWh sessionEnergy bufferSoc sponsor chargerIcon connected tariffPriceHome pvRemaining pvEnergy chargerPhases1p3p sessionCo2PerKWh planOverrun tariffPriceLoadpoints vehicleOdometer enableThreshold chargerPhysicalPhases chargeRemainingDuration chargeCurrent chargedEnergy circuits chargeDuration chargeRemainingEnergy title influx loadpoint effectiveLimitSoc effectivePlanTime chargePower statistics smartCostType effectiveMinCurrent effectiveMaxCurrent phasesEnabled limitEnergy vehicleClimaterActive vehicleSoc tariffFeedIn gridConfigured siteTitle chargerFeatureHeating chargerFeatureIntegratedDevice vehicleName chargeCurrents chargeTotalImport fatal battery batteryDischargeControl gridPower pv enabled phasesConfigured planEnergy mqtt residualPower priority vehicleLimitSoc greenShareLoadpoints prioritySoc pvAction planTime maxCurrent disableThreshold currency mode vehicleRange smartCostActive batteryMode network interval limitSoc auth vehicles homePower maxGridSupplyWhileBatteryCharging sessionSolarPercentage greenShareHome effectivePlanSoc minCurrent vehicleDetectionActive phaseRemaining bufferStartSoc]
bei start:
invalid message template for start: wanted: [vehicleTitle], got: [fatal pvAction sessionPricePerKWh minCurrent effectivePriority pvRemaining chargerIcon version effectiveLimitSoc mode batteryDischargeControl vehicleClimaterActive pvEnergy priority chargerPhysicalPhases maxGridSupplyWhileBatteryCharging bufferStartSoc pvPower vehicleRange chargedEnergy sessionPrice gridPower effectiveMinCurrent vehicleDetectionActive loadpoint tariffPriceLoadpoints currency effectivePlanSoc enabled disableThreshold title gridConfigured circuits effectivePlanTime vehicles limitEnergy chargeCurrent homePower auth effectiveMaxCurrent vehicleSoc phasesConfigured smartCostActive greenShareHome chargerPhases1p3p phasesActive pv bufferSoc residualPower influx phaseAction mqtt interval chargePower tariffPriceHome chargerFeatureHeating planProjectedStart connectedDuration sessionEnergy smartCostType limitSoc greenShareLoadpoints prioritySoc sessionSolarPercentage phasesEnabled enableThreshold network vehicleOdometer batteryMode chargeDuration vehicleLimitSoc maxCurrent planTime sessionCo2PerKWh battery siteTitle connected sponsor planEnergy chargeTotalImport charging tariffGrid chargeCurrents planOverrun chargerFeatureIntegratedDevice statistics vehicleName tariffFeedIn phaseRemaining]
Du hast ja mehrere Ladepunkte. Zu welchem gehört das Problem beim connect?
in desem fall war es lp-1.
zuhause mit nur einem ladepunkt (openwb pro) ist das gleiche verhalten. ${vehicleTitle}
bei conncect/disconnect und (glaube ich start/stop). battery soc update mit ${vehicleTitle}
funktioniert.
Also:
"vehicleName": "car1",
"title": "VW ID.5 (Tobias Huber)",
dann sollte der Titel auch verfügbar sein- im Code ist das drin. Du kannst nochmal cache: trace
setzen und so einen Fall bei connect
reproduzieren- vielleicht sehen wir dann etwas. Gerne Lp1.
ist jetzt von der pv anlage daheim: Trace-Log: evcc-20240706-115040-trace.log
api/state:
{
"result": {
"auth": {
},
"battery": [
{
"power": -4270.294921875,
"soc": 90.0751292705536,
"capacity": 11.5,
"controllable": false
}
],
"batteryCapacity": 11.5,
"batteryDischargeControl": false,
"batteryEnergy": 0,
"batteryMode": "unknown",
"batteryPower": -4270.295,
"batterySoc": 90.075,
"bufferSoc": 100,
"bufferStartSoc": 0,
"currency": "EUR",
"fatal": null,
"greenShareHome": 1,
"greenShareLoadpoints": 0,
"gridConfigured": true,
"gridEnergy": 0,
"gridPower": 5.631,
"homePower": 385.48,
"influx": {
"url": "",
"database": "",
"org": "",
"user": ""
},
"interval": 20,
"loadpoints": [
{
"chargeCurrent": 0,
"chargeCurrents": [0, 0, 0],
"chargeDuration": 0,
"chargePower": 0,
"chargeRemainingEnergy": 6844.444,
"chargeTotalImport": 1358.923,
"chargedEnergy": 0,
"chargerFeatureHeating": false,
"chargerFeatureIntegratedDevice": false,
"chargerIcon": null,
"chargerPhases1p3p": true,
"chargerPhysicalPhases": null,
"charging": false,
"connected": true,
"connectedDuration": 0,
"disableThreshold": 0,
"effectiveLimitSoc": 100,
"effectiveMaxCurrent": 16,
"effectiveMinCurrent": 6,
"effectivePlanSoc": 0,
"effectivePlanTime": null,
"effectivePriority": 0,
"enableThreshold": 0,
"enabled": false,
"limitEnergy": 0,
"limitSoc": 0,
"maxCurrent": 16,
"minCurrent": 6,
"mode": "pv",
"phaseAction": "inactive",
"phaseRemaining": 0,
"phasesActive": 3,
"phasesConfigured": 0,
"phasesEnabled": 3,
"planEnergy": 0,
"planOverrun": 0,
"planProjectedStart": null,
"planTime": null,
"priority": 0,
"pvAction": "enable",
"pvRemaining": 59,
"sessionCo2PerKWh": null,
"sessionEnergy": 0,
"sessionPrice": null,
"sessionPricePerKWh": null,
"sessionSolarPercentage": 0,
"smartCostActive": false,
"title": "Garage",
"vehicleClimaterActive": null,
"vehicleDetectionActive": false,
"vehicleLimitSoc": 100,
"vehicleName": "db:1",
"vehicleOdometer": 16004,
"vehicleRange": 481,
"vehicleSoc": 92
}
],
"maxGridSupplyWhileBatteryCharging": 0,
"mqtt": {
"broker": "",
"topic": "evcc",
"user": "",
"clientID": "",
"insecure": false
},
"network": {
"schema": "http",
"host": "evcc.local",
"port": 7070
},
"prioritySoc": 90,
"pv": [
{
"power": 4650.14453125
}
],
"pvEnergy": 0,
"pvPower": 4650.145,
"residualPower": 100,
"siteTitle": "Zuhause",
"smartCostType": "pricestatic",
"sponsor": {
"name": "TobiasHuber1980",
"expiresAt": "2043-08-28T15:25:58Z"
},
"statistics": {
"30d": {
"avgCo2": 0,
"avgPrice": 0.0827934639863253,
"chargedKWh": 28.2749999999996,
"solarPercentage": 98.7822737635897
},
"365d": {
"avgCo2": 0,
"avgPrice": 0.129765028890619,
"chargedKWh": 1797.01722999354,
"solarPercentage": 79.5076524962261
},
"total": {
"avgCo2": 0,
"avgPrice": 0.127126745395713,
"chargedKWh": 2047.55724366258,
"solarPercentage": 80.9361983352054
}
},
"tariffFeedIn": 0.08,
"tariffGrid": 0.309,
"tariffPriceHome": 0.08,
"tariffPriceLoadpoints": 0.309,
"vehicles": {
"db:1": {
"title": "VW ID.5",
"icon": "car",
"capacity": 77
},
"db:3": {
"title": "VW ID.4",
"icon": "car",
"capacity": 77
},
"db:6": {
"title": "VW ID.3",
"icon": "car",
"capacity": 58
}
},
"version": "0.128.1"
}
}
Wo siehst Du trace?
@hrpv kannst du den fehler bei dir mit der konfig nachstellen?
also konkret ${vehicleTitle}
bei connect
und disconnect
events:
start: # charge start event
title: Charge started
msg: ${vehicleTitle} started charging
stop: # charge stop event
title: Charge finished
msg: ${vehicleTitle} finished charging ${chargedEnergy:%.1fk}kWh
connect: # vehicle connect event
title: Car connected
msg: ${vehicleTitle} connected on Wallbox ${title}
disconnect: # vehicle connected event
title: Car disconnected
msg: ${vehicleTitle} disconnected
Wo siehst Du trace? yaml log levels gesetzt:
log: debug levels: messaging: trace cache: trace
Im Log im UI findet jedoch an keiner Stelle
[cache ] TRACE
. Keine Ahnung warum!?
api/state erkennt korrekt:
"vehicleName": "db:1",
"db:1": {
"title": "VW ID.5",
}
evcc-20240707-195416-trace.log api_state.txt
habe noch https://github.com/evcc-io/evcc/issues/12862 und https://github.com/evcc-io/evcc/pull/10668 dazu gefunden, ich kann aber nicht sagen, ob das damit zusammenhängen könnte.
Describe the bug
bei connect & disconnect kommt folgender fehler:
[push ] ERROR 2024/07/04 09:19:24 invalid message template for connect: wanted: [vehicleTitle], got:.... siehe unten
kann vielleicht noch mit #13856 in Verbindung gebracht werden.
start/stop charging undsoc update funktionieren.Steps to reproduce
Configuration details
Log details
What type of operating system are you running?
Linux
Version
0.128.0