IOG tariff goes stale, meaning optimed plan same as intial plan

[stevebuk1]

My import tariff is Octopus Intelligent Go, with no export tariff (as my install is DIY with no MCS)

I find that every few days, the IOG tariff goes "stale", in that instead of the cheap rate lasting for 6 hours and then reverting to peak, it stays at cheap rate for at least the next 24 hours. I think this is causing Pv_opt to not schedule any charging.

Tariffs are loaded via BottlecapDave integration, however setting import tariff directly in config.yaml("octopus_import_tariff_code: E-1R-INTELLI-BB-VAR-23-03-01-N") would emulate the problem.

Screenshots below and pv_opt.log attached.

Pv_opt is at v3.12.1.

pv_opt.log

[fboundy]

Hmmm. I'll add some more logging to the EV- charging pre-release to try to track this down. I can see it's flagging the discrepancy with Bottlecap Dave's tariffs so when that happens I'll get it to dump some more info.

[fboundy]

Is there anything in error.log?

[stevebuk1]

Is there anything in error.log?

There wasn't when I posted, but I've recently moved Pv_opt to a new Pi so the issue may not have been caught when it actually occurred.

I have just checked it this morning next day and I found a few entries at 23.35 that might be related:
error.log

Note : I can clear the issue by stopping AppDaemon and then restarting.

[fboundy]

Could you upload a snip of pv_opt.log for 23:35 too so I can see the context of the error?

[stevebuk1]

Could you upload a snip of pv_opt.log for 23:35 too so I can see the context of the error?

Attached, from 11pm to Midnight (I think I've got the right night):
pv_opt.log

[fboundy]

Nothing that gives any clues there. Let's see what the latest release logs.

[stevebuk1]

'3.14.0-beta-6' used.

Logs are here:
pv_opt.log
error.log

Current image for reference (same as in first entry above, in that only a cheap rate is forecast when it should revert to a peak rate at 05.30 tomorrow morning):

[stevebuk1]

The code in PR #215 appears to be working reliably so if this PR is accepted this issue can be closed.

[fboundy]

Closing. Thanks for the PR