Does anyone have any ideas as to why the inverter is drawing from the grid to cover the house load rather than use the battery? For some reason the battery is only covering 233W. It did the same thing two nights ago. Attached a couple of pics for reference. It’s a gen 2 inverter and and 9.5kW battery. First time poster so shout for info I’ve missed!
No, the charge and discharge are both set to 3600W…
Thinking about it, it’s been since I updated the firmware on Wednesday night it so there’s the likely culprit. Is it a ‘send support a ticket’ job or is there a more immediate nudge (restart?) that I can do?
We are experiencing a similar problem, where the house is drawing from the grid in the evening rather than the battery even when times are scheduled and the battery is full. In addition, the full battery is only discharging to the grid in the evenings and not to home consumption. Have tried all the settings including dynamic which then doesn't discharge the battery at all. Am also a first time poster so grateful to hear any ideas.
I think eco is off, but it says it is on. I had same issue.
From the web portal, my inverter page, settings tab, try this
Eco slider to off. Save. Wait a few seconds. Eco slider to on. Save.
Thanks for the tips! Tried both of those- unfortunately the battery is still being throttled to 384-385W and the rest is being imported…
So I reset to default settings again and also changed the timed charge settings back to 00:00 (for some reason these didn’t change with the reset) and it seems to be working normally. Timed charge has been switched off the whole time so I didn’t think those settings would’ve made a difference but something’s clicked. Just glad to have things back even if my zero import streak is now scuppered!
Thanks, will try that.
I had similar problem batteries stopped covering load at night and sat idle . I found my grid voltage was too high and had it lowered by DNO this seems to have cured my problem .
I have been using Octo R&D scheduler for months for off peak charge and approx. 50% peak discharge. I dont play with % settings but just discharge from 16:00 to 18:00. I dont use all 3 hours as I want to keep 50%
2 hours at 2.6kW is approx. 50% of 9.5kWhr battery. What is left gets me though to 2 am.
At 18:00 Octo issues a command to the inverter to go to Idle. (back to Eco)
This has been working for for months.
Since the battery firmware update, Octo still issues the same command at 18:00, I can see in the inverter Remote Control history that ECO has been set, but at 18:00 the inverter starts charging the battery from grid rather than using the 50% in the battery to power the house.
If I restart the inverter, it reboots and comes back in Eco but uses the battery rather than grid.
Strange!!
I have a similar issue, if there is even 1W coming from solar (such as in early evening before the sun goes fully down) then the battery discharge seems limited to about 550W.
As soon as the solar hits 0 its able to discharge at the full 3.5KW.
apc
Does the new firmware for the BMS fix this issue? I can get round it by disabling TIGO optimisers so I get zero PV but of course this is a short term solution.
Today I have turned off battery. It is practically full. I’m guessing as it approaches 100% it charges at a lower rate but somehow this seems to affect the PV generation. I had around 2kW PV and as soon as I turned off battery it jumped to 3.5kW - same blue sky. Usually it goes down to less that 500W until I turn off TIGO via fuse. Does firmware upgrade fix this? Or do I need inverter upgrade? I am on Gen 2 5kW inverter v906, 8.2kWh battery v307. Any feedback would be great. It’s ironic that a blue sky means I have to keep an eye on it! Cloudy days no problems as battery not full! Cheers, Dom
Dom66 sorry I seem to have got 2 issues mixed together.
Does the new firmware for BMS fix either of these issues?
I had a similar issue recently whwn my system went from working normally to doign the same thing and my supplier took up the case the GE and reported that they had made some chnages (don't know what was changed). But, whaterver they did it sorted it out and is back to normal. This happend before the latest 3012 firmware was out.