Skip to content
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

Solaredge hold for car and freeze charge/discharge #1688

Open
PieBeard opened this issue Dec 4, 2024 · 0 comments
Open

Solaredge hold for car and freeze charge/discharge #1688

PieBeard opened this issue Dec 4, 2024 · 0 comments

Comments

@PieBeard
Copy link

PieBeard commented Dec 4, 2024

Is your feature request related to a problem? Please describe.
With a SolarEdge system when Predbat plans to hold charge for car what actually occurs is that the battery is discharged into the car and then as the SOC drops the plan reevaluates and charges the battery more increasing cycles on the battery.

Describe the solution you'd like
Whilst trying to work out some automations and for a backup to Predbat not charging properly related to Issue #1632 I've found that you can prevent battery discharge by selecting other options from the entity select.solaredge_i1_storage_command_mode (mine is called select.solaredge_multi_i1_storage_command_mode)

by selecting:
"Solar Power Only (off)" battery charge and discharge is turned off and the house will run of grid or solar power
"Charge from Clipped Solar Power" and the battery will only charge from excess solar above the inverters capacity this seems to draw power for the house from the grid with about 40w coming from the battery, nothing much really.
"Charge from Solar Power" is any excess solar the house isn't using is used to charge the battery and when house load is above Solar power it draws from the grid with only about 40w coming from the battery again.

So in essence the Hold for Car could select any of these and they could be used for the equivalent of freeze charging too.

Just a note that in SolarEdge Systems there is a default mode which can be set and is usually maximise self consumption. The timeout for this is usually set at 3600s from when the service selection changes the storage_command_mode. Given that the SolarEdge Modbus Multi is a local connection there is no risk of excess API calls and so service calls at every slot even if there is no change in what it is doing helps prevent this automatic reset to the default mode.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant