reinhard-brandstaedter / solarflow-control

A tool to automatically control Zendure's Solarflow hub with more flexibility to match home power demand
70 stars 12 forks source link

DEV: System leaving charge through however should not be the case #77

Closed tuxianerDE closed 11 months ago

tuxianerDE commented 1 year ago

The logs are indicated that path 3.2.2 is taken and thus leaving charge through, however criteria logically should not be met.

Note: We are in low light (low watt situation), direct panels <10

Actual situation should be:

solarFlow.log

reinhard-brandstaedter commented 1 year ago

"leaving charge through mode" is probably a bit misleading here. What happens is that, while the SolarInput is below the minimum reserved charge power (MINIMUM_CHARGE_LEVEL) it will not discharge from batteries even though leaving charge through. Assuming that throughout the day we still want to use the produced solar energy directly while using only the overproduction for charging (why store something - with losses - when we can make use of it directly) However, I agree in cases where additional panels are connected directly it would make more sense to use everything from the SF Input to charge and leverage the direct panels for household supply.

On the contrary the same principle would apply here: use as much as possible for direct consumption and only store overproduction, meaning also the SF input could supply to the current demand (without further discharging)?

tuxianerDE commented 1 year ago

True that last sentence is valid, i.e. take the direct panels (fully like in 3.2.1) and add anything above the minimum charge level from the SF to the house - if needed by the demand.

The current situation is that it will always follow path 3.2.2 which leads the system to limit itself to 0 completely instead of the smart combination of direct connected panels which we have in 3.2.1

I stopped the container today morning to see if the direct panels deliver (and they do around 40W) so in theory it suffices to let them through and regulate the solarflow down.

reinhard-brandstaedter commented 1 year ago

This commit should fix this behavior

tuxianerDE commented 1 year ago

pulled dev container. seems to operate now fine with decision path 3.2.2

solarFlowDev | 2023-10-20 13:50:25,851:INFO: Sun: 08:03 - 18:30, H_SM: [ 159, 160, 160, 160, 154], H_D: 250W, SF_S: 105W, I_DP: 95.9 (47.6W|48.3W), I_OP: 91.8W, SF_H: 0W, SF_B: 15% (13%|8%|24%), CH_T: off, charging: 97W => Limit: 0W - [ 0, 0, 0, 0, 0] - decisionpath: 3.2.2 solarFlowDev | 2023-10-20 13:50:25,852:INFO: Setting solarflow output limit to 0 W solarFlowDev | 2023-10-20 13:50:25,852:INFO: Setting inverter output limit to 210.0 W (105 x 1 / (2/4)