Colin Robbins

That all looks OK. I can only think it is a rogue data point somewhere.

There not really an easy way in HA, and depends your SQL knowledge. If you are happy with SQL, you could use SQLLite to query the HA database and see...

For hints on exploring the database see [this thead](https://community.home-assistant.io/t/energy-dashboard-allow-gas-as-kwh/339891/27).

The spikes are ‘usual’ sadly, The reading provided is the reading is the delta since the last success. It seems from your stats, that some data points were not read...

The integration should cope with the UTC/DST conversion. The delay is because the Glow API presents data 30 minutes delayed. They also implement some form of rate limiting, so sometime...

The code makes a UTC/DST calculation [glow.py line 139](https://github.com/HandyHat/ha-hildebrandglow-dcc/blob/main/custom_components/hildebrandglow_dcc/glow.py#L139). it’s working correctly for me… 

This seems to be the behaviour I would expect, and the best I believe we can achieve with this approach. The DDC data is delayed by at least 30 minutes...

As explained above, this is expected behaviour. The DDC data is delayed by at least 30 minutes by DCC design. Thus any data from the Glow API is at least...

I think this is a duplicate of https://github.com/Villhellm/custom-sidebar/issues/40

The issue is the same with the release version `2021.11.0` ``` Logger: frontend.js.latest.202111030 Source: components/system_log/__init__.py:190 First occurred: 17:16:35 (4 occurrences) Last logged: 17:26:13 http://192.168.10.39:8123/hacsfiles/custom-sidebar/custom-sidebar.js:164:66 Uncaught TypeError: Cannot read properties of...