Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Startup with Offline Wallbox(es) in EVCC #14474

Closed
pjohde opened this issue Jun 19, 2024 · 4 comments
Closed

Startup with Offline Wallbox(es) in EVCC #14474

pjohde opened this issue Jun 19, 2024 · 4 comments
Labels
wontfix This will not be worked on

Comments

@pjohde
Copy link

pjohde commented Jun 19, 2024

Is your feature request related to a problem? Please describe.
evcc fails to start if any of the connected charge points (Wallboxes) are offline. Currently, evcc waits for all Wallboxes to respond during the startup process. If one Wallbox is offline or unresponsive, evcc does not start and logs a fatal error message, then attempts to restart after a set period, but remains down.

Describe the solution you'd like
I would like evccto have the capability to start even if some of the Wallboxes are offline. Specifically, evcc should start without the offline Wallbox(es) and continue operating with the available Wallboxes. This would ensure that the charging system remains functional even if one or more Wallboxes are temporarily offline. A more resilient startup behavior would improve the reliability and user experience of evcc.

Describe alternatives you've considered
An alternative solution might be adding a feature where evccretries to connect to the offline Wallbox(es) in the background while remaining operational with the available Wallboxes.

Additional context
In the current scenario, the evcc logs the following fatal error when a Wallbox is offline:
[main ] FATAL 2024/06/19 11:30:35 cannot create charger 'EV_Box_Garage': cannot create charger type 'template': cannot create charger type 'ocpp': timeout [main ] FATAL 2024/06/19 11:30:35 will attempt restart in: 5m0s

@andig
Copy link
Member

andig commented Jun 19, 2024

On the otherhand side doing so would mean that the fauly box stays offline indefinitely. Sofar we have always opted for the seemingly safer path and try to restart instead. We're not planning to change this anytime soon.

@andig andig added the wontfix This will not be worked on label Jun 19, 2024
@pjohde
Copy link
Author

pjohde commented Jun 20, 2024

Wouldn't it be an option for evcc to start as soon as at least one wallbox is on? And for the other wallboxes, it could be monitored in the background to see if they respond.
This way, evcc would be operational, and if an inactive wallbox goes online, it would also change to active status in evcc.

@andig
Copy link
Member

andig commented Jun 20, 2024

Imagine 2 boxes. The car is connected to the flaky one. Restarting often can fix the problem. Now you don't restart and instead are happy with the box without vehicle. The car will not get charged. Does that sound good?

Imho the real question here is: why would the box not be available or become available when retrying? What is the actual use case? My 2 boxes have been running for 5 years without any single fault...

@naltatis
Copy link
Member

I've created a more general issue describing the desired behavior. I'll close this one as duplicate the the new #14496

@naltatis naltatis closed this as not planned Won't fix, can't repro, duplicate, stale Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants