Replies: 2 comments 4 replies
-
There's a clue in the documentation: To make Predbat planned car charging more accurate, configure the following items in apps.yaml: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Thanks, I appreciate the explanation. |
Beta Was this translation helpful? Give feedback.
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I use Octopus Intelligent Go, and I am a bit confused about the correct way to set up my car charging in Predbat.
Under "Planned Car Charging" it states the following:
_**To make Predbat planned car charging more accurate, configure the following items in apps.yaml:
car_charging_battery_size - Set this value in apps.yaml to the car's battery size in kWh which must be entered with one decimal place, e.g. 50.0. If not set, Predbat defaults to 100.0kWh. This will be used to predict when to stop car charging.
car_charging_limit - You should configure this to point to a sensor that specifies the % limit the car is set to charge to. This could be a sensor on the EV charger integration or a Home Assistant helper entity you can set as you wish. If you don't specify a sensor Predbat will default to 100% - i.e. fill the car to full.
car_charging_soc - You should configure this to point to a sensor (on the HA integration for your EV charger) that specifies the car's current charge level expressed as a percentage - it must NOT be set to a sensor that gives the car's current kWh value as this will cause Predbat to charge the car to an incorrect level. If you don't specify a sensor, Predbat will default to 0%.**_
Does all of this apply to both Octopus led charging and Predbat led charging? I can see a reference to using car_charging_soc further on in the docs under "Octopus Led Charging", so I have tried setting this in apps.yaml. I also tried setting up the battery size, but got a configuration error stating that a sensor was expected instead of a hard-coded number.
Beta Was this translation helpful? Give feedback.
All reactions