reinhard-brandstaedter
commented
5 months ago Your hub has probably set the max inverter input to 600W (inverter overload protection)?
Closed mavo closed 5 months ago
reinhard-brandstaedter
commented
5 months ago Your hub has probably set the max inverter input to 600W (inverter overload protection)?
mavo
commented
5 months ago The hub is set to 800w max output. At least this is what I configured when I initially set it up.
As said, as soon as I set the inverter to 100%, it will pass the full 800w. But then the app strikes back and regulates down again.
mavo
commented
5 months ago Here's a screenshot from the app settings.
From the logs you can also see, that the inverter is limited, not the hub output.
mavo
commented
5 months ago Hello @reinhard-brandstaedter,
was using the time while kids doing a nap to dig a bit. 🙈
I changed this line back to its original value, which is using max inverter power. I see the commit msg, which seems to manage concerns when the bypass is about to end.
To make sure its not the hub having set the 600W somewhere, I changed it back and since then the hub happily contributes 800W.
2024-04-06 11:31:16,965:INFO: SMT triggers limit function: -480.6 -> -490.8
2024-04-06 11:31:16,965:INFO: HUB: S:801.3W [ 799.4,795.2,773.8,800.3,810.5,810.4 ], B:100% (100|100), V:49.8V (49.9|49.8), C: 0W, P:True, F:0.0h, E:-1.0h, H:847W, L:800W
2024-04-06 11:31:16,969:INFO: INV: AC:801.5W, AC_Prediction: 801.2W, DC:843.6W, DC_prediction: 843.3W (0.0|0.0|427.3|416.4), L:1600.0W [1600W]
2024-04-06 11:31:16,971:INFO: SMT: T:ShellyEM3 P:-480.3W [ -479.2,-416.8,-482.0,-481.9,-482.2,-480.6 ] Predict: -490.8W
2024-04-06 11:31:16,974:INFO: Direct connected panels (0.0W) can't cover demand (310.4W), trying to get rest from hub.
2024-04-06 11:31:16,974:INFO: Checking if Solarflow is willing to contribute 310.4W ...
2024-04-06 11:31:16,974:INFO: Based on time, solarpower (801.3W) minimum charge power (0W) and bypass state (True), hub could contribute 800.0W - Decision path: 1.2.
2024-04-06 11:31:16,974:INFO: Hub should contribute more (800.0W) than what we currently get from panels (0.0W), we will use the inverter for fast/precise limiting!
2024-04-06 11:31:16,975:INFO: Hub has just recently adjusted limit, need to wait until it is set again! Current limit: 800, new limit: 800
2024-04-06 11:31:16,975:INFO: Current inverter AC output is higher than configured output limit (ac_limit), reducing limit to {inv_limit}
2024-04-06 11:31:16,975:INFO: Not setting inverter output limit as it is identical to current limit!
2024-04-06 11:31:16,975:INFO: Sun: 06:30 - 19:51 Demand: 310.4W, Panel DC: (0.0|0.0), Hub DC: (427.3|416.4), Inverter Limit: 1598.0W, Hub Limit: 800.0W
2024-04-06 11:31:27,028:INFO: SMT triggers limit function: -487.4 -> -506.7
2024-04-06 11:31:27,028:INFO: HUB: S:805.9W [ 795.2,773.8,800.3,810.5,810.8,814.1 ], B:100% (100|100), V:49.8V (49.9|49.8), C: 0W, P:True, F:0.0h, E:-1.0h, H:850W, L:800W
2024-04-06 11:31:27,032:INFO: INV: AC:805.4W, AC_Prediction: 806.6W, DC:847.7W, DC_prediction: 849.0W (0.0|0.0|429.3|418.4), L:1600.0W [1600W]
2024-04-06 11:31:27,034:INFO: SMT: T:ShellyEM3 P:-487.8W [ -416.8,-482.0,-481.9,-482.2,-480.6,-487.4 ] Predict: -506.7W
2024-04-06 11:31:27,038:INFO: Direct connected panels (0.0W) can't cover demand (299.9W), trying to get rest from hub.
2024-04-06 11:31:27,038:INFO: Checking if Solarflow is willing to contribute 299.9W ...
2024-04-06 11:31:27,038:INFO: Based on time, solarpower (805.9W) minimum charge power (0W) and bypass state (True), hub could contribute 800.0W - Decision path: 1.2.
2024-04-06 11:31:27,038:INFO: Hub should contribute more (800.0W) than what we currently get from panels (0.0W), we will use the inverter for fast/precise limiting!
2024-04-06 11:31:27,038:INFO: Hub has just recently adjusted limit, need to wait until it is set again! Current limit: 800, new limit: 800
2024-04-06 11:31:27,038:INFO: Current inverter AC output is higher than configured output limit (ac_limit), reducing limit to {inv_limit}
2024-04-06 11:31:27,039:INFO: Not setting inverter output limit as it is identical to current limit!
2024-04-06 11:31:27,039:INFO: Sun: 06:30 - 19:51 Demand: 299.9W, Panel DC: (0.0|0.0), Hub DC: (429.3|418.4), Inverter Limit: 1598.0W, Hub Limit: 800.0WIs the limitedRise function somehow holding itself back? To me, it looks like the app never sets the inverter to 100%, therefore, the hub reported solar input never goes up to the allowed max of 800W, therefore, the set limit function will never realize, that more power is actually available 🤔
reinhard-brandstaedter
commented
5 months ago Hi @mavo , the limited rise function is a "limited exponential growth" function which uses the max_inverter_limit setting as limit. In bypass mode this uses the current available solarinput and sets the inverter limit so that it should very close to that allow the solarinput to pass into the inverter AC output.
This example from your logs seems to pretty match this precisely:
2024-04-06 08:27:12,525:INFO: HUB: S:629.9W [ 629.3,628.7,630.6,630.1 ], B:100% (100|100), V:50.5V (50.5|50.5), C: 0W, P:True, F:0.0h, E:-1.0h, H:658W, L:800W
...
2024-04-06 08:27:12,534:INFO: Adjusting inverter limit from 629.9W to 635.4W
...
2024-04-06 08:27:12,534:INFO: Sun: 06:30 - 19:51 Demand: 497.3W, Panel DC: (0.0|0.0), Hub DC: (339.2|330.3), Inverter Limit: 1268.0W, Hub Limit: 800.0WThe inverter limit is set to 1268W (317W) which is actually higher than what the hub is currently reporting on solar input (629.9W), so in theory (keeping delays in reported data out of the calculation) the inverter will pass though everything it gets from the hub.
Now as with the nature of an exponential function the actual limit 800W (max_inverter_limit) is never precisely reached, maybe something like 799. And here comes the "top edge" that you are reporting in your last log into play: it's approx 800W the hub is feeding to the inverter. The hub's solarInput is slightly above 800W e.g. 805W, you can also see that the hub is not exactly feeding 800W to the inverter (the inverter is e.g. reporting 429.3W and 418.4W and the two y-cable-connected channels). In reality you are not missing any real power, it's all about the minimal skew in measuring and reporting. Additionally there is another difference in DC and AC (channels report DC, inverter limit is applied to AC)
What you can try is rising the max_inverter_limit to something like 820, that should push your limit on the inverter in bypass mode up.
mavo
commented
5 months ago Hey @reinhard-brandstaedter,
so I get what you explain on how it should work. But this does not match what I can see.
In the screenshot you can see the time when I used the rise function, the power was maxing at around 630w. When I modified the code to simply use max inverter power, it jumped to the expected ~800w.
So it looks to me as if something is keeping the inverter too much at pace so that it fails to grow...
MaVo
reinhard-brandstaedter
commented
5 months ago Also please note this typical bypass behavior: The hub usually "reduces" reported SolarInput before the bypass is enabled. Once the bypass is active it goes back up:
mavo
commented
5 months ago Also please note this typical bypass behavior: The hub usually "reduces" reported SolarInput before the bypass is enabled. Once the bypass is active it goes back up:
Good morning @reinhard-brandstaedter,
that's true, I noticed as well. But my bypass was active since around 9:45am.
Notice the hard drop around this time
The one short spike up to ~800 you can see once is where I was fighting the app to convince it to get to full steam.
reinhard-brandstaedter
commented
5 months ago Please set max_inverter_limit to 920, this will top you out at 800W with the current limit function on max input..
mavo
commented
5 months ago Please set max_inverter_limit to 920, this will top you out at 800W with the current limit function on max input..
Thx, will try this. Although it's hard to actually test because I need a very sunny day and bypass enabled. But I'll try anyway.
One question for this: As I still use my hms-1600-4t I double the value, meaning 1840, correct? Does this in any way allow an overpowering of the inverter, in case the house consumption is high whilst preparing lunch in combination with high radiation from the sun? 🤔
MaVo
reinhard-brandstaedter
commented
5 months ago No, keep it at 920 do not double it. This impacts the top off of the limit function and the per-channel input. In theory if you get 400W input per channel you will get a 1600W total output, but there is another safety that throttles the overall limit based on the AC output (if this goes over a safe zone). you can see this in your last log even.
mavo
commented
5 months ago Is this still required after the latest changes on master?
mavo
commented
5 months ago Seems to work without the setting to 920 now, thx!
Hello @reinhard-brandstaedter,
today I noticed a behaviour, I never saw before. My battery is full and I am in bypass mode. However, the SF-control app does limit my home output to ~600W (80% of inverter capacity).
When I disable the app and set the inverter to 100%, it will deliver the 100%. However, the app as soon as it runs will fight this again. Here's my config.
Any Idea why this is happening?
Cheers, MaVo