Suggestion: Delay readings to get accurate data

[Scryb]

I've had the integration installed for a few months, but for most of that time it has barely populated my energy readings at all. The daily totals are way below the actual usage, even though the Bright app shows more or less correct data.

Having just come back from a trip I decided to investigate some more, so I fired up Postman and followed the instructions from Glowmarkt to get my own readings. The readings I get from the Hildebrand API are very accurate. In fact more so than the Bright app. For example on September 18th Bright showed 15.06 15 kWh electricity used, whereas a call to the API using "sum" function and from/to set to 00:00:00 and 23:59:59 gave a reading of 16.85, which exactly matches the EON Next app.

I proceeded to collect hourly data from yesterday using the API, and they add up to exactly the same net usage as Bright (EON readings lag a few days).

What this suggests to me is that the problems with the integration might be related to trying to keep up with meter readings in real-time, which the Hildebrand API has trouble with. To test this I also tried getting readings using the API for the last few hours, and for the last two they show zero which is obviously false as I have a fridge and other things that use at least a little constantly.

My suggestion therefore would be to rework the integration to collect data with a 6, 12 or even 24 hour delay. I believe most users would prefer accurate data over quick readings.

[danlts]

I experience exactly the same when accessing the API directly. I think this is a good idea - keep this for 6 / 12 hours as suggested and recommend the setting up of MQTT local for those that want real time

[rahulpdev]

I have just started using the Hildebrand integration and am experiencing the same issue. I am also on EoN Next tariff and the Bright app is displaying accurate information so it does appear to be an issue with the integration.