Using Predbat compare, my setup has not been showing any result for Flux for a week or so. (“No data yet”)I did not think anything of it. Yesterday with the sun actually starting to appear I thought I would switch back to Flux (for the last 3 years I use Flux in summer and Eco7 and fixed export in winter). Octopus website says “Flux not available at present”
Yes, 2 or 3 tariffs have been withdrawn due to the Iran conflict and energy price turmoil.
Also some tariffs now have exit fees.
Octopus protecting itself. Flux and the others will come back sometime.
its highly likely that the tariff codes for your compare have been expired. A number of codes were expired about 6 months ago.
Instructions on finding the latest tariff codes and configuring Predbat compare to use them are as ever in the documentation Comparing Energy Tariffs - Predbat Documentation
Even if Flux isn’t available to join, you can still compare the latest Flux version to your current tariff.
TBH though I don’t see Flux as being a particularly good tariff. The day export rate is lower than the flat 12p export rate and the only upside is the peak export rate. So I feel Flux is only a good tariff if you have lots of battery storage relative to your solar array size and can store sufficient in the battery to (a) export in the evening peak and (b) still retain enough to see you through to the start of the next solar day. The import rates on Flux, even overnight, aren’t that attractive
1 Like
Geoffrey thanks
I have followed the Predbat documentation and have the correct codes for Flux but still see “no data yet”. Based on your comments I will just sit on Eco7 import and fixed export for now until things settle. I am sure predbat will do it’s best
What does it show in the logfile when the comparison runs at midnight for Flux?
Can you share that bit of the apps.yaml config and I can see if there is something weird with the tariff code.
Cheers
1 Like
The predbat logfile is set to not exceed a certain size, 10Mb I think. When it reaches that it renames predbat.log to predbat.1.log, and .1.log to .2.log, etc. So the old logfiles are still there, you just need to find and open the right one with a text editor.
Thanks fir sharing your config.
In short, you are using out of date tariff codes.
The -BB codes were withdrawn some time ago, the Flux export in September 2025, and that’s what’s causing the compare not to work. I’m surprised your agile codes are working still.
If I look at the code you are using:
Notice the valid from and to dates
And the correct code to use
1 Like
Geoffrey. Thanks. Is there somewhere I can download the new codes to put in my Predbat Apps.yaml editor
I have found 10 predbat.x.log files, but the earliest I can get back to is 01:26
I have setup the Octopus integration and enabled events (i think), but is there anywhere else i need to enter anything for Predbat to find my tariffs?
I would like to use the auto discovery.
What is the sensor metric_octopus_xxx that I think I have to name in apps.yaml
Keeping on top of the Octopus tariff codes isn’t really something Predbat can do, so I’ve put instructions about how to fid the tariff codes in the documentation as its something you have to manually configure.
Having said that, the tariff codes in the documentation which were updated in October 2025 are valid and still work. They may not be the absolutely latest current tariff codes, but that is a never ending chase process and hence why the instructions in the documentation.
The tariff codes are nothing to do with the Octopus integration, these are you configuring Predbat to directly retrieve the rates you want to compare from the Octopus API.
that is you configuring predbat to get your energy rates from the octopus integration. The octopus integration gets the rates based on what tariff you are on from your octopus account.
1 Like
Thanks. This is hurting my head. What do I type in xxx in " metric_octopus_xxx ". Sorry to be such a knob
What should the text line look like for import and export
Is that your import and export ENERGY RATES for the tariff you are on (which is the metric_octopus setting that points to an entity with your meter number in it from the Octopus integration) Energy rates - Predbat Documentation
Or is it the tariff entries for the COMPARE which is what you started asking about ?
Examples of how to configure the compare tariffs are in the documentation Comparing Energy Tariffs - Predbat Documentation
You can either configure a manual entry (rate X for times A to B) or you can use Octopus URL’s as you have been using. Example tariffs codes are in the documentation but as I said, check that the tariff codes are the latest ones.
Instructions for how to find the latest tariff codes e.g. for Octopus Flux are in the same place.
Geoffrey. Thanks. Grandparent duties tomorrow, so I will try and get my head around reding and understanding over the weekend, though from what I can see there are not many tariffs available at the moment.