Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should use historical data entry for the sensor to improve reliability #389

Open
mattinglis opened this issue Jan 18, 2024 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@mattinglis
Copy link

Having used this integration for a few weeks, it's apparent that the API can't produce "live" data like a standard HA sensor does.

The code in sensor loops all catchup values and adds them together. This has the effect if the API is delayed, to just get splurges of data and not spread out through the day.

IMHO this sensor should use:
https://github.com/ldotlopez/ha-historical-sensor

And populate historical values rather than live.

If I get a chance I will fork this and give it a bash but next to no free time for the coming weeks so placing here for reference.

@mattinglis mattinglis added the enhancement New feature or request label Jan 18, 2024
@timrwhite87
Copy link

Let us know if you do manage to fork it; i'd love to test this!

@AN53808
Copy link

AN53808 commented Jan 19, 2024

Likewise, I've only just enabled the Hildebrand Glow integration and I'm also getting groups of data in the wrong timeslot and wrong day sometimes. I have my electricity and gas meter set up (my electricity meter is dual tariff too) so plenty of opportunity to get inaccurate data. I'd be very interested if you manage to find time to fork it, happy to test also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants