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

Update Interval? #5

Open
think-nice-things opened this issue Apr 15, 2021 · 2 comments
Open

Update Interval? #5

think-nice-things opened this issue Apr 15, 2021 · 2 comments

Comments

@think-nice-things
Copy link

How often are the sensors updated?
Adjusting this to something like at least every few minutes would be helpful at least for the heart rate.

@cyberjunky
Copy link
Owner

Every 30 minutes, Google changed their API rate limits to 10000/month (we think)
I don't know it this is true for all endpoints, or we need to change code with different fetch processes with their own poll rates.

@think-nice-things
Copy link
Author

Hi
I digged a litte into the code.
It seems that for every sensor a dataPointChanges().list() is requested anyway.
What is returned is a list of data points but google_fit just uses the latest instead of updating HA with all datapoints which are not in HA so far.
So even if google is contacted every 30 minutes only, it might be able to get more datapoints for example if fit stores more datapoints than every 30 minutes only.

There are sensors which are probably not really updated frequently (like size or weight).
There are sensors which maybe are updated frequently, take for example heart rate.
If doing a workout, the heart rate might be updated more frequently.

It would be helpful, if google_fit integration would update HA with all datapoints of the list which are not yet in HA.

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

No branches or pull requests

2 participants