reinhard-brandstaedter / solarflow-control

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

Inverter set to negative value #219

Closed mavo closed 5 months ago

mavo commented 5 months ago

Hi @reinhard-brandstaedter,

only saw it once - and it seem to had no effect on the actual power of the inverter, but still want to let you know. For a reason, the app determined an inverter limit of -4 is a good value to use... I guess some calculation went south.

2024-04-17 12:24:44,296:INFO: HUB: S:798.4W [ 759.9,759.9,758.5,778.6,790.0,798.4 ], B:100% (100|100), V:51.0V (51.0|50.9), C: 0W, P:True, F:0.0h, E:-1.0h, H:840W, L:800W
2024-04-17 12:24:44,299:INFO: INV: AC:803.9W, AC_Prediction: 724.1W, DC:846.1W, DC_prediction: 762.2W (0.0|0.0|427.9|416.6), L: 0W [1600W]
2024-04-17 12:24:44,301:INFO: SMT: T:ShellyEM3 P:-464.2W [ -409.7,-409.7,-448.8,-453.4,-452.2,-470.4 ] Predict: -319.7W
2024-04-17 12:24:44,301:INFO: Direct connected panel are producing 0.0W, trying to get 321.9W from hub.
2024-04-17 12:24:44,301:INFO: Adjusting inverter limit from 798.4W to 798.7W
2024-04-17 12:24:44,301:INFO: Based on time, solarpower (798.4W) minimum charge power (0W) and bypass state (True), hub could contribute 798.0W - Decision path: 1.1.
2024-04-17 12:24:44,301:INFO: Not setting solarflow output limit to 800.0W as it is identical to current limit!
2024-04-17 12:24:44,301:INFO: Solarflow is willing to contribute 399.0W of the requested 321.9!
2024-04-17 12:24:44,302:INFO: Current inverter AC output (803.9) is higher than configured output limit (800), reducing limit to -4
2024-04-17 12:24:44,302:INFO: Not setting inverter output limit as it is identical to current limit!
2024-04-17 12:24:44,302:INFO: Grid feed in from unknown: 480.4!
2024-04-17 12:24:44,302:INFO: Sun: 06:05 - 20:10 Demand: 321.9W, Panel DC: (0.0W), Hub DC: (802.3W), Inverter Limit: -4.0W, Hub Limit: 800.0W
2024-04-17 12:24:44,302:INFO: SMT triggers limit function: -452.2 -> -470.4: executed
2024-04-17 12:24:44,305:INFO: SMT triggers limit function: -452.4 -> -470.1: skipped
2024-04-17 12:24:44,309:INFO: SMT triggers limit function: -452.5 -> -469.8: skipped
2024-04-17 12:25:21,216:INFO: Battery is full: 100
2024-04-17 12:25:21,217:INFO: Reading last full time: 2024-04-17 12:25:21
2024-04-17 12:25:21,218:INFO: Reading battery target mode: discharging

Cheers, MaVo

mavo commented 5 months ago

Ah while I just see it again, there is a log error in the line(s)

2024-04-17 12:24:44,301:INFO: Not setting solarflow output limit to 800.0W as it is identical to current limit!
2024-04-17 12:24:44,301:INFO: Solarflow is willing to contribute 399.0W of the requested 321.9!

Solarflow actually is willing to deliver the full power, but as it seems to log the value being used for calculation (value * output channels) its reporting always half of the energy (for me).

Only cosmetic one, so nothing to worry.

reinhard-brandstaedter commented 5 months ago

Did the -4 maybe happen right after start?

2024-04-17 12:24:44,299:INFO: INV: AC:803.9W, AC_Prediction: 724.1W, DC:846.1W, DC_prediction: 762.2W (0.0|0.0|427.9|416.6), L: 0W [1600W]

This doesn't seem to be correct, the inverter absolute limit is reported as 0 (and that is taken for the calculation of the -4W). However your inverter just puts out 803W so the reported limit can't be 0. I begin to feel your DTU is not reporting data correct or it's lost somewhere....

reinhard-brandstaedter commented 5 months ago

Ah while I just see it again, there is a log error in the line(s)

2024-04-17 12:24:44,301:INFO: Not setting solarflow output limit to 800.0W as it is identical to current limit!
2024-04-17 12:24:44,301:INFO: Solarflow is willing to contribute 399.0W of the requested 321.9!

Solarflow actually is willing to deliver the full power, but as it seems to log the value being used for calculation (value * output channels) its reporting always half of the energy (for me).

Only cosmetic one, so nothing to worry.

Yes, that has been fixed in the log message already.

mavo commented 5 months ago

It did correct itself. Maybe it really was the DTU reporting something weird. It did not happen directly after start, was a couple of minutes after. But hey ho, nothing happened. I'll check if it happens again -> closed for now.