[FEATURE] Target SOC reached by end of day for morning consumption

[TobiS87]

Area of the proposal

Energy management or control strategy

What problem would this solve?

The predictive charging system currently always nets at 0 - so it calculates to use all predicted household consumption either by smart charging or solar energy. It does that for the calculation period from 0:05 am to 0:05 am (as far as I can see).

For most users in the summertime grid electricity prices could be cheapest in the evening (when there is a lot of solar energy being pumped in the grid). The predictive charging calculates to have 0% SOC at 0:05am. Therefore the household consumption has to be provided by from grid energy for the current (oftentimes expensive) grid energy prices.

Proposed solution

Omnibattery could provide a target SOC slider 0-100% which sets a target for the predictive charging system to reach by the end of it's cycle to account for the morning household consumption.

So two solutions: Omnibattery could calculate these values at a fixed time (e.g. still 0:05 am) but would set the "net at 0" timeframe differently (maybe at 13:00 when oftentimes solar production ramps and energy prices are low) OR provide a SOC slider for the user which will guarantee that the battery is at that SOC by the time of calculation so the calculation (which takes battery energy into account) takes this energy into account already for the daily net 0 calculation. This would help in situations where energy need and energy production are very asynchronous. (Solution 2 seems to be the more practical solution)

Example use case

When solar production is high and energy prices are low the system would charge the battery fully and also use alle the energy for all appliances which need energy at that time. But it would also take the energy used at the next morning (when production is low AND prices are high) into account with the provided target SOC so the user reaches higher autarky.

Who would benefit from this?

Most Omnibattery users

Alternatives or workarounds

There is no workaround for that right now. Maybe a complicated automation which uses manual melde but thats completely against the integrations logic.

Additional context

No response

Confirmations

• I searched existing discussions and did not find the same proposal.
• This is a general feature idea, not a request to support a new battery brand or model.
• I understand that community interest and technical feasibility influence prioritization, and that no delivery date is guaranteed.
• I removed passwords, tokens, API keys, complete serial numbers, IP addresses, and other sensitive information.

[github-actions[bot]]

Thanks for the suggestion! 🙌

Here's how this works:

• Vote by clicking 👍 on the original post — not in the comments
• The more votes an idea gets, the higher it moves in the priority queue
• I review feature ideas periodically and implement the ones that benefit the most users

If your idea is very specific to your setup, it may not make it into the core integration — I'll try to suggest a workaround in that case.

Feel free to discuss details or alternatives below.