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

Octopus Home Mini live meter reading needs caching #379

Open
ryanw-mobile opened this issue Dec 22, 2024 · 0 comments
Open

Octopus Home Mini live meter reading needs caching #379

ryanw-mobile opened this issue Dec 22, 2024 · 0 comments
Assignees
Labels
feature A new feature for the user, not a new feature for a build script.

Comments

@ryanw-mobile
Copy link
Owner

This is the real issue:

This determines how often data related to your Home Mini is retrieved from Octopus Energy. The Octopus Energy APIs have a rate limit of 100 calls per hour, which is shared among all calls including through the app.

Our latest implementation to get a reading every minute takes up to 60 API calls if we do not navigate to other screens.
Since we don't cache API results if we hop between screens AND trigger other API calls (like getting usage) it is very likely we hit the limit very quickly.

Since we no longer get 10-seconds readings, it brings more value if we cache the latest 1-minute live meter reading.

@ryanw-mobile ryanw-mobile added the feature A new feature for the user, not a new feature for a build script. label Dec 22, 2024
@ryanw-mobile ryanw-mobile self-assigned this Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature for the user, not a new feature for a build script.
Projects
None yet
Development

No branches or pull requests

1 participant