Why energy totals disagree across midnight

Write the reporting time zone explicitly

One system may group records by UTC date while another groups them by the property’s local date. A third may show times using the browser’s location. “October 10” is not enough information to compare their daily totals.

Record both the property’s time zone and the report’s grouping rule. If you are viewing a distant property while traveling, do not assume the clock printed by your phone represents the property’s day. Timestamp display and daily aggregation can be configured independently.

Follow one reading across the boundary

The example uses a stated fixed offset. Other locations, and some jurisdictional exceptions, require their actual time-zone rules rather than an assumed offset copied from this worksheet.

Handle daylight saving as elapsed time

In locations that change clocks, a local calendar day can contain a different number of elapsed hours around the transition. A repeated clock label such as 1:30 a.m. may refer to two separate instants. Preserve an offset or UTC timestamp to distinguish them.

MDN’s Date reference explains the distinction between an instant and its local-time interpretation, including offset changes. For a monitoring comparison, use unambiguous timestamps and calculate duration from the instants rather than simply subtracting printed clock labels.

Check for a wrong clock as a separate problem

A legitimate time-zone difference is different from a host whose clock is wrong. If fresh samples appear far in the future, arrive out of order or shift after reconnection, record the device time, your reference time and whether the host recently restarted. Preserve the original timestamps while investigating.

Do not repair a historical report by arbitrarily moving rows until the bars match. First establish whether the issue is display formatting, grouping boundaries, a clock correction or missing data. Those require different remedies.

Use one comparison contract

1. Choose the exact start and end instants.
2. State the time zone used for labels.
3. Use the same measurement source and units.
4. Include the same valid intervals in both reports.
5. Decide how a boundary sample or cumulative counter is handled.

Write the contract above the spreadsheet or screenshot. If one report cannot supply the matching interval, describe the limitation rather than calling the difference an accuracy error.

This is especially useful when comparing a local dashboard, a manufacturer portal and a utility statement. Resolve the time window first; then investigate meter boundaries and measurement methods.