Repository navigation
Replies: 3 comments 25 replies
|
How is the failsafe timeout in the charger configured? 180 seconds? The behavior of the Wallbox seems strange, there is a lot of modbus communication within this timeframe, but still, it starts charging after they elapse. |
|
Sorry for not responding immediately. I am on vacation for some days. I can give it a try on 19.6.Am 17.06.2025 11:38 schrieb andig ***@***.***>:
If I can further assist here - your welcome.
@Myky09 did you test the PR?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi, I have a closely related setup: SolarEdge Home EV Charger (rebranded Keba P30) with a SolarEdge hybrid inverter, evcc 0.306.3 on a Raspberry Pi, BMW i5. I disabled the failsafe via UDP (failsafe 0 0 1) and blocked the charger's internet access in the router to cut the SolarEdge OCPP control. Despite this I still see the recurring "charger out of sync: expected enabled, got disabled" with the car staying in status B, and only a brief start/stop when it does engage. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I am new to evcc. Still setup etc. worked quite well. Then I turned on the failsafe mode on Keba P30x to reduce charging to minimum if connection from wallbox to evcc get's lost and get some strange issues. According to the implementation the code should support that setup. Extra go command is setup I guess to prevent the timer on the wallbox running into timeout.
After starting in PV mode with welcome charge enabled, the wallbox starts charging, then it stops as expected. PV output is too low to continue. But then exactly after 3 minutes I get an "out of sync error" and evcc restarts charging again. This continues until i explicitly stop charging. Still then the game "continues". The out of sync error repeats itself but evcc then starts and immediatly stops charging thus nothing happens.
I guess this also happens in other scenarios and is caused by the extra code triggered by the fail safe configuration.
evcc running as homeassistant addon
evcc version used: 0.203.5
can be verified also under windows
Actually, I wanted to create a bug report but that is always denied.
evcc_config.txt
trace.txt
All reactions