Solar Production Issue since 28 August

Hi,

Seems similar to [(https://community.givenergy.cloud/d/6238-no-solar-production-is-this-an-inverter-issue)] but possibly not similar enough?!
Up until 28 August my (14) solar panels were working perfectly. However, since 13:00 on 28 August my solar panels have only been providing around 20w (virtually nothing) - power just dropped off to virtually nothing. Peak power should be around 5500w.... (all of my data comes from either the GivEnergy App and / or API)

Since 28 August I've had no solar power.

Any thoughts from the community on how to diagnose this?

I've restarted the Inverter. I have 2 Solar strings so don't think this is going to be a physical issue with cables to the panels and both Strings are showing the same issue.

Example data (a very slight consistent difference between string 1 and 2 but maybe rounding?):-

| Time                | String 1 V | String 1 A | String 1 W | String 2 V | String 2 A | String 2 W | Solar Generation |
|---------------------|------------|------------|------------|------------|------------|------------|------------------|
| 08/09/2025 15:18:00 | 110.1      | 0          | 1          | 305.7      | 0.1        | 19         | 20               |
| 08/09/2025 15:13:53 | 110.1      | 0          | 1          | 304.1      | 0          | 10         | 11               |
| 08/09/2025 15:13:42 | 110.2      | 0          | 1          | 304.7      | 0          | 36         | 37               |
| 08/09/2025 15:13:31 | 110.3      | 0          | 1          | 304.8      | 0          | 16         | 17               |
| 08/09/2025 15:13:20 | 110.3      | 0          | 1          | 305.5      | 0          | 5          | 6                |

GivEnergy are ignoring my requests for support (via WhatApp and support@givenergy.co.uk) - Any help you can provide would be much appreciated

Thanks
Steve

Further info. Inverter is GIV-HY5.0 and all lights are green.
Grid voltage looks to be stable at 242V (high grid voltage seemed to be the issue for the other thread I've referenced above but not for me)

Have you checked that Eco is enabled?

SweatyGoans I would try a reset to defaults of the inverter in the portal, and then go through and check that the settings are all as they should be.

Look back in the remote control history and see whether anything changed around the time your solar stopped working?

110 volts on string 1 is insufficient to start the inverter.

Thanks all. Some responses / updates:-
1) Yesterday afternoon I turned off battery, inverter, AC and DC isolators and turned all back on again - Briefly all was working properly again, until the sun went down... Then from today I have the same issue again.
2) Watcher - Yes, Eco is enabled
3) @geoffreycoan - Not done this yet but can try...
4) Rubikcube - Can you explain what you mean by this / the implication? Are you thinking there could be a physical issue with String 1? (String 1 has 6 panels, String 2 has 8. String 2 is in a slightly better place for solar but both Strings / all panels are on the same roof / pitch facing the same orientation)
Thanks
Steve

SweatyGoans Faulty panel on string 1 is what I'd suspect.

The inverter won't put a load on the string ("start") until the string voltage exceeds 120V.

Typically I'd expect to see 180V+ on a 6 panel string. 110V suggests only 3 are actually functioning so perhaps the third panel in the string is dead - that would stop the first two panels contributing.

The other potential "fault" is that the strings were configured as independent and have somehow become set to 1x2. There's a voltage/power limit per string so if all the panels were electrically on one string they'd potentially exceed that limit. What happens then I have no idea, perhaps one physical string gets shut down.

GivTCP will show the PV input mode and allow it to be changed, don't think anything else does.

Vestas - Thanks for useful info. Can't rule out a faulty panel for sure, not sure I can check without involving a solar electrician? I would be surprised if strings have been reconfigured as nothing / no-one has touched my setup as far as I know. If one string were faulty though, wouldn't I expect the other one (with more than half the panels) to still contribute more than half the PV Power? Seeing virtually nothing (15w to 20w) still.

SweatyGoans Installer should be your first call.

Vestas GivTCP will show the PV input mode and allow it to be changed, don't think anything else does.

I have been looking and I can’t find PV input mode in GivTCP (3.2) anywhere. It used to be there but I have a feeling it was deprecated in GivTCP v3 and no longer being populated so I deleted it from MQTT.

geoffreycoan I basically froze the GivTCP software at the point Paul Landregan put the fast response f/w on. There was no need to stay up to date as the inverter f/w wasn't going to change so I'm on 2.4.3.

Just coming back to original issue (and thanks for all the help / suggestions). I swapped String 1 and String 2 over - Same issue but zero reading now coming from String 2, not String 1 (in the App). So then disconnected String 2 (Originally String 1) from the inverter completely and I'm now getting a full reading from String 1 (Originally String 2). So to my mind this points clearly to a physical fault outside of the inverter. i.e. a fault with either wiring or panels on the string with 6 panels (originally String 1)- as Vestas suggested. Actually quite pleased - as my experience with GivEnergy Support suggested it would be very painful to get anything done if Inverter itself was faulty. Will bet my installer round....
Thanks All

SweatyGoans the negative side of both strings are physically connected inside the inverter at the PV isolator - hence how a fault on one string can pull both down.

[unknown] Have you looked at what your grid voltage is?

SweatyGoans Grid voltage looks to be stable at 242V (high grid voltage seemed to be the issue for the other thread I've referenced above but not for me)

The OP has already considered and dismissed grid voltage as the cause.

[unknown] Would be interesting to see what this issue turns out to be

SweatyGoans Would be interesting to see what this issue turns out to be