Predbat not reading the Cosy Octopus cheap times

Third party integrations
1

Salve Cognoscenti,
I have Predbat running as an add-on on my HA OS loaded on a Pi 5. The log shows it is running successfully. However it has set up a schedule that does not recognise the times of day that my Octopus Cosy runs at it’s lowest rate (0400-0700, 1300-1600, 2200-0000). I changed Predbat from “Monitor” to “Control charge & discharge” last night, and woke to discover my GiveEnergy AIO was flat. Predbat had changed it’s settings so it did not charge between 0400-0700 and it had been supplying my ASHP which is set up to run during the cheap electricity periods.

I have pored over the Predbat installation configuration and I have checked that the following entities are running:
event.octopus_energy_electricity_xxxxxxxxxxxxxxxxxxx_current_day_rates, previous_day_rates and next_day_rates. They are showing sensible attributes i.e.:


event_types:
  - octopus_energy_electricity_current_day_rates
event_type: octopus_energy_electricity_current_day_rates
rates:
  - start: "2025-02-09T00:00:00+00:00"
    end: "2025-02-09T00:30:00+00:00"
    value_inc_vat: 0.255204
    is_capped: false
  - start: "2025-02-09T00:30:00+00:00"
    end: "2025-02-09T01:00:00+00:00"
    value_inc_vat: 0.255204
    is_capped: false

There is probably something basic that I havn’t switched on or off. One thing I haven’t done is changed any of the settings related to discharging the battery to the grid. I have the old Feed-in Tariff for solar generation so it isn’t commercially sensible to cancel this. Might something be needed to be tweaked here?

Any ideas gratefully accepted!

2

I think that Predbat was picking up the Octopus Cosy tariff details after all. On the Predbat Plan it shows the tariff correctly, and I think it may have been showing it before I sought help.

But I noticed in the log that there was an error about my Day 7 records:

Warn: Historical day 7 has no data, unable to fill gaps normally using nominal 24kWh - you should fix your system!

A week ago I decided to reduce the size of the home_assistant_v2_db_size as it had got to 1.9GB. So I switched off all the sensors. As a result Predbat assummed the nominal 24kWh when the actual consumption is 40+kWh. So it calculated that the battery consumption was not as hight as it actually was, and therefore switched off the charging period 04.00-07.00.

If this is correct I should see the appropriate battery charging pattern in seven day’s time - I have turned back on the following:

include:
  entity_globs:
    - binary_sensor.octopus*
    - sensor.octopus*
    - sensor.solcast*
    - sensor.predbat*
    - event.octopus*
    - number.givtcp*
    - select.givtcp*
    - sensor.givtcp*
    - switch.givtcp*
    - update.givtcp*

Although, seeing the quantity of data the givtcp entities contain, I suspect the HA database is going to bloat further.
If anyone can advise which of the predbat/octopus/givtcp entity values I do not need to record I would be very grateful.