Utility meters broken - or am I missing something?

Configuration
1

To quote the doc:

Cycle reset occur at the beginning of the period (0 minutes, 0h00 hours, Monday, day 1, January).

Yet what I see in my meters is something like this:

Bildschirmfoto 2022-10-31 um 10.38.44
Bildschirmfoto 2022-10-31 um 10.38.441083×972 50.2 KB

As we can see - reset happens not at 00:00:00 (or “0h00 hours” for whatever that is supposed to express). This is bad if you rely on the period starting at zero and goes against the documented behavior.

Am I missing something obvious or should I file a bug?

Config:

      {
        "entry_id": "abf460bb1f1e53e7b8a424c010089428",
        "version": 1,
        "domain": "utility_meter",
        "title": "Wasser Utility",
        "data": {},
        "options": {
          "name": "Wasser Utility",
          "source": "sensor.wasserverbrauch",
          "cycle": "daily",
          "offset": 0.0,
          "tariffs": [],
          "net_consumption": false,
          "delta_values": false
        },
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": null,
        "disabled_by": null
      },
2

Check that the time on the pc you are viewing this on correct.

The web interface uses the browser time.

3

Time is correct (Both server and client are synced to ntp) though I wonder how a difference would come into play here. The stats are supposed to show the recorded value - how would a time difference between browser and server play any role here?

Edit: just noticed something:

1314815|2022-10-31 00:05:10.830649|2022-10-31 00:00:00.000000|||||0.0|5757.49|224
1314590|2022-10-31 00:00:10.802047|2022-10-30 23:55:00.000000|||||432.52|5757.49|224

The recorded value is correct. The UI displays a datapoint that just isn’t there. So the issue seems not to be with the Utility Meter but the graph display card pulling data points out of thin air.

4

The web browser you are using has the incorrect time.

5

If you say so…

6

I do. This issue has come up many, many times.

7

OK, enlighten me - how would that come into play here?

And again:

Bildschirmfoto 2022-10-31 um 12.24.47

8

HA just pulls the counter from the meter and only reset as the docs state, but the meter itself can also reset the counter, so maybe that is what occurs.