Mindestladung bei Ankunft: Lädt nur 1-phasig bei Phaseneinstellung "automatisch" #18610
Closed
2 tasks done
Assignees
Labels
bug
Something isn't working
Comments
|
Missing config |
|
Config ergänzt in Beschreibung oben... |
|
Laut Log passiert // minimum or target charging
case lp.minSocNotReached() || plannerActive:
err = lp.fastCharging()
lp.resetPhaseTimer()
lp.elapsePVTimer() // let PV mode disable immediately afterwardswobei der erste Aufruf auf 3p schaltet. Davon zeigt das Log aber nichts. Das müsste hier passieren: // scalePhasesIfAvailable scales if api.PhaseSwitcher is available
func (lp *Loadpoint) scalePhasesIfAvailable(phases int) error {
if lp.configuredPhases != 0 {
phases = lp.configuredPhases
}
if lp.hasPhaseSwitching() {
return lp.scalePhases(phases)
}
return nil
}@naltatis hältst Du es für möglich, dass mit den Phasen irgendwas prinzipiell kaputt ist? |
|
@naltatis das sieht ähnlich aus wie #18606. Nur ist es hier v133- da war noch kein Config UI drin? Mit dieser Config ist der Charger ab Start immer auf 3p- was nicht sein sollte. network:
port: 7070
log: debug
interval: 3s
javascript:
- vm: shared
script: |
state = {
residualpower: 500,
pvpower: 0,
batterypower: 0,
batterySoc: 55,
gridpower: -1000,
loadpoints: [
{ enabled: false, vehicleSoc: 0, maxcurrent: 6, phases: 1, chargepower: 0 },
{ enabled: false, vehicleSoc: 22, maxcurrent: 0, phases: 3, chargepower: 0 }
]
};
function logState() {
console.log("state:", JSON.stringify(state));
}
meters:
- name: grid
type: custom
power:
source: js
vm: shared
script: |
state.gridpower = state.loadpoints[0].chargepower + state.loadpoints[1].chargepower + state.residualpower - batterypower - pvpower;
state.gridpower;
in:
- name: pvpower
type: float
config:
source: js
vm: shared
script: |
state.pvpower = 8000+500*Math.random();
state.pvpower
- name: batterypower
type: float
config:
source: js
vm: shared
script: |
state.batterypower = state.gridpower > 0 ? 1000 * Math.random() : 0;
state.batterypower
- name: pv
type: custom
power:
source: js
vm: shared
script: 0
- name: battery
type: custom
power:
source: js
vm: shared
script: state.batterypower;
soc:
source: js
vm: shared
script: |
if (state.batterypower < 0) state.batterySoc++; else state.batterySoc--;
if (state.batterySoc < 10) state.batterySoc = 90;
if (state.batterySoc > 90) state.batterySoc = 10;
state.batterySoc;
capacity: 13.4
batterymode:
source: js
vm: shared
script: |
1
- name: meter_charger_1
type: custom
power:
source: js
vm: shared
script: state.loadpoints[0].chargepower;
chargers:
- name: charger_1
type: custom
enable:
source: js
vm: shared
script: |
logState();
var lp = state.loadpoints[0];
lp.enabled = enable;
enable;
out:
- name: enable
type: bool
config:
source: js
vm: shared
script: |
if (enable) lp.chargepower = lp.maxcurrent * 230 * lp.phases; else lp.chargepower = 0;
enabled:
source: js
vm: shared
script: |
state.loadpoints[0].enabled;
status:
source: js
vm: shared
script: |
if (state.loadpoints[0].enabled) "C"; else "B";
maxcurrent:
source: js
vm: shared
script: |
logState();
var lp = state.loadpoints[0];
lp.maxcurrent = maxcurrent;
if (lp.enabled) lp.chargepower = lp.maxcurrent * 230 * lp.phases; else lp.chargepower = 0;
Phases1p3p:
source: js
vm: shared
script: |
logState();
lp.phases = phases
Tos: true
vehicles:
- name: vehicle_1
title: blauer e-Golf
type: custom
soc:
source: js
vm: shared
script: 10
capacity: 44
site:
title: Zuhause
meters:
grid: grid
pv: pv
battery: battery
loadpoints:
- title: Carport
charger: charger_1
mode: pv
meter: meter_charger_1
vehicle: vehicle_1 |
This was referenced Feb 5, 2025
andig
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Erwartet hatte ich ein Laden mit 3 Phasen, um möglichst schnell die Mindestladung zu erreichen.
Die Logs habe ich selektiv angefügt (wichtigen Einträgen mit Stichwort "phase", den Ladestart sowie die manuellen Eingriffe).
Bei Bedarf liefere ich gern weitere Logs nach.
Ergänzend sei noch angemerkt, dass letzten Woche Freitag (31.1.) ein Firmware-Updates meiner Wallbox erfolgt ist.
Möglicherweise ist durch den Hersteller-Support zuletzt am 3.2. ein Neustart der Wallbox durchgeführt worden -> ggf. haben sich dadurch unerwartete Konstellationen ergeben.
Steps to reproduce
[lp-1 ] DEBUG 2025/02/01 22:41:26 switched phases: 3p[lp-1 ] INFO 2025/02/02 08:50:49 start charging ->[lp-1 ] INFO 2025/02/02 16:37:30 stop charging <-[lp-1 ] DEBUG 2025/02/04 19:33:28 set phases: 0[lp-1 ] INFO 2025/02/04 19:45:51 car connected[lp-1 ] INFO 2025/02/04 19:46:11 start charging ->[lp-1 ] DEBUG 2025/02/04 19:46:31 detected active phases: 1p[lp-1 ] DEBUG 2025/02/04 20:15:47 set phases: 3[lp-1 ] DEBUG 2025/02/04 20:15:47 detected active phases: 1p[lp-1 ] DEBUG 2025/02/04 20:15:51 detected active phases: 1p[lp-1 ] DEBUG 2025/02/04 20:15:53 set phases: 1[lp-1 ] DEBUG 2025/02/04 20:15:55 set phases: 0[lp-1 ] DEBUG 2025/02/04 20:16:08 switched phases: 3pConfiguration details
Log details
What type of operating system or environment does evcc run on?
Windows
External automation
Nightly build
Version
0.133.0
The text was updated successfully, but these errors were encountered: