SolaX Inverter Support — X-Hybrid Battery Charging, SolaX Cloud & Tariff Faults
SolaX battery not charging on cheap rate, SolaX Cloud offline, T-BAT BMS faults, grid disconnections — we diagnose SolaX X-Hybrid systems at the engineering level. Remote-first using SolaX Cloud data and ForceTime configuration logs. Independent from SolaX and your installer.
Most SolaX configuration issues are fixed remotely in a single session. Tell us what you're seeing and we'll resolve it.
Book Remote Diagnostic — from £75 → See the Solar Health PlanSafety: If your SolaX or T-BAT is showing error lights or unusual behaviour, isolate at the DC switch before investigating.
Common SolaX problems we diagnose
Every fault below has a proven diagnostic path. Book a diagnostic if you're unsure where to start.
SolaX X-Hybrid connected but T-BAT not charging on cheap rate. Most often a ForceTime or TOU schedule configuration error in SolaX Cloud — ForceTime not enabled for the correct period, charge power set too low, or grid charge not active. BST/GMT offsets are very common on SolaX systems.
See diagnostic guide →SolaX's ForceTime feature forces the inverter to charge at a set power level during a specified window. It's powerful but frequently misconfigured. Common errors: ForceTime period not overlapping the cheap rate window, SoC target already met, charge power too low to make meaningful progress, or daylight saving time offset causing the window to fire incorrectly.
See diagnostic guide →SolaX T-BAT and Triple Power batteries communicate with the X-Hybrid inverter via CAN bus. A BMS comm fault stops the inverter reading battery state. Causes include a loose CAN cable, incorrect battery type selected in inverter settings, or a firmware mismatch between battery and inverter. Diagnosable remotely via the SolaX Cloud event log.
See diagnostic guide →Triple Power HV batteries require the inverter battery type setting to be correctly selected — choosing T-BAT when Triple Power is installed (or vice versa) will cause the inverter to report a BMS fault or show 0% state of charge. Module address assignments and CAN termination must also be correct when stacking multiple Triple Power units.
See diagnostic guide →T-BAT battery charged but not powering the house during peak times. Common causes: discharge schedule not configured in SolaX Cloud, minimum SoC threshold too high, or the inverter's self-use mode not active. EPS backup must also be separately configured if backup power during outages is needed.
See diagnostic guide →SolaX hybrid powered but not generating. Check SolaX Cloud for DC input voltage — if zero, inspect DC isolators and PV string connections. MPPT tracking issues or a DC isolation fault can stop generation while battery functions continue.
See diagnostic guide →SolaX inverters comply with G98/G99 and disconnect if grid voltage or frequency is outside limits. The inverter reconnects automatically once conditions normalise. In high-solar-density areas, repeated trips may require export limiting or reactive power configuration.
See diagnostic guide →SolaX X-Hybrid inverters support EPS mode but require dedicated backup wiring and must be enabled in settings. If power was lost during a grid outage, EPS may not have been commissioned during installation, or the connected load exceeds the inverter's EPS output rating.
See diagnostic guide →SolaX Cloud shows no data. The inverter's WiFi or 4G pocket WiFi logger has lost connectivity — common after a router change, password update, or ISP-pushed firmware. The inverter and battery continue operating. We reconnect the logger remotely and restore SolaX Cloud access.
See diagnostic guide →SolaX uses a Pocket WiFi dongle (or 4G Pocket LAN for remote sites) to connect to SolaX Cloud. The dongle requires 2.4GHz WiFi. After a router change or upgrade, reconnection requires re-pairing the pocket WiFi to the new network. We guide through this remotely.
See diagnostic guide →What we do for SolaX owners
Remote SolaX Diagnostic
We review SolaX Cloud data, ForceTime schedules, T-BAT BMS logs, and error history to identify the exact fault without a site visit.
SolaX Tariff Configuration
We configure ForceTime settings and TOU schedules in SolaX Cloud for Octopus Agile, Intelligent, Go, or Flux. SolaX ForceTime is powerful but often set up incorrectly — we fix it from scratch in a single session.
On-Site SolaX Repair
EPS circuit verification, CAN bus checks, T-BAT BMS pairing, DC fault location, and component replacement for SolaX X-Hybrid inverters.
SolaX datasheets, manuals & warranty PDFs
Download datasheets, installation manuals and warranty documents for SolaX hybrid inverters and battery systems. Self-hosted and always current.
SolaX fault code index
Seeing an error code on your SolaX inverter? Our fault code index explains what each code means, common causes, and safe next steps.
About SolaX Power systems — what you need to know
SolaX Power is a Chinese manufacturer producing hybrid and string inverters with a strong UK installed base, particularly from installations between 2015 and 2024. Their core hybrid range is the X-Hybrid series — single-phase X1-Hybrid (3kW–6kW) and three-phase X3-Hybrid (5kW–15kW). These pair with two battery families: the older T-BAT range (T-BAT-SYS-HV, T-BAT-5.8, T-BAT-3.0) and the newer Triple Power high-voltage batteries (5.8kWh per module, stackable to 11.6kWh). Both families use CAN bus communication with the inverter. SolaX's ForceTime feature allows precise charging windows to be configured, but it is frequently set up incorrectly — making it one of the most common causes of overnight charging failure on SolaX systems.
Monitoring is provided by the SolaX Cloud platform. The inverter connects via a Pocket WiFi dongle (2.4GHz only) or Pocket LAN adapter. The most common queries we handle: SolaX battery not charging overnight, SolaX ForceTime not working, SolaX Cloud offline, T-BAT or Triple Power BMS communication fault, and SolaX grid disconnection fault. A common Triple Power-specific issue is the inverter battery type being left on the T-BAT setting after a battery upgrade — this causes the inverter to reject the Triple Power modules. STS provides independent support — not affiliated with SolaX Power.
SolaX questions answered
The most common cause on SolaX systems is a misconfigured ForceTime period in SolaX Cloud. The ForceTime window must exactly cover the cheap rate window, charge power must be set high enough to make meaningful progress, and grid charge must be active. BST/GMT offsets frequently cause the window to fire at the wrong time. We reconfigure ForceTime remotely.
Yes — if SolaX Cloud shows offline, the inverter and battery are almost certainly still operating normally. Only the Pocket WiFi dongle has lost its internet connection. The inverter continues to manage solar, battery, and grid independently. We reconnect the Pocket WiFi remotely to restore SolaX Cloud access.
We support all SolaX hybrid generations — X1-Hybrid (G2, G3, G4), X3-Hybrid (G4, G4-Pro), X3-Mega, and the older X-Series range. We cover all SolaX battery systems: T-BAT (T-BAT-SYS-HV, T-BAT-5.8, T-BAT-3.0) and the newer Triple Power range (5.8kWh and 11.6kWh HV modules). A common Triple Power issue is an inverter battery type mismatch — if the inverter is still set to T-BAT after a Triple Power installation, the battery won't be recognised. For string-only SolaX inverters (X1-Boost, X3-Pro), we handle the monitoring and grid fault aspects.
Yes. We configure SolaX Cloud ForceTime periods and TOU schedules to work correctly with Octopus Agile, Go, Intelligent, Flux, or any other tariff. SolaX's ForceTime is powerful but often set up incorrectly — we configure it correctly from scratch in a single remote session.
STS supports all major inverter and battery brands — not just SolaX. If you have a mixed-brand system, visit the brand hub.
Browse all supported brands →Ready to fix your SolaX system?
Tell us what's happening. We'll review your SolaX Cloud data and come back with a clear diagnosis — usually same day.