Hello there:
Just last week noticed email reports is grabbing wrong days. Has anything being changed in the code?
See example of last 2 weeks, it’s self explanatory…
Hello there:
Just last week noticed email reports is grabbing wrong days. Has anything being changed in the code?
See example of last 2 weeks, it’s self explanatory…
Hello @Jujonet nothing should have changed in the code, are you using emoncms.org? All of my reports are showing ok (looking at a report sent earlier today).
Yeap, as stated in the Subject I’m using emoncms.org
I use PHPTIMESERIES in both feeds… gives any clue?
Any news on this?
Still getting wrong days in the report.
On top of it also noticed that assuming in the email the data is sorted in the good order (Monday to Sunday) I compared latest reports with feeds data with suprinsingly results: All weeks have 1 day offset and also 1 day with wrong data. See Below in text Format:
As stated in my latest post I use PHPTIMESERIES if that gives a clue.
Regards
Date | Weekday | “Node:01:Contador” | Email report |
---|---|---|---|
10 June 2019 | Monday | 1,320 | 1,395.00 |
11 June 2019 | Tuesday | 1,395 | 1,262.00 |
12 June 2019 | Wednesday | 1,262 | 1,238.00 |
13 June 2019 | Thursday | 1,238 | 1,062.00 |
14 June 2019 | Friday | 1,062 | 1,038.00 |
15 June 2019 | Saturday | 1,038 | 666 |
16 June 2019 | Sunday | 666 | 634 |
17 June 2019 | Monday | 1,291 | 993 |
18 June 2019 | Tuesday | 993 | 1,327.00 |
19 June 2019 | Wednesday | 1,327 | 1,032.00 |
20 June 2019 | Thursday | 1,032 | 1,325.00 |
21 June 2019 | Friday | 1,325 | 875 |
22 June 2019 | Saturday | 875 | 860 |
23 June 2019 | Sunday | 860 | 3,404.00 |
24 June 2019 | Monday | 4,696 | 1,674.00 |
25 June 2019 | Tuesday | 1,674 | 1,802.00 |
26 June 2019 | Wednesday | 1,802 | 1,596.00 |
27 June 2019 | Thursday | 1,596 | 2,444.00 |
28 June 2019 | Friday | 2,444 | 1,115.00 |
29 June 2019 | Saturday | 1,115 | 1,112.00 |
30 June 2019 | Sunday | 1,112 | 478 |
1 July 2019 | Monday | 1,324 | 1,398.00 |
2 July 2019 | Tuesday | 1,398 | 1,150.00 |
3 July 2019 | Wednesday | 1,150 | 1,556.00 |
4 July 2019 | Thursday | 1,556 | 1,671.00 |
5 July 2019 | Friday | 1,671 | 1,148.00 |
6 July 2019 | Saturday | 1,148 | 1,030.00 |
7 July 2019 | Sunday | 1,030 | 609 |
8 July 2019 | Monday | 1,275 | 1,298.00 |
9 July 2019 | Tuesday | 1,298 | 1,393.00 |
10 July 2019 | Wednesday | 1,393 | 1,489.00 |
11 July 2019 | Thursday | 1,489 | 1,477.00 |
12 July 2019 | Friday | 1,477 | 777 |
13 July 2019 | Saturday | 777 | 764 |
14 July 2019 | Sunday | 764 | 704 |
15 July 2019 | Monday | 1,575 | 1,066.00 |
16 July 2019 | Tuesday | 1,066 | 1,011.00 |
17 July 2019 | Wednesday | 1,011 | 1,555.00 |
18 July 2019 | Thursday | 1,555 | 1,407.00 |
19 July 2019 | Friday | 1,407 | 2,027.00 |
20 July 2019 | Saturday | 2,027 | 1,078.00 |
21 July 2019 | Sunday | 1,078 | 459 |
22 July 2019 | Monday | 1,353 | 996 |
23 July 2019 | Tuesday | 996 | 1,138.00 |
24 July 2019 | Wednesday | 1,138 | 1,454.00 |
25 July 2019 | Thursday | 1,454 | 1,405.00 |
26 July 2019 | Friday | 1,405 | 864 |
27 July 2019 | Saturday | 864 | 650 |
28 July 2019 | Sunday | 650 | 604 |
Hello @Jujonet what input processor are you using to generate the feed? are you using power_to_kwh or power_to_kwhd?
Ok, could you try using the wh_accumulator process and writing to a PHPFina feed instead? I think it will give better results.
Could you explain the reason for that? Is that a bug or is the email module only intended to work with fixed interval whacc?
Could it be TZ errors? ie a mismatch of TZ’s and/or day/week starting points.
A quick look at the example data Julio has provided, if you shift the email reported data forward one day that only leaves a dependency once a week when the start of the week could be different.
Date | Weekday | “Node:01:Contador” | Email report | Diff | |
---|---|---|---|---|---|
10-Jun-19 | Monday | 1320 | |||
11-Jun-19 | Tuesday | 1395 | 1395 | 0 | |
12-Jun-19 | Wednesday | 1262 | 1262 | 0 | |
13-Jun-19 | Thursday | 1238 | 1238 | 0 | |
14-Jun-19 | Friday | 1062 | 1062 | 0 | |
15-Jun-19 | Saturday | 1038 | 1038 | 0 | |
16-Jun-19 | Sunday | 666 | 666 | 0 | |
17-Jun-19 | Monday | 1291 | 634 | 657 | |
18-Jun-19 | Tuesday | 993 | 993 | 0 | |
19-Jun-19 | Wednesday | 1327 | 1327 | 0 | |
20-Jun-19 | Thursday | 1032 | 1032 | 0 | |
21-Jun-19 | Friday | 1325 | 1325 | 0 | |
22-Jun-19 | Saturday | 875 | 875 | 0 | |
23-Jun-19 | Sunday | 860 | 860 | 0 | |
24-Jun-19 | Monday | 4696 | 3404 | 1292 | |
25-Jun-19 | Tuesday | 1674 | 1674 | 0 | |
26-Jun-19 | Wednesday | 1802 | 1802 | 0 | |
27-Jun-19 | Thursday | 1596 | 1596 | 0 | |
28-Jun-19 | Friday | 2444 | 2444 | 0 | |
29-Jun-19 | Saturday | 1115 | 1115 | 0 | |
30-Jun-19 | Sunday | 1112 | 1112 | 0 | |
01-Jul-19 | Monday | 1324 | 478 | 846 | |
02-Jul-19 | Tuesday | 1398 | 1398 | 0 | |
03-Jul-19 | Wednesday | 1150 | 1150 | 0 | |
04-Jul-19 | Thursday | 1556 | 1556 | 0 | |
05-Jul-19 | Friday | 1671 | 1671 | 0 | |
06-Jul-19 | Saturday | 1148 | 1148 | 0 | |
07-Jul-19 | Sunday | 1030 | 1030 | 0 | |
08-Jul-19 | Monday | 1275 | 609 | 666 | |
09-Jul-19 | Tuesday | 1298 | 1298 | 0 | |
10-Jul-19 | Wednesday | 1393 | 1393 | 0 | |
11-Jul-19 | Thursday | 1489 | 1489 | 0 | |
12-Jul-19 | Friday | 1477 | 1477 | 0 | |
13-Jul-19 | Saturday | 777 | 777 | 0 | |
14-Jul-19 | Sunday | 764 | 764 | 0 | |
15-Jul-19 | Monday | 1575 | 704 | 871 | |
16-Jul-19 | Tuesday | 1066 | 1066 | 0 | |
17-Jul-19 | Wednesday | 1011 | 1011 | 0 | |
18-Jul-19 | Thursday | 1555 | 1555 | 0 | |
19-Jul-19 | Friday | 1407 | 1407 | 0 | |
20-Jul-19 | Saturday | 2027 | 2027 | 0 | |
21-Jul-19 | Sunday | 1078 | 1078 | 0 | |
22-Jul-19 | Monday | 1353 | 459 | 894 | |
23-Jul-19 | Tuesday | 996 | 996 | 0 | |
24-Jul-19 | Wednesday | 1138 | 1138 | 0 | |
25-Jul-19 | Thursday | 1454 | 1454 | 0 | |
26-Jul-19 | Friday | 1405 | 1405 | 0 | |
27-Jul-19 | Saturday | 864 | 864 | 0 | |
28-Jul-19 | Sunday | 650 | 650 | 0 | |
604 |
Guess have to leave this till month end as I’m on holidays…
Could you leave the bug opened till my return to see if it is solved? Do not want to start a new feed and therefore loose all my history…
I was thinking it could be caused by missing datapoints around midnight. The general design approach for kWh data and associated features is to use the power_to_kwh process. This said I thought I had asked about timezone settings but looking again above I did not.
Could you check your timezone setting under the My Account tab @Jujonet
Thanks @Jujonet that looks fine. I think this is being caused by a timing issue with the data relating to the use of the PHPTimeSeries feed. The implementation is not really designed for the use of PHPTimeSeries in this way unfortunately. I will see if I can find a way to get it working.
I think I’ve got it, I’ve applied a rounding to the timestamps returned by PHPTimeSeries so that if the timestamps are returns as one minute to midnight they are rounded to be midnight values (within the email report module).
Just to help me try and understand this a little better, how often and at what times was the data from your water meter being read/sent? Was it quite regularly, on change or just once or twice a day?
Great to hear, not 100% about the 8 days I think its a difference in the phptimeseries vs phpfina api response.
Just to help me try and understand this a little better, how often and at what times was the data from your water meter being read/sent? Was it quite regularly, on change or just once or twice a day?
As soon as it delivers new measure. Can be every minute or once an hour depending on the water usage in my house…