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

Huawei only discharge when discharge_rate: is popuated with + value #1962

Open
JohanAlvedal opened this issue Feb 4, 2025 · 0 comments
Open

Comments

@JohanAlvedal
Copy link

JohanAlvedal commented Feb 4, 2025

I thought we should take another look at the Huawei inverter.
Right now, I'm running my own automations to control charging, etc., using predbat.status, but a step in the right direction would be to implement charge_rate: and discharge_rate:.

I'm running my inverter in "Maximise Self Consumption" mode, which means that if, for example, the battery is at 50% and charge_rate: is set to 5000, then with excess solar production, the battery would charge (demand).

Similarly, if discharge_rate: is set to 5000, the battery would discharge if the house needs the power (demand).

This means that if the battery should not discharge—such as in the states "Hold charging," "Freeze charging," "Hold for car," or "Hold exporting"—then discharge_rate: must be 0.

charge_rate: should only be 0 when the status is "Freeze charging" or "Hold charging."

Additionally, even if the following action is sent:

action: huawei_solar.forcible_charge
data:
  duration: 60
  power: 1000
  device_id: 6893ee838a0972bd3e50d9e0faa0ba5a

Furthermore, number.battery_maximum_charging_power must be set to the desired power value (e.g., XXXXw), otherwise, nothing will happen.

When using forcible_charge, for example at night, discharge_rate: must be set to 0. Otherwise, the battery will immediately discharge, counteracting the charging process.

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