South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
What's the weather looking like today? Any hope for sun or grid all the way?Power can back on now. I lasted till 4am.
Charging up the batteries and getting the geyser warmed up. View attachment 1541197
Had the same issue, and also the graph is almost one hour behind. Support cannot explain it, suggested a firmware update which I did, and now seems to be fine.On SunSynk web/app portal.
Had another day with load number (from 11 June) disappearing from history the next day. It reports 0.1kWh, but I used about 28kWh for sure.
Anyone else?
View attachment 1540893
Grid all the way till middle of next week at least.What's the weather looking like today? Any hope for sun or grid all the way?
Thanks.Had the same issue, and also the graph is almost one hour behind. Support cannot explain it, suggested a firmware update which I did, and now seems to be fine.
Out of interest, what size is your solar array?Grid all the way till middle of next week at least.
I'll be lucky to get 5kWh from the solar panels per day for the next 7 days.
10.37kwpOut of interest, what size is your solar array?
Ok - little more than mine (9kwp) - at least I know I'm not the only one suffering with low yield at the moment.10.37kwp
My guess is that it is actually a server side problem, but there is a whole lot of new settings which may cause data mapping problems on older inverter versions.Thanks.
I see now that 13 and 14 June load data has also gone AWOL. So 11th gone; 12th there; 13,14 gone.
Nervous about doing firmware upgrade since everything else works perfectly fine.
SS 8kW Inverter with firmware as follows: M 6.0.2.1 / S 1.7.2.4 / C E.4.2.6
If yours was/is the same, then I might have to roll the dice.
They did elevate my access level a while ago to reduce data logging intervals to 60s, but cannot imagine that's got anything to do with this.
What's the recommended process way for firmware upgrade?
I need more than the 5400w panels I have. Thanks for the reminder lolA bit of sun through all the grey clouds View attachment 1541487
Afaik It's all going to depend on your battery % set on your system work mode. I guess 100% settings will guarantee only excess solar goes to non-essentials. But I know that's not what most people want.Anyone know the correct settings to allow excess solar to go to non-essentials but not battery to power them?
I'd rather Eskom power my non-essentials during low production days instead of pulling 3+kW from the battery and then topping it up in Eskom later... Hope that makes sense.
There's no way, unless you do it through aux...Anyone know the correct settings to allow excess solar to go to non-essentials but not battery to power them?
I'd rather Eskom power my non-essentials during low production days instead of pulling 3+kW from the battery and then topping it up in Eskom later... Hope that makes sense.
Yeah. Or with home assistant. As you say, it's not a native option on the inverterThere's no way, unless you do it through aux...
I also noted load figures going missing. My inverter is on the latest firmware so updating will not resolve the issue. The load values are recorded correctly through the day but at 00h00 the previous day's s load values goes whack. I think the issue is on the server side.On SunSynk web/app portal.
Had another day with load number (from 11 June) disappearing from history the next day. It reports 0.1kWh, but I used about 28kWh for sure.
Anyone else?
View attachment 1540893

How is it done on aux? My understanding here was if the SOC drops below the aux SOC then the aux is not powered (as opposed to powered from grid while everything else, ess & non-ess, runs on battery).There's no way, unless you do it through aux...
See today that load total for 15th is intact, but yesterday (16th) also missing.I also noted load figures going missing. My inverter is on the latest firmware so updating will not resolve the issue. The load values are recorded correctly through the day but at 00h00 the previous day's s load values goes whack. I think the issue is on the server side.
View attachment 1541929