Could Tariff comparison data be extended to include current/next rate?

[deltamelter]

I was making my own comparison sensors for a couple of other tariffs I am watching beside Agile when I noticed you added the Tariff Comparison at the add integration menu.
This is doing most of what I had just made in jinja template on a rest/commandline sensor except that I am calculating using live consumption from mini, right up to the minute so that I can graph how much current usage would cost on different tariffs.
The Tariff Comparison in the OE integration only looks at the previous full 24 hours up to midnight. Could you add cost calculation up to the current time and also show all upcoming rates?

Also, is the Tariff Comparison a one off calculation for one time previous 24hr calculation? Or was this broken be my recent Agile tariff change. The rest of the OE sensors stopped working until I restarted HA after the tariff renewed.

note the flat lines until I manually restarted HA after tariff renewed (changed tariff code)

[BottlecapDave]

Hello. There are no plans to expose current data for other tariffs. I thought I put this rationale in the docs, but I clearly haven't. The main reasons are

1. OE are already upset with the amount of data I am pulling from the API, so I only pull through data that is required to provide functionality, which is then exposed as raw data where possible. No evaluation is performed on current data, so that data isn't pulled
2. I only evaluate previous consumption data as this data is available to everyone and I feel this feature is reflective on historic data not on current data. I don't feel anyone is going to make a decision based on current data alone, so having it be calculated on this data felt unnecessary.

These calculations are performed everytime the previous consumption data updates. Before v14 there was a bug where new tariffs were not being updated in certain scenarios, so could be linked to this. If you were already on this version, any logs would be useful to track down the error.