FoxESS Community - Owners & Installers Forum

Hi folks,
I'm on the UK Octopus Flux (not intelligent) and as with many folks, I have scheduler set to force charge between 02:00 & 05:00 (to 50%) then set to force discharge from 16:00 to 19:00. Buy low, sell high

All well and good but, looking back over Apr data the FoxESS app/cloud shows differs to the data provided by Octopus, in fact it isn't even close! I've attached snippets of the respective datasets, just in case I'm missing something obvious.

Has anyone else observed this, and if so how did you approach resolving it with Octopus, assuming that the FoxESS data is indeed correct?
Rgds, Graham

Can I suggest you post some condensed numbers?

Octopus Export (month) = xxx.yy kWh
Fox Cloud Export (month) = xxx.yy kWh

and if you want, data for a day.


Regards to the topic directly, Fox data cannot be used to query Octopus as the CT clamp won't be calibrated for meter level accuracy.

FWIW my export readings for a month are 97% Octopus vs Fox roughly.

Hi folks,

Short update on the issue I had.

It transpires that the meter clock was indeed out (not in sync to the central time source) by 5 1/2 hours.

This was eventually corrected by Octopus. What is taking longer to resolve is the delta between what I was billed for (import) / and credited for export; but at least they have acknowledged that it wasn't calculated correctly.

So, a top tip... once you have had a solar install - do check that your meter is showing the correct time

Glad you found the error, a bad meter clock can cause a lot of trouble with TOU tariffs.
Hope the billing is sorted out quickly.