-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with accumulative off peak cost tracker #1094
Comments
By my reckoning Off peak should have been 27kWh less than the total usage by the end of the day. It should have flatlined/ remained at 16kWh from 7am until 9am when the bump charge for the free electricity session transitioned to a IOG scheduled smart charge (as shown by the current rate dropping to 7p/kWh) until 12pm when that ended. Shape of off peak us right from 9am onwards - just 27kWh too high due to the two steps/corrections (that are wrong) in the graph of off peak usage. |
Saw something similar to this myself that I am currently working to try and understand if it’s normal behaviour or not for these sensors. I’m new to Intelligent Go and the energy monitoring is all over the place now with values moving around the various accumulation stats that didn’t occur on Tracker previously |
Hello and sorry you're seeing this issue. The off peak sensor is based on the consumption blocks reported by the Home Mini along side the appropriate rates for those consumption periods. These values may reconcile during the day when consumption data from the Home Mini is corrected or new completed dispatches come through from OE. It looks like the off peak sensor is increasing in all of the right places and that it's the current consumption sensor that hasn't updated enough. Do you have any completed dispatches during the period in your dispatching sensor? If you're comfortable with SQL, you could have a look to see what the charges breakdown was for the target day (unfortunately HA doesn't provide a way other than SQL to get at this data). You'll need the SQL add-on to run this command.
|
One thing to bare in mind is that the graph is when the sensor's total updates. If there is a delay in getting the consumption data (e.g. OE APIs are unavailable) or the data is corrected, then this can cause spikes in the graph even though consumption didn't occur at that point. It might have been a correction to an earlier period (e.g. it goes from total 10kWh to 15kWh where the additional 5kWh was added to an earlier period). The part that is odd is that you didn't seem to consume any additional energy from 12pm to 12am, as the accumulative consumption sensor didn't increase. But I obviously don't know your energy arrangement (e.g. batteries). It might also be worth comparing the off peak and total accumulative costs to see if they show a similar story. |
Will try at get the requested data via SQL. NB the yellow line on the above graph is the total accumulative consumption. My calculations would have the blue (off peak usage) flat from 5:30-9am and then run parallel to total consumption from 9-12 but 27kWh lower. It can't ever catch up with total surely. Graph above shows it jumping up to run the same as total usage for the rest of the day. I'll look for another day where we've imported peak rate for comparison. |
@BottlecapDave Ive got the SQL, shows an entry at 8:28 and 9:28 for the off peak consumption and cost jumps seen in the first screen shot. Obviously between 9:00 and 9:27 the off-peak consumption should be increasing and parallel to total consumption whilst EV was charging on a IOG smart charge (it was - the small gentle slope at that time between the two jumps), but it has jumped either side of that for some reason. 8:28 jumps from 16.411kWh to 30.082kWh 9:28 jumps from 33.579kWh to 46.642kWh {"state_class":"total","last_reset":"2024-11-24T00:00:00+00:00","mpan":"XXXXX","serial_number":"XXXXX","is_export":false,"is_smart_meter":true,"total":46.642,"charges":[{"start":"2024-11-24T00:00:00+00:00","end":"2024-11-24T00:30:00+00:00","consumption":4.019},{"start":"2024-11-24T00:30:00+00:00","end":"2024-11-24T01:00:00+00:00","consumption":4.06},{"start":"2024-11-24T01:00:00+00:00","end":"2024-11-24T01:30:00+00:00","consumption":3.999},{"start":"2024-11-24T01:30:00+00:00","end":"2024-11-24T02:00:00+00:00","consumption":1.694},{"start":"2024-11-24T02:00:00+00:00","end":"2024-11-24T02:30:00+00:00","consumption":0.138},{"start":"2024-11-24T02:30:00+00:00","end":"2024-11-24T03:00:00+00:00","consumption":0.128},{"start":"2024-11-24T03:00:00+00:00","end":"2024-11-24T03:30:00+00:00","consumption":0.133},{"start":"2024-11-24T03:30:00+00:00","end":"2024-11-24T04:00:00+00:00","consumption":0.143},{"start":"2024-11-24T04:00:00+00:00","end":"2024-11-24T04:30:00+00:00","consumption":0.432},{"start":"2024-11-24T04:30:00+00:00","end":"2024-11-24T05:00:00+00:00","consumption":1.366},{"start":"2024-11-24T05:00:00+00:00","end":"2024-11-24T05:30:00+00:00","consumption":0.299},{"start":"2024-11-24T07:00:00+00:00","end":"2024-11-24T07:30:00+00:00","consumption":6.427},{"start":"2024-11-24T07:30:00+00:00","end":"2024-11-24T08:00:00+00:00","consumption":7.244},{"start":"2024-11-24T08:00:00+00:00","end":"2024-11-24T08:30:00+00:00","consumption":7.145},{"start":"2024-11-24T08:30:00+00:00","end":"2024-11-24T09:00:00+00:00","consumption":5.918},{"start":"2024-11-24T09:00:00+00:00","end":"2024-11-24T09:30:00+00:00","consumption":3.497}],"unit_of_measurement":"kWh","device_class":"energy","icon":"mdi:lightning-bolt","friendly_name":"Off Peak Current Accumulative Consumption Electricity (XXXXX)"} |
If you look at the cost sensor instead of the consumption, that should include the breakdown of the consumption and the associated rate/cost. It might also be worth looking at the dispatching sensor at the same time to see what it thought the pending/completed dispatches were. In addition it might be worth looking at the data at the end of the day as well. |
Ok so Cost sensor shows it using the off peak rate during the 7-9am slots... Data is from the 9:28 update {"start":"2024-11-24T07:00:00+00:00","end":"2024-11-24T07:30:00+00:00","rate":0.070003,"consumption":6.427,"cost":0.45},{"start":"2024-11-24T07:30:00+00:00","end":"2024-11-24T08:00:00+00:00","rate":0.070003,"consumption":7.244,"cost":0.51},{"start":"2024-11-24T08:00:00+00:00","end":"2024-11-24T08:30:00+00:00","rate":0.070003,"consumption":7.145,"cost":0.5},{"start":"2024-11-24T08:30:00+00:00","end":"2024-11-24T09:00:00+00:00","rate":0.070003,"consumption":5.918,"cost":0.41}, In order to trigger the EV charge during the 7-9 free electricity slot I had to bump charge it as the Hypervolt integration is still beta and disabling smart charging didn't give Hypervolt back control to manage the charge and allow me to manually trigger it. Wondering of that's confused something and for the import to be treated as off peak for cost and therefore match the total consumption when it shouldn't have been? |
Something appears to have triggered the off peak rate from 7:30 even though the current rate shows the correct rate, dispatching sensor is right as are smart charge and bump charge. Full end of day data for the off peak cost sensor. Presume as 6:00 and 6:30 slots are missing they were treated as peak (albeit it with no consumption due to battery), but that 7:00, 7:30, 8:00, and 8:30 slots were tracked as off peak rate... Does the Mini get the rate data from Octopus direct, may have been that Octopus have chosen that any IOG bump charges during a free electricity window are off peak...? Bill be out on 6th December so can confirm what I get billed then... {"start":"2024-11-24T00:00:00+00:00","end":"2024-11-24T00:30:00+00:00","rate":0.070003,"consumption":4.019,"cost":0.28},{"start":"2024-11-24T00:30:00+00:00","end":"2024-11-24T01:00:00+00:00","rate":0.070003,"consumption":4.06,"cost":0.28},{"start":"2024-11-24T01:00:00+00:00","end":"2024-11-24T01:30:00+00:00","rate":0.070003,"consumption":3.999,"cost":0.28},{"start":"2024-11-24T01:30:00+00:00","end":"2024-11-24T02:00:00+00:00","rate":0.070003,"consumption":1.694,"cost":0.12},{"start":"2024-11-24T02:00:00+00:00","end":"2024-11-24T02:30:00+00:00","rate":0.070003,"consumption":0.138,"cost":0.01},{"start":"2024-11-24T02:30:00+00:00","end":"2024-11-24T03:00:00+00:00","rate":0.070003,"consumption":0.128,"cost":0.01},{"start":"2024-11-24T03:00:00+00:00","end":"2024-11-24T03:30:00+00:00","rate":0.070003,"consumption":0.133,"cost":0.01},{"start":"2024-11-24T03:30:00+00:00","end":"2024-11-24T04:00:00+00:00","rate":0.070003,"consumption":0.143,"cost":0.01},{"start":"2024-11-24T04:00:00+00:00","end":"2024-11-24T04:30:00+00:00","rate":0.070003,"consumption":0.432,"cost":0.03},{"start":"2024-11-24T04:30:00+00:00","end":"2024-11-24T05:00:00+00:00","rate":0.070003,"consumption":1.366,"cost":0.1},{"start":"2024-11-24T05:00:00+00:00","end":"2024-11-24T05:30:00+00:00","rate":0.070003,"consumption":0.299,"cost":0.02},{"start":"2024-11-24T07:00:00+00:00","end":"2024-11-24T07:30:00+00:00","rate":0.070003,"consumption":6.427,"cost":0.45},{"start":"2024-11-24T07:30:00+00:00","end":"2024-11-24T08:00:00+00:00","rate":0.070003,"consumption":7.244,"cost":0.51},{"start":"2024-11-24T08:00:00+00:00","end":"2024-11-24T08:30:00+00:00","rate":0.070003,"consumption":7.145,"cost":0.5},{"start":"2024-11-24T08:30:00+00:00","end":"2024-11-24T09:00:00+00:00","rate":0.070003,"consumption":5.918,"cost":0.41},{"start":"2024-11-24T09:00:00+00:00","end":"2024-11-24T09:30:00+00:00","rate":0.070003,"consumption":3.783,"cost":0.26},{"start":"2024-11-24T09:30:00+00:00","end":"2024-11-24T10:00:00+00:00","rate":0.070003,"consumption":3.88,"cost":0.27},{"start":"2024-11-24T10:00:00+00:00","end":"2024-11-24T10:30:00+00:00","rate":0.070003,"consumption":3.442,"cost":0.24},{"start":"2024-11-24T10:30:00+00:00","end":"2024-11-24T11:00:00+00:00","rate":0.070003,"consumption":4.108,"cost":0.29},{"start":"2024-11-24T11:00:00+00:00","end":"2024-11-24T11:30:00+00:00","rate":0.070003,"consumption":3.615,"cost":0.25},{"start":"2024-11-24T11:30:00+00:00","end":"2024-11-24T12:00:00+00:00","rate":0.070003,"consumption":3.315,"cost":0.23},{"start":"2024-11-24T23:30:00+00:00","end":"2024-11-25T00:00:00+00:00","rate":0.070003,"consumption":3.673,"cost":0.26} |
Just checked online and I've been credited with £1.76 for the 2 hours which would correlate to 25kWh at off peak rate and only 6.7kWh at peak rate. This would seemingly confirm that the bump charge during a free electricity session triggers an off peak rate from Octopus ! I'll ask on the Smart Energy forums too. think folks generally use manual control rather than bump charge in this scenario |
As previously mentioned the rates are adjusted to off peak rates based on pending and completed dispatches. What I probably didn't make clear was that this is done within the integration. The rates provided by OE are just the base rates. If you could grab the attributes of the dispatching sensor around the same time, it might indicate why the rates were lowered during this time. |
The dispatching sensor is on the original screen shot and shows as 'Off'. Here's the attributes of that sensor at 08:27 on 24/22/2024 and at 09:00. Show source as bump charge for first and then smart charge for 9am onwards, and initially a planned dispatch from 07:07 to 16:43. Note we stopped the smart charge at 12pm (after the first of the subsequently scheduled smart charges anyway as we went out) 08:27 attributes 09:00 attributes |
Thanks for that. It might be that when your bump charge goes into a completed dispatch, the source turns to null, so the integration doesn't know if the completed dispatch was a smart charge or a bump charge. This means that at 9am it would have recatagorised those earlier bump charges as off peak. I might need to look at keeping track of the pending dispatches for longer somehow so I can match them up with the completed dispatches. I might also contact OE to see if this is a bug. |
Thanks. Given what I’ve been credited and what the Home Mini reported according to the all queries you had me grab earlier I think Octopus have dropped the rate despite the peak time bump charge because it was also a free electricity session. Will be interesting to check my bill in a few days and what OE say to your enquiry. |
I've been having an issue with Predbat cost calculations and it seems that the cause is that Completed Dispatches for smart charges are removed from the history after a couple of hours. They don't remain in the data for the rest of the day and so when Predbat does it's recalculation it doesn't know the charging happened during an off-peak period because there's no longer anything in the data to say it was cheap and so it incorrectly uses the peak rate for the cost calculation. From reading the above, I think it could this be the same issue (apologies if it isn't). Here's an example: for these two slots, the first persists throughout the day (and is still present for the whole of the following day) but the second 'smart-charge' rate is no longer present in the data retrieved when the system runs five minutes later at 9am. This results in a very similar vertical jump in cost calculated but no increase in kWh usage:
These purges of previously used smart charging slots seem to occur at similar times each day which appears to be just before 09:00 and around 4pm (usually gone in the 16:15/16:20 runs). I have a Tesla but the IOG is setup to connect with my Zappi charger and the car was plugged in the previous evening on 10% and set to charge to 100%. If the car is left plugged in and full then there's no additional slots and so the issue doesn't occur - it's only when it is plugged in and needs charge. This only seems to affect slots where the source is smart-charge, though it seems from the API docs and comments in the IOG Forums that the max intended retention is 12 hours anyway so it won't last the whole day ("All completed device dispatches 12 hours behind, in reverse time order.") Here's the report over there with more info/data: springfall2008/batpred#1663 Therefore, I don't think this is bug with this integration, just a consequence of Octopus not persisting certain slots for a long time in the historic data. |
Describe the bug
Incorrect behaviour yesterday (24/11/24) with the accumulative off peak usage tracker (kWh). It "jumped up" incorrectly to follow the total accumulative usage during the 7-9am. this happened to be a free electricity session, but I don;'t have any triggers or automations using that new sensor. NB I do have an automation it's just manually trigger on the time.
Reproduction steps
Not sure how or why it happened
Expected behaviour
Off peak sensor only tracks true off peak or IOG off peak rate usage
Tariff Code
E-1R-INTELLI-VAR-22-10-14-H
Integration Version
13.1.3
Home Assistant Version
2024.11.3
Fresh Install?
After upgrading
Home Assistant Logs
Will try and get these later - nothing obvious in HA Logbook or Logs from an initial scan
Confirmation
The text was updated successfully, but these errors were encountered: