Loadpoint: release priority PV reservation when car reached charge goal (#31759)
This commit is contained in:
parent
3e15012186
commit
9ad5120c98
5 changed files with 50 additions and 12 deletions
|
|
@ -112,6 +112,8 @@ type API interface {
|
|||
EffectiveMinPower() float64
|
||||
// EffectiveMaxPower returns the max charging power taking active phases into account
|
||||
EffectiveMaxPower() float64
|
||||
// PvChargeStarting reports a PV loadpoint claiming surplus but not yet drawing it
|
||||
PvChargeStarting() bool
|
||||
// EffectivePlanStrategy returns the effective plan strategy
|
||||
EffectivePlanStrategy() api.PlanStrategy
|
||||
// PublishEffectiveValues publishes effective values for currently attached vehicle
|
||||
|
|
|
|||
|
|
@ -767,6 +767,20 @@ func (mr *MockAPIMockRecorder) PublishEffectiveValues() *gomock.Call {
|
|||
return mr.mock.ctrl.RecordCallWithMethodType(mr.mock, "PublishEffectiveValues", reflect.TypeOf((*MockAPI)(nil).PublishEffectiveValues))
|
||||
}
|
||||
|
||||
// PvChargeStarting mocks base method.
|
||||
func (m *MockAPI) PvChargeStarting() bool {
|
||||
m.ctrl.T.Helper()
|
||||
ret := m.ctrl.Call(m, "PvChargeStarting")
|
||||
ret0, _ := ret[0].(bool)
|
||||
return ret0
|
||||
}
|
||||
|
||||
// PvChargeStarting indicates an expected call of PvChargeStarting.
|
||||
func (mr *MockAPIMockRecorder) PvChargeStarting() *gomock.Call {
|
||||
mr.mock.ctrl.T.Helper()
|
||||
return mr.mock.ctrl.RecordCallWithMethodType(mr.mock, "PvChargeStarting", reflect.TypeOf((*MockAPI)(nil).PvChargeStarting))
|
||||
}
|
||||
|
||||
// SetBatteryBoost mocks base method.
|
||||
func (m *MockAPI) SetBatteryBoost(enable bool) error {
|
||||
m.ctrl.T.Helper()
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue