-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Allow for different types of optimisation #980
Comments
I like the idea :) Do you know how you can determine 'greenest' on the grid inside HA? |
Yes I thought about using Octopus' greenness forecast - currently I'm using the National Grid's Carbon Intensity API which publishes regional half-hourly carbon intensity estimates, which could work nicely with Agile. I've integrated into HA using this guide: https://www.speaktothegeek.co.uk/2023/05/local-uk-grid-carbon-intensity-in-home-assistant/ |
I found this integration that might help: https://github.com/jfparis/sensor.carbon_intensity_uk |
The forecast part is now on main using the HA integration for national grid. Optimisation for carbon will be added soon |
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
As we move into the summer, predbat wants to charge my battery up cheaply (usually in the early morning), and then export as much of my solar as possible. Although this usually minimises my effective energy cost (on Octopus Agile tariffs), I would like to self-consume my solar as much as possible - for example, letting the solar panels charge up the battery in the early morning. Even if this isn't the most cost effective idea, it is likely the most 'green' energy I can use.
It would be great to have a new 'select' input or 'boolean toggles' where I could choose between the following algorithim optimisations:
If these were boolean toggles for the three options, I could then pick and choose my desired 'blend' of optimisations. If it is a select input that I choose between the three, then I was thinking that self-consumption of solar would be priority but the algorithm would still buy energy when it is greenest, and cheapest, whilst keeping the battery charged for the evening (i.e. a rainy summer day).
Describe alternatives you've considered
I've considered using expert mode to tune the algorithm for the above, but ideally this would be a feature of predbat that I can use to pick and choose some defaults. This would make it easier when moving from winter, into spring and summer. Please let me know if you have ideas on how I could use expert mode to achieve this though!
Additional context
N/A
The text was updated successfully, but these errors were encountered: