We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently Huawei allow read and control (write) Forcible Charge MODBUS register Address 47100.
But the integration only allows write via services (huawei_solar.forcible_charge and huawei_solar.forcible_charge_soc).
I have an automation to start forcible charge under certain circumstances (eg when energy is cheap at night), but is impossible to know when ends.
Also, is necessary to check if another forcible charge is ongoing before start new forcible charge cycle.
For this reason it will be good to read the state of forcible charge register to a sensor, and enable automation management.
The text was updated successfully, but these errors were encountered:
Implemented in in v1.4.0. You can use the state attributes of the new sensor to retrieve different properties of the forcible (dis)charge function.
Sorry, something went wrong.
Thank you!!
No branches or pull requests
Describe your feature request
Currently Huawei allow read and control (write) Forcible Charge MODBUS register Address 47100.
But the integration only allows write via services (huawei_solar.forcible_charge and huawei_solar.forcible_charge_soc).
I have an automation to start forcible charge under certain circumstances (eg when energy is cheap at night), but is impossible to know when ends.
Also, is necessary to check if another forcible charge is ongoing before start new forcible charge cycle.
For this reason it will be good to read the state of forcible charge register to a sensor, and enable automation management.
Proper usage
The text was updated successfully, but these errors were encountered: