Closed feserdel closed 3 months ago
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.
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.
Thank you!!
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