Behaviour of the service "Forcible Charge (to a SoC level)" ? #553
Replies: 1 comment
-
I have exactly the same question, even though I don't have a boiler but an electric car that I want to charge during night. Looking at it again, it might be smarter to use the service "Huawei Solar: Set Fixed Charge Periods" instestead of "Huawei Solar: Set TOU Periods". I might give it a try it in the future. Pls. keep me updated how you solve it! |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm really enjoying this integration. Kudo's to the authors(s)
After playing around with some nice dashboards, I would now like to control the charging behaviour of my battery.
During winter, my solar production is not sufficient and so I would charge my 5KWh battery during the night (=cheaper) for discharge during the day. I also own an electric waterboiler (1.8KW) that I charge at night in winter (during day in summer) This one is controled via a Tuya switch.
I have 3 automations running:
Now here comes the question.
Resulting behaviour:
(see picture at the bottom)
I was hoping that the service "Forcible Charge to a SoC level" would keep the battery charged at SOC level and the boiler would charge from the grid (iso battery) as long as forcible_stop is not called.
I know I can reverse the order to solve my particular problem but this question is really about understanding the forcible service call behaviour as the documentation is not fully explicit about this: https://github.com/wlcrs/huawei_solar/wiki/Force-charge-discharge-battery
Beta Was this translation helpful? Give feedback.
All reactions