Stefan/evcc-io
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

EEBUS: ignore EVSEs not providing current limits (#15299)

Browse source 
Some EVSEs using EEBUS sometimes do not provide any current charging limits and also do not provide valid ranges just ignore these scenarios and hope for the best.
This commit is contained in:
Andreas Linde 2024-08-08 18:57:55 +02:00 • committed by GitHub
parent 0de5261be8
commit 4bea3c7fcb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
charger/eebus.go
View file

@ -356,13 +356,13 @@ func (c *EEBus) writeCurrentLimitData(currents []float64) error {
_, maxLimits, _, err := c.uc.OpEV.CurrentLimits(evEntity)
if err != nil {
return errors.New("no limits available")
c.log.DEBUG.Println("no limits from the EVSE are provided:", err)
}
// setup the limit data structure
limits := []ucapi.LoadLimitsPhase{}
for phase, current := range currents {
if phase >= len(maxLimits) || phase >= len(ucapi.PhaseNameMapping) {
if phase >= len(ucapi.PhaseNameMapping) {
continue
}
@ -373,7 +373,7 @@ func (c *EEBus) writeCurrentLimitData(currents []float64) error {
}
// if the limit equals to the max allowed, then the obligation limit is actually inactive
if current >= maxLimits[phase] {
if phase < len(maxLimits) && current >= maxLimits[phase] {
limit.IsActive = false
}