-
Notifications
You must be signed in to change notification settings - Fork 28
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
More frequent updates? #537
Comments
Why would you want to do this when:
These sort of requests are generally made by people who don’t understand system dynamics or engineering., or the implication ms of increasing data rates. |
I'm content with the polling frequency but, it would be awesome if we could access the data locally, rather than via the myenergi API. Perhaps if enough of us up vote a request for local access on their official forums (myenergi.info) MyEnergi will consider implementing the functionality. I agree with @G6EJD's first point. I would hate for MyEnergi to revoke, limit, or start charging for access to the API, which increasing polling frequency of ha-myenergi might increase the risk of happening. |
@i00 Currently sensors update every minute. That's the data resolution the API provides and it's unlikely to change. The local devices don't expose an easily readable interface, so you need to be a bit more 'creative'.
I've got the second option up and running and you get much more detailed info compared to the official API. I did have all the HW for option one as well, however not all the info is presented on the radio interface. |
Is your feature request related to a problem? Please describe.
Currently the sensors update every 5 mins - is there a reason for this? - is it possible to poll directly from the devices if there are call restrictions on the API calls (would be better IMHO if it was local poling anyway)?
Describe the solution you'd like
More frequent updates, pref with local polling
Describe alternatives you've considered
Updating source to increase polling period
Additional context
The text was updated successfully, but these errors were encountered: