Solis S5-EH1P6K-L Faulty??

I am concerned that this new inverter is faulty and I'd like to ask for thoughts before I take it up with the supplier It appears to operate intermittently and often won't wake up in the morning until a load is switched on. I have 1800w of panels facing due south at 53 degrees tilt and a Pylon 4.8Kw battery and from observation I'll get around 500w out of it on a bright cloudy day and around 180w with heavy grey cloud. As you'll see the graphs are very jagged, this is one of my concerns as it not just the graphic as the monitor on the inverter shows all sensors at 0, ie no power being generated or consumed anywhere at these times. So the one dated 25/4 was a sunny day with some light cloud and at around midday it decided to start taking power from the battery, the following day it behaved as expected (apart from the jaggys). On both these days I had switched on some small loads (about 200w) around 8am. On the 29/4 I didn't get to the studio until late afternoon and as you can see It did not use any PV to charge the somewhat depleted battery until I turned on some loads and then it sprang into life, for a little while. And a similar story for the 30th. It certainly does not seem to operating correctly to me. What do you think?

Hi bazza14, I see this is an old query so you might not be monitoring it but did you ever find a solution to this? I have a grid tied S5 series and the power generated seems to intermittently drop to zero which sounds similar to your problem. It may be generating say 2500w on a bright cloudless day then suddenly drop to about 400w for a couple of seconds and build back up to 2500w. As far as I can tell it is the current reading that drops and pulls down the power generated rather than the voltage. Im wondering if it is a firmware issue?

Hi Corkster, I had the same problem, I managed to get it sorted by going into the storage mode on the unit and making sure that only Self-Use was on, by going into all the other options and making sure they were OFF. In may case, somehow, I had managed to get Feed In Priority and Self Use ON and I think this was causing the problem.