Having just joined the Next Drive EV tariff I’ve been analysing my usage to monitor the costs/savings I’m getting with this tariff.
I've been using the ½ hourly data from the Bright app (taken from the DCC) and comparing the measured kWh usage with my own usage recorded from my car-charger.
In an earlier thread I thought I had found an anomaly between the times reported by the DCC data, but realised that their data is based on Zulu time (ie UTC/GMT) and not BST.
https://community.eonnext.com/thread...iff-experience
I had also noticed a mismatch between my charger’s data and the daily “Usage” data being displayed in the EonNext app - I am now certain that the app is using the date/time from the DCC as it’s supplied (ie GMT) and not applying the correction for BST, so the daily totals are out by an hour during summertime.
For example, I’ve taken a couple of days’ usage and done the calculations for totals based on GMT, and totals based on BST.
I’m happy that the BST calculated data is correct as it matches my own recorded usage. However the GMT calculated data is what is being shown by the EonNext app, which will therefore be incorrect during the summer months.
I haven’t yet received a bill for the Next Drive tariff, but am concerned that there is the possibility of being charged at the daytime tariff rather than the EV night-time tariff for the first hour after midnight BST, as in the GMT data this is recorded as the last hour from 23:00 of the preceding day.
This image shows the data being displayed in the app
And these Excel extracts show the GMT calculation (in blue) on the left and BST calcs (in purple) on the right (rows 6 thru 46 hidden for clarity)
Consumption on the 27th
Consumption on the 28th