evcc: go-e charger - 1p setting ignored since 0.112
Describe the bug
I am having a “classic” go-e charger, which is physically connected on 3phases, but I am using a 1p charging cable so to being able to load solar power with low production in winter.
Therefore I have hardcoded the loadpoint to “1 phase” and it was working fine until the recent update.
I suppose that this PR breaks it: https://github.com/evcc-io/evcc/pull/5764 by overriding the loadpoint setting with something derived from connected voltages.
Steps to reproduce
- Start evcc in “pv” mode with loadpoint 1p
- Check the logs
Configuration details
loadpoints:
- title: go-e # display name for UI
charger: goe # charger
mode: pv
phases: 1 # ev phases (default 3)
enable: # pv mode enable behavior
delay: 30s # 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: 10m # threshold must be exceeded for this long
threshold: 500 # maximum import power (W)
Log details
Startup:
Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main ] INFO 2023/02/06 09:29:30 evcc 0.112.4
[main ] INFO 2023/02/06 09:29:30 using config file: /config/evcc.yaml
[lp-1 ] INFO 2023/02/06 09:29:30 loadpoint 1:
[lp-1 ] INFO 2023/02/06 09:29:30 mode: pv
[lp-1 ] INFO 2023/02/06 09:29:30 charger: power ✓ energy ✓ currents ✓ phases ✗ wakeup ✗
[lp-1 ] INFO 2023/02/06 09:29:30 meters: charge ✓
[lp-1 ] INFO 2023/02/06 09:29:30 charge: power ✓ energy ✓ currents ✓
[lp-1 ] DEBUG 2023/02/06 09:29:30 phase timer inactive
[lp-1 ] DEBUG 2023/02/06 09:29:30 pv timer inactive
[lp-1 ] DEBUG 2023/02/06 09:29:30 charge power: 0W
[lp-1 ] DEBUG 2023/02/06 09:29:31 charge voltages: [223 220 223]V
[lp-1 ] DEBUG 2023/02/06 09:29:31 detected connected phases: 3p
[lp-1 ] DEBUG 2023/02/06 09:29:31 charge currents: [0 0 0]A
[lp-1 ] DEBUG 2023/02/06 09:29:31 charger status: B
[lp-1 ] INFO 2023/02/06 09:29:31 car connected
[lp-1 ] DEBUG 2023/02/06 09:29:31 pv timer elapse
[lp-1 ] DEBUG 2023/02/06 09:29:31 pv timer inactive
[lp-1 ] DEBUG 2023/02/06 09:29:31 pv charge current: 2.3A = 0A + 2.3A (-1590W @ 3p)
[lp-1 ] DEBUG 2023/02/06 09:29:31 pv enable timer reset
[lp-1 ] DEBUG 2023/02/06 09:29:31 pv timer inactive
After manual switch to "minpv" mode, the problem fixes itself, as it detects that only 1p is working:
[lp-1 ] DEBUG 2023/02/06 09:29:51 set charge mode: minpv
[lp-1 ] DEBUG 2023/02/06 09:29:51 charge power: 0W
[lp-1 ] DEBUG 2023/02/06 09:29:51 charge voltages: [224 219 222]V
[lp-1 ] DEBUG 2023/02/06 09:29:51 detected connected phases: 3p
[lp-1 ] DEBUG 2023/02/06 09:29:51 charge currents: [0 0 0]A
[lp-1 ] DEBUG 2023/02/06 09:29:52 charger status: B
[lp-1 ] DEBUG 2023/02/06 09:29:52 pv charge current: 2.21A = 0A + 2.21A (-1527W @ 3p)
[lp-1 ] DEBUG 2023/02/06 09:29:52 max charge current: 6A
[lp-1 ] DEBUG 2023/02/06 09:29:52 charger enable
[lp-1 ] DEBUG 2023/02/06 09:29:52 wake-up timer: start
[lp-1 ] DEBUG 2023/02/06 09:30:00 charge power: 1350W
[lp-1 ] DEBUG 2023/02/06 09:30:01 charge voltages: [223 220 221]V
[lp-1 ] DEBUG 2023/02/06 09:30:01 detected connected phases: 3p
[lp-1 ] DEBUG 2023/02/06 09:30:01 charge currents: [6 0 0]A
[lp-1 ] DEBUG 2023/02/06 09:30:01 charger status: C
[lp-1 ] INFO 2023/02/06 09:30:01 start charging ->
[lp-1 ] DEBUG 2023/02/06 09:30:01 pv charge current: 6.2A = 6A + 0.204A (-141W @ 3p)
[lp-1 ] DEBUG 2023/02/06 09:30:01 max charge current: 6A
[lp-1 ] DEBUG 2023/02/06 09:30:03 set charge mode: pv
[lp-1 ] DEBUG 2023/02/06 09:30:03 charge power: 1330W
[lp-1 ] DEBUG 2023/02/06 09:30:03 charge voltages: [222 221 222]V
[lp-1 ] DEBUG 2023/02/06 09:30:03 detected connected phases: 3p
[lp-1 ] DEBUG 2023/02/06 09:30:03 charge currents: [5.9 0 0]A
[lp-1 ] DEBUG 2023/02/06 09:30:03 detected active phases: 1p
[lp-1 ] DEBUG 2023/02/06 09:30:03 charger status: C
[lp-1 ] DEBUG 2023/02/06 09:30:03 pv charge current: 6.87A = 6A + 0.867A (-200W @ 1p)
[lp-1 ] DEBUG 2023/02/06 09:30:03 max charge current: 6A
What type of operating system are you running?
Docker container
Version
0.112.4
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (10 by maintainers)
Super dass wir eine Lösung gefunden haben ohne den anderen Anwendern die automatische Umschaltung weg nehmen zu müssen 😃
@premultiply I disagree insofar as that it is also the phases the charger (!) will use for charging. We have not considered the cable scenario. We may of course chose to ignore it.
Optionally using a 1p cable is a perfectly viable scenario that the detection is breaking. Even if user sets
1
on loadpoint (which is correct for the cable) we would change that to3
which is not what will happen. Also, we don’t have an API for setting the value on vehicle level, so we’re forcing a wrong update on the user.