SolaX ForceTime Not Working — Octopus Charging Fix
Your SolaX battery should be charging overnight on Octopus Go, Flux, or Agile — but it is not. ForceTime is configured in SolaX Cloud but the battery stays flat. The most common causes are a disabled Charge from Grid setting, a BST/GMT clock offset firing the window at the wrong time, or a work mode conflict overriding ForceTime.
SolaX ForceTime has several hidden dependencies — Charge from Grid, work mode, SoC targets, and clock sync all need to be correct. We review your SolaX Cloud configuration remotely and fix it in a single session.
Book Remote Configuration — from £75 → Back to SolaX hubIndependent — not affiliated with SolaX Power.
⚡ Safety Warning
Do not open your inverter or interfere with DC cabling. Solar panels produce live DC voltage whenever exposed to light. Always use your DC isolator switch and contact a qualified solar engineer for hands-on fault diagnosis.
6-step ForceTime diagnosis
Work through these steps to identify why your SolaX battery is not charging during the cheap rate window. Each step addresses a different common configuration error.
Check if ForceTime is actually enabled in SolaX Cloud
Log into SolaX Cloud and navigate to your inverter's settings. Open the ForceTime configuration page and check whether the ForceTime periods are enabled. SolaX allows up to two ForceTime periods — each must be individually toggled on.
A common mistake is setting the time window but leaving the period toggle off. If you see ForceTime Period 1 with times configured but the toggle is disabled, the inverter will not charge during that window. Enable the period and save. Changes pushed from SolaX Cloud can take several minutes to reach the inverter — check the inverter display or live data to confirm the command was received.
Verify the ForceTime window matches your tariff exactly
The ForceTime start and end times must exactly cover your cheap rate window. Common UK tariff windows:
If the ForceTime window is shorter than the tariff window, the battery may not reach full charge. If it is longer, you will import at the standard rate for the extra time. SolaX Cloud uses 24-hour format.
Confirm Charge from Grid is active
ForceTime tells the inverter when to charge, but Charge from Grid must also be enabled for the inverter to actually pull power from the grid into the battery. This is a separate setting in SolaX Cloud — it is not automatically enabled when you turn on ForceTime.
Navigate to your inverter settings and look for the grid charge toggle. If this is off, the inverter will only charge the battery from solar during the ForceTime window — which produces zero charge overnight when there is no sunlight. This is one of the most common causes of ForceTime appearing correctly configured but the battery staying flat every morning.
Check for BST/GMT clock offset
SolaX inverters and SolaX Cloud do not always handle British Summer Time correctly. When the clocks change in March or October, the ForceTime window may shift by one hour relative to your actual tariff window.
If your Octopus Go window is 00:30 to 04:30 but the inverter clock is still on GMT during BST, ForceTime will actually run from 01:30 to 05:30 — charging for one hour at the standard rate. Check the clock on the inverter display against the actual time. If it is one hour behind or ahead, the timezone or DST setting needs correcting in SolaX Cloud.
Some firmware versions require a manual clock sync after each DST changeover. This is the single most common ForceTime issue we see in UK SolaX systems.
Review work mode and SoC target settings
SolaX X-Hybrid inverters have several work modes — Self Use, Feed-in Priority, Backup, and Off-Grid. ForceTime only functions correctly in Self Use or Backup mode. If the inverter is set to Feed-in Priority, it will prioritise exporting solar to the grid over charging the battery, and ForceTime may not override this.
Also check the target state of charge. If the ForceTime SoC target is set to 50 percent and the battery is already at 50 percent, ForceTime will not charge further. Set the ForceTime SoC target to 100 percent to ensure a full charge during the cheap rate window. The minimum SoC setting (which controls how low the battery can go during the day) should be configured separately — typically 10 to 20 percent.
Book a remote configuration session if settings will not hold
If you have checked all five steps above and ForceTime is still not charging correctly, the issue may be firmware-related or involve a setting conflict that is not visible in SolaX Cloud. Older firmware versions have known bugs where ForceTime settings revert after a power cycle or fail to sync from the cloud.
STS can access your SolaX Cloud data remotely, verify every configuration parameter, identify firmware issues, and push corrected settings — usually in a single session. We support all X-Hybrid generations (G2 through G4) and all UK time-of-use tariffs.
Why SolaX ForceTime is the most commonly misconfigured battery feature in the UK
SolaX's ForceTime is one of the most powerful charging features available on any UK hybrid inverter. It allows precise control over when the battery charges from the grid, at what power level, and to what state of charge. For time-of-use tariff owners — particularly Octopus Go, Flux, and Agile customers — ForceTime is the core mechanism that makes cheap overnight charging work.
The problem is that ForceTime has several hidden dependencies. Enabling the ForceTime period is only the first step. Charge from Grid must be separately enabled. The work mode must be Self Use or Backup. The SoC target must be set correctly. The inverter clock must be synchronised and handling BST/GMT correctly. A conflict in any one of these settings will prevent charging, and SolaX Cloud does not warn you about conflicting configurations.
The BST/GMT issue affects thousands of SolaX systems across the UK twice a year. When the clocks change, owners who set up ForceTime months ago suddenly find the battery is not fully charged in the morning — or that charging starts an hour late and imports at the expensive rate. Older firmware versions are particularly affected because they do not automatically adjust for DST. This single issue generates more support calls to STS than any other SolaX problem.
Most common ForceTime configuration errors
The inverter will only charge from solar during ForceTime if grid charge is disabled. Enable Charge from Grid in SolaX Cloud settings.
Inverter clock has not adjusted for daylight saving time. Check display clock against actual time. Correct the timezone or DST setting in SolaX Cloud.
Inverter is set to Feed-in Priority. ForceTime requires Self Use or Backup mode. Change the work mode in SolaX Cloud.
ForceTime SoC target is set below 100%. The inverter stops charging when the target is reached. Set ForceTime SoC to 100% for a full overnight charge.
Known bug on older SolaX firmware versions. ForceTime settings saved in SolaX Cloud do not persist after an inverter restart. Firmware update may be required.
ForceTime & Octopus charging — common questions
ForceTime is a SolaX feature that forces the X-Hybrid inverter to charge the battery from the grid during a set time window. You configure up to two ForceTime periods in SolaX Cloud with a start time, end time, and target state of charge. During that window, the inverter draws grid power at the configured charge rate until the battery reaches the SoC target. It is designed for time-of-use tariffs like Octopus Go, Flux, or Agile — charging on cheap rate so you use stored energy during expensive peak hours. Charge from Grid must be separately enabled for ForceTime to work.
The most common cause is a BST/GMT clock offset. SolaX inverters do not always adjust for British Summer Time automatically. When the clocks change, the ForceTime window shifts by one hour — so a window set for 00:30 to 04:30 actually runs from 01:30 to 05:30, meaning you charge for one hour at the standard rate. Check the clock on the inverter display against the actual time. If it is one hour out, the timezone or DST setting needs correcting in SolaX Cloud. Some older firmware versions require a manual clock sync after each DST change.
Yes — ForceTime is configured through SolaX Cloud, which any system owner can access. You need to enable the ForceTime period, set the correct start and end times, set the target SoC to 100 percent, and enable Charge from Grid. The challenge is that SolaX Cloud has multiple overlapping settings — work mode, ForceTime, TOU schedules, min SoC, and charge power — and a conflict between any of them can prevent charging. If you are not confident with the settings, a remote configuration session can set everything up correctly in one go.
For Octopus Go, configure ForceTime Period 1 with a start time of 00:30 and end time of 04:30. Set the target SoC to 100 percent and the charge power to the maximum your inverter supports. Enable Charge from Grid. Set the work mode to Self Use so the battery discharges to power the house during the day. Set the minimum SoC to your preferred backup level — typically 10 to 20 percent. After saving, check SolaX Cloud live data the next morning to confirm the battery charged during the correct window. Repeat the check after the next BST/GMT changeover.
ForceTime forces the inverter to charge from the grid during a set window regardless of other conditions. TOU (Time of Use) is a more complex scheduling system that manages both charging and discharging across multiple time periods. ForceTime is simpler and more reliable for most UK tariffs — you set the cheap rate window and the inverter charges. TOU allows more granular control but is harder to configure correctly and more prone to conflicts. For standard tariffs like Octopus Go or Flux, ForceTime is usually the better choice. TOU suits Agile tariffs where rates change every 30 minutes.
ForceTime not charging? We configure it remotely.
We access your SolaX Cloud, verify every ForceTime parameter, fix clock offsets, correct work mode conflicts, and confirm the battery charges on the correct window — usually in a single session.