Ron responded very promptly regarding my GivEnergy battery issue, his knowledgeable diagnosis was spot on and resolved the issue on first attempt. Would recommend to any and all.
Simon Hill · May 2026
Field note · Case study · FoxESS · May 2026
Solar Batman FoxESS CODE-240 fixed in 30 minutes
Andrew's FoxESS hybrid threw CODE-240 the day his second battery was bolted on. The front-panel code pointed at a CT clamp fault. It wasn't. Here is what was really wrong, and how it was fixed without anyone leaving a desk.
- Real customer fault
- Fixed inside 30 minutes
- No site visit
Got a code that does not add up?
CODE-240, BMS errors, system refusing to start after firmware or battery work — most of these are remote-fixable once the real fault is named. Start a free diagnostic.
Book your free diagnosticFoxESS support hubMy Givenergy battery stopped working nearly a month ago. After unsuccessfully reaching out to my installer, who looks like he's also busted, I found Solar Tech Support on a Google search. They fixed my issue in a couple of hours. Any frustrated Givenergy customers, I highly recommend these guys.
Sarma Amirapu · May 2026
Absolutely wonderful support. I have a GivEnergy system that was installed in 2022, and a firmware update was flagged in the app, so I proceeded to update the software .... and immediately regretted it, as my inverter came up with an error, and was not working at all! With no GivEnergy support available, and my installer saying there was nothing he could do, I googled help, and found Ron. What a stroke of good luck! Submitted an on line enquiry late morning, and received phone call just after 5 pm, and later that evening Ron was able to supply me with old firmware no longer available on the GivEnergy web site. I was then able to update the firmware using a GivEnergy youtube video as reference, and hey presto the system was back up and running. One further slight adjustment by Ron and we are back normal. What a relief. I have no hesitation in recommending Solar Tech Support if you have a problem. Great service! And if you are a GivEnergy system owner, whatever you do, DO NOT UPDATE FIRMWARE!
Neill Ginn · Jul 2026 Google
Ron very quickly diagnosed what was wrong with my GivEnergy system. Unfortunately the kit has died after only 3.5 years of use-which is quite sad and timing couldn’t be worse with GivEnergy gone bust. Ron gave me advise on how to handle this with my installer. I’m hoping they’ll be forthcoming, but if they aren’t i now have a good idea how to deal with that. Thanks a lot Ron!
Dennis Koenen · Jul 2026 Google
Excellent response to diagnose a problem on our SolarEdge installation. Kept us informed at every step. Diagnosis quickly completed and solution implemented.
Les Bennett · May 2026
Had a fault on a GivEnergy AC coupled 3kW home battery and was getting no joy from multiple companies I contacted, as well as the original installer. Contacted Solar Tech Support and they sorted it really quickly, now working perfectly again, can’t recommend them highly enough, professional and very responsive!
John Jones · Jul 2026 Google
A man called Andrew pinged me on WhatsApp last week. His FoxESS hybrid was throwing CODE-240 and refusing to start. He'd just had an extra battery bolted onto the existing pack — but the installers couldn't get the system going — and the inverter had taken one look at the new hardware and shut the entire stack down.
CODE-240 is one of those error codes that points you in the wrong direction.
The fault that wasn't a CT clamp
Open the FoxESS service manual and CODE-240 reads current sensor abnormality — i.e. a CT clamp fault. So your first instinct is to check the CT connections at the inverter. Which is exactly the trap. Because when the inverter throws CODE-240 immediately after a battery pack change, the CT clamp is almost never the problem.
The inverter is.
Why CODE-240 leads you the wrong way
The full chain looks like this. When a FoxESS hybrid boots, it interrogates every battery pack on the BMS bus, checks their firmware revisions, and confirms the combination is one it has seen before. If a new pack ships with a firmware version the inverter has never met — or a slightly newer one than the older packs already there — the inverter refuses to commission.
You don't get an honest error like battery firmware mismatch. You get CODE-240. Same code path, different root cause. The CT-clamp message is the fallback the inverter throws when it can't tell you what is really wrong. The same trap shows up across other brands too — see how firmware updates break things for the wider pattern.
The honest answer is rarely on the front panel.
What Oscar did, and why it mattered
Now — here is where the story gets good.
Andrew's original installer was a former colleague of mine, Oscar, at SAS Solar in Essex. Great engineer. Still in. I picked up the phone, told him what I was seeing, and he was on the FoxESS engineering portal before I'd finished the sentence. Two minutes later he had identified the pack with the lagging firmware and pushed an update over the air. The inverter rebooted. The fault cleared. The system started exporting.
Less than thirty minutes from Andrew's first email to a fully working hybrid. No site visit. No call-out charge. No parts. No engineer's day lost driving to Essex. Andrew got the cheapest possible outcome — which is exactly what a remote diagnostic is meant to do.
What Andrew said
What a fantastic service. Had my fault diagnosed within minutes and actually managed to resolve the issue remotely within a few minutes more. This guy is like a "Solar Batman" helping consumers fix their problems using his extensive industry knowledge and expertise. Outstanding service. Thank you so much.
What you know, and who you know
Two things made this work. The first is the boring one: knowing what CODE-240 really means on a FoxESS when it lands the day a battery pack changes. That's pattern recognition you only get from seeing it across enough sites. The second is the one I'm more pleased about — Oscar, who could have ignored a system he installed years ago, jumped on it inside the same hour because that's what good contractors do.
So it's both. What you know, and who you know.
You don't see this enough in our industry. Most fault codes hide their real cause. Most installers go quiet the moment they've banked the deposit. So when an installer takes the call after the install is long-banked, and an old colleague stays an old colleague — that is worth a write-up.
A fault tracked down. An installer who stood behind his work. A homeowner back online before lunch. That's the kind of fix that makes me glad to be back doing this.
If your inverter is throwing a code that doesn't add up after recent work — new battery, firmware update, change of installer — start where Andrew started: drop me a line.
Frequently asked questions
No. The service manual reads CODE-240 as a current-sensor abnormality, but in practice the FoxESS hybrid throws it any time the BMS handshake or the system identity check fails at boot. Anything that confuses the inverter about what is on the DC bus — a new battery pack, a firmware mismatch, a comms cable on the wrong port — can present as CODE-240. The CT clamp is one cause out of many.
When a FoxESS hybrid boots, it interrogates every battery pack over the BMS bus and checks their firmware revisions against its own known-good table. A new pack shipped with a slightly newer firmware than the rest of the stack is enough to fail the check. Instead of a clear 'firmware mismatch' message, the inverter falls back to CODE-240 and refuses to commission until the packs are aligned.
By skipping the front panel. The combination of new pack + CODE-240 immediately after install is a known signature for a firmware mismatch, not a CT clamp problem. The diagnostic time was the call to the original installer to coordinate an over-the-air battery firmware push from the FoxESS engineering portal — about ten minutes of actual work, the rest is the inverter reboot.
For most brands, no. Firmware updates live in the engineering portal, which is keyed to the installer account that originally commissioned the system. Independent engineers like STS can run the diagnostic, identify exactly what needs pushing, and coordinate with the original installer to make it happen — which is how this fix worked. If the original installer is gone, our installer-gone-bust workflow takes over.
It happens — installers go quiet, go bust, or were never that engaged in the first place. STS works the manufacturer side of these where the installer side has stalled: opening tickets directly with the brand, escalating through their engineering channel, and in some cases getting the system reassigned. Most owners assume the installer is the only route. Often they are not.
Got a fault that does not match the code on the screen?
Tell me what the inverter is saying and what changed before it started saying it. Most root causes named inside a 30-minute session. No fix, no fee.
We use cookies to measure traffic and improve our ads — including sharing limited, hashed details with Meta (Facebook) and Google to measure ad performance. Accept, or decline for essential cookies only. Privacy policy
STS Solar Tech Support
Usually replies within minutes
Hi there!
Got a solar fault or need a quick answer? Drop us a message — we usually reply within a few minutes. Mon–Fri, 9am–7pm.
Start WhatsApp Chat
Got a solar fault or need a quick answer? Drop us a message — we usually reply within a few minutes. Mon–Fri, 9am–7pm.
End-to-end encrypted