Report vs. Widget Discrepancies

This discussion is intended to be about the new web application for EKM Push users at http://www.encompass.io that has been beta released. Use this discussion to talk about your experiences with Encompass, including what works, what doesn't, and what could be added or improved.
Post Reply
bandtank
Posts: 13
Joined: Fri Mar 08, 2019 8:43 am

Report vs. Widget Discrepancies

Post by bandtank » Sun Dec 01, 2019 10:58 am

I am seeing discrepancies between widget and report values. The calendar widget, which aggregates monthly usage, shows a monthly total that does not match the monthly total the associated report. Here are some examples:

From the widgets on the website:
  • October = 153.24 kWh
  • November = 303.1 kWh
However, the report shows different values:
  • October = 140.3 kWh
  • November = 303.7 kWh
There are two issues that I've seen so far. The first is that the report does not always include the correct number of days when calculating the total for the previous month. October has 31 days, but only 30 are included in the report even though I have it set to the 1st through the 31st. It appears to be using the last day of the current month in the query even if the previous month has more days. The second issue is that the values are slightly off even if the correct number of days are used (303.1 vs. 303.7 kWh for November as an example).

I have seen both behaviors on multiple reports and widgets including electric and water meters from two Omnimeter V4s.
Attachments
meters.png
meters.png (45.27 KiB) Viewed 298 times

Jameson
Posts: 775
Joined: Fri Nov 04, 2011 7:42 pm
Location: Santa Cruz, CA
Contact:

Re: Report vs. Widget Discrepancies

Post by Jameson » Tue Dec 03, 2019 5:00 am

Yes I can see what you are saying about November, it looks like the data in encompass is correct. The data in your report is off by 0.6 kWh for some reason (I would guess it has something to do with the timezone shift, meaning a month in your timezone will be just slightly different than a month in the wrong timezone). We should be able to get to the bottom of this and sort it out pretty quickly.

As for October, it is off by quite a bit more. Encompass is also correct in this case. The report is off because like you say, the report is dropping the last day of the month. This started from a desire to compare one month to the previous month. But if one month has 30 days and the next month has 31 days, you could either compare 30 days to 31 days or 30 days to 30 days. If you compare 30 to 31, then the months with more days will always look like higher consumers of electricity. If you compare 30 to 30 then you have the issue of dropping a day. There is no perfect solution to this. We are leaning toward comparing 30 days to 31 days in this case. Maybe adding something like a kWh per day value, which could be a good idea. Let us know which you think would be a better comparison to use.

If you ever really want to look at the data behind the scenes that we are using with your meter, it would be best to go to the source and look at the Summary API data for your meters. Here is a link to the Summary API data section of out Developer Portal: https://documents.ekmmetering.com/api-d ... ummary-api

And please by all means always point out issues you are seeing and improvements you want, we are making these tools for you :ugeek:
Jameson
EKM METERING
http://www.ekmmetering.com
831.425.7371

bandtank
Posts: 13
Joined: Fri Mar 08, 2019 8:43 am

Re: Report vs. Widget Discrepancies

Post by bandtank » Tue Dec 03, 2019 8:26 am

I see what you mean regarding the comparison periods. Interesting.

I think a kWh per day metric would be the most straightforward solution since that's arguably what you are really comparing when it comes to long periods of time. The total is relevant in other contexts, so having both would be helpful. With that said, leaving days off of a period is not an intuitive behavior and I didn't notice that October ended on the 30th until I had been confused for a few days. I would argue that the day boundaries should be handled in the most intuitive way even if it means sacrificing the ability to make exact comparisons in other places. I agree there is no perfect solution.

I have some broader feedback regarding reports, timezones, and other Encompass features that I will post in a different thread.

Post Reply