Repository navigation
Replies: 1 comment
|
I have a slight update on the idea of the discharge lock feature. The discharge lock is really a feature targeted to a certain solution/integration. A broader usable feature would be the ability to define a range where a battery can operate. For instance, setting a range of -2500..2500 allows for (dis)charging at 2500W, while setting 100..1500 would allow only charging in that range. This feature would be useful to gain more control over the process:
I made some first steps here that I can test the next days: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
First of all thanks for this project! Running it for almost a year now...
I have an idea to add a so called discharge lock. This would be a toggle via mqtt that would prevent any discharging of the battery, but does allow charging.
The usecase:
I'm running EVCC to charge an EV with dynamic pricing. The batteries are set to zero-feed-in/self-consumption. When charging an EV it is not desired to use the batteries for this. EVCC has the ability to control batteries and set them to a "hold". So far, so good, this is already possible by setting 0W manual charging setpoint.
However, some EV charges only 3.3kW and when there is plenty of PV power, the remaining kWs (up to 4kW in my case) are being fed back into the grid. Practically giving it away...
The discharge lock would be useful here. When we're taking energy from the grid, the batteries won't discharge, but when there is sufficient PV, they will charge. A small detail is that we would need a "reservation" variable, leaving say 100W of export such that the EV solar charging can incrementally reclaim any solar charging.
What do you think of this feature? I would be willing to create a PR for it and test it.
(EVCC info: https://docs.evcc.io/en/features/battery/#discharge-lock)
All reactions