Closed mavo closed 4 months ago
Check your DTU if the inverters limit > 0. If thas the case, wait until the hub delivers, if it doesnโt, itโs a zendure issue.
Inverter limit was set to 400, this was actually ongoing for couple of hours.
It now resolved itself... Strange. Anyway. Will close the ticket.
Thx for fast response.
It happens again - right now. Battery is full, but no power is delivered to home.
Are you running Hub2k? If yes, which firmware version do you run for battery and hub @reinhard-brandstaedter?
Apparently I only have to write a comment here and then it fixes itself ๐ค
Now, that this has recovered again another question - is it on purpose, to have 0-feed-in when battery is full and one is on pass-through? The app limits my inverter now to match the house consumption.
Yes, currently in BP it matches demand, thinking of changing that again.
To the original topic. We canโt influence what the hub is doong in BP itself, we can switch it to BP, buth what the hub is doing and delivering once switched depends on the hub.
Yes, currently in BP it matches demand, thinking of changing that again.
Make it configurable ๐ I know, one more config param makes applications mostly not more user friendly. But adds flexibility ๐
Yes, currently in BP it matches demand, thinking of changing that again.
Make it configurable ๐ I know, one more config param makes applications mostly not more user friendly. But adds flexibility ๐
I would also vote for WR > Max if Bypass = YES :-D
Another issue I just noticed... when BP is active and more power is needed than a panel on SF is producing, it looks like the information about the total power available is missing due to the effect that only the power of one panel is reported.
Another issue I just noticed... when BP is active and more power is needed than a panel on SF is producing, it looks like the information about the total power available is missing due to the effect that only the power of one panel is reported.
I saw the same. I think this is the transition phase between non-BP and BP. It can last a while, or at least it did for me lately. It actually improved (or it feels like it did - only had it one more time happening) after I switched to latest dev build + letting the app control BP manually. Then it happened "only" for ~15min instead of up to an hour previously. In the time, when only one input src actually reports something, it still does not deliver any power to the home. You can also see this in the "output to home", as this will sit at 0. You can see this also here, when the 2 lines match up there is no power added to the house from solar sources.
To compare - this was how it looked when BP was set to automatic without the app controlling it. It took ~45min to actually start to deliver power finally again.
I would also vote for WR > Max if Bypass = YES :-D
Latest dev now uses the maxInversePower from the hub. Which likely means full steam. However this will need more consideration as it could also mean trouble in case additional panels are connected to the inverter at the same time.
Another issue I just noticed... when BP is active and more power is needed than a panel on SF is producing, it looks like the information about the total power available is missing due to the effect that only the power of one panel is reported.
What do you mean by only the power of one panel is reported? Did you observe that the hubs solarInput (total power of both panels) is not correct?
I would also vote for WR > Max if Bypass = YES :-D
Latest dev now uses the maxInversePower from the hub. Which likely means full steam. However this will need more consideration as it could also mean trouble in case additional panels are connected to the inverter at the same time.
Ok, will try to check tomorrow, currently running on:latest (maybe that is already dev?)
Another issue I just noticed... when BP is active and more power is needed than a panel on SF is producing, it looks like the information about the total power available is missing due to the effect that only the power of one panel is reported.
What do you mean by only the power of one panel is reported? Did you observe that the hubs solarInput (total power of both panels) is not correct?
prior to bypass
after bypass (and limiting from your script)
so for my it looks like SF is only reporting 1 panel as solarpower
maybe this problem is gone with your current update
No, that is likely the "match to demand" in bypass mode. If you check your smartmeter reading it's likely hovering around 0 at this time?
Another issue I just noticed... when BP is active and more power is needed than a panel on SF is producing, it looks like the information about the total power available is missing due to the effect that only the power of one panel is reported.
What do you mean by only the power of one panel is reported? Did you observe that the hubs solarInput (total power of both panels) is not correct?
To me this sounds like what you can see in my first screenshot. (excerpt from it here)
Never gets boring with Zendure ;-) I've never seen this behavior ...
with the last update the behaviour in the bypass has changed, works as it should! :-) However, I have noticed that the "Switch" is not set correctly in the HA, but the status is set to bypass
It is not precisely as I want it. There could still be situations where it goes on/off too often. But we are close!
As this one is kinda old, I'll close it. Will re-open or use a new ticket, if it still exists in latest build - maybe its also something to contact zendure support about as it seem to only happen to me ๐ค
Hi @reinhard-brandstaedter,
for some reason there is no power delivered to my home, even tho the battery is full and bypass got enabled.
Here is some log output, do you have any idea what's going on?
Cheers, MaVo