Download data different than in app
in Bright App
Title says it really. I downloaded my data from Glowmarkt but it is different to what I see in the Bright App. Monthly usage is quite different. Daily usage seems to be roughly the same but a day out of sync.
Any ideas?
Comments
So I looked at this some more and there are clearly bugs in the way the download data is compiled.
Taking one day of my data (19 Jan 2025), I compared the download 30 minute data with the app and it's the same. So the raw data which the daily and monthly figures are compiled from is correct. Totaling the usage for that one day from the 30 minute data comes to 50.2KW. On the daily download the usage for the 19th is completely different but the usage data for the 18th is 50.8KW - almost the same as for the 19th on the app but with a 0.6KW difference. The last 30 minute interval for the 18th is 0.6Kw and adding that to the total for the 19th gives the same value as that shown for the 18th in the download. So, in the daily usage download, the figures seem to be a total of all the 30 minute intervals for each day plus the last 30 minute interval of the previous day and then the result is put into the wrong day. I guess a similar thing is happening with the monthly download data but I haven't checked it.
Who's responsible for this? Or who can I contact about this?
Just emailed this to support.
I've been informed by Support that this has now been fixed and, as far as I can see, the data is now correct.
I think you'll find that it's probably a GMT/BST issue which I don't think the app handles correctly - your data probably looked OK when you posted on Feb 7 as that was in GMT so the displayed data in Bright matched the meter-data
Because the data you download from the meters is all recorded in UTC format, there are 4 scenarios which have to be handled when processing it in programs, or apps like Bright etc...
1) GMT - no problem since hours 00:00 thru 23:30 for that day are correct so Bright will display correctly
2) BST - have to use 23:00 & 23:30 from the previous day, then 00:00 to 22:30 on the current day due to the hour shift (23:00 & 23:30 belong to the following day)
3) Last Sunday in March GMT>BST - use 00:00 & 00:30 from current day ; set 01:00 and 01:30 to zero (as these are the hours you lose when the clock goes forwards) then the actual readings for 01:00;01:30 thru 22:30 are essentially shifted to 02:00;02:30 thru 23:30
4) Last Sunday in October BST<GMT - use 23:00 & 23:30 from the previous day and 00:00; 00:30 for the current day - however at 1am GMT (=2am BST) the clocks go back (so you get an extra hour in bed etc) so have to add the 01:00;00:30 values to the 00:00;00:30 values to account for this, then the 02:00 thru 23:30 values are correct, since these are already recorded in UTC time
I've just been through all this, writing code in Python on my raspberryPi, pulling the data from the Glow APIs and recording the readings in mySQL. I'm pretty sure I've got it coded correctly, but the data on the Bright App certainly seems to be all over the place now we're in BST