You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Predbat is putting itself into hold for car, even though the car isn't charging and there are no IGO slots planned let along currently active.
Expected behaviour
Predbat should be following it's normal plan.
Might have discovered the issue, I had the following commented out in my apps.yaml octopus_intelligent_slot: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching)' octopus_ready_time: 're:(time.octopus_energy([0-9a-z_]+|)_intelligent_ready_time)' octopus_charge_limit: 're:(number.octopus_energy([0-9a-z_]+|)_intelligent_charge_limit)'
Will report back if this does fix it. Currently it's not planning charge so I don't know for sure if it's sorted it.
If you have moved from predbat-led charging to iGo led charging then there are a number of reconfigurations you need to make to your predbat setup so that predbat takes the car charging slots from Octopus rather than plan them itself
Yes I've done all the others. It's been running fine all winter. I suspect because Predbat was planning charges during the night when IGO was. Now the sun has come out, predbat is planning more during the day so the issue has appeared.
This, plus our cars SOC isn't updating as fast (due to a number of reason, not needed for IGO) meant predbat wasn't seeing the car charged when it was.
Describe the bug
Predbat is putting itself into hold for car, even though the car isn't charging and there are no IGO slots planned let along currently active.
Expected behaviour
Predbat should be following it's normal plan.
Predbat version
v8.15.1 (Running on HA via Addon)
Environment details
Screenshots
Log file
predbat.log
Predbat debug yaml file
predbat_debug_16_40_00.yaml.txt
The text was updated successfully, but these errors were encountered: