Reading aggregate calculation incorrect on perfectly hourly input data

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: DB
    • None

      If a datum stream has datum on perfect hour timestamps the reading style aggregate calculation always produces 0 as the output, even though there is a difference in the input values. For example, a datum stream like the following:

      created,localDate,localTime,nodeId,sourceId,wattHours
2017-07-04T07:00:00.000Z,2017-07-04,03:00,1,A,12476432000
2017-07-04T08:00:00.000Z,2017-07-04,04:00,1,A,12476432000
2017-07-04T09:00:00.000Z,2017-07-04,05:00,1,A,12476432001
2017-07-04T10:00:00.000Z,2017-07-04,06:00,1,A,12476432038

      Should result in hourly reading accumulation differences of

      2017-07-04T07:00:00.000Z,0
2017-07-04T08:00:00.000Z,1
2017-07-04T09:00:00.000Z,37

      Instead SolarNetwork is generating 0 for all output hours.

       

            Assignee:
            Matt Magoffin
            Reporter:
            Matt Magoffin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: